In the nova-api meeting today we were talking about the nova
os-assisted-volume-snapshots API and whether or not it was a proxy API
to cinder. We determined it's not, it performs an action on a server
resource. But what a few of us didn't realize was it's an admin API in
nova only for cinder RemoteFSSnapDrivers to call when creating a volume
snapshot.
From what I can tell, this is used in Cinder by the glusterfs, scality,
quobyte and virtuozzo remotefs volume drivers.
This is also a nova API that's only implemented for the libvirt compute
driver - so gmann is going to document that in the nova api-ref for the
API so it's at least communicated somewhere (it's not in the nova
feature support matrix).
The other thing I was wondering about was CI coverage. I looked through
several cinder patches this morning looking for recent successful CI
results for gluster/scality/quobyte but couldn't find any.
Does someone have a link to a successful job run for one of those
drivers? I'd like to see if they are testing volume snapshot and that
it's properly calling the nova API and everything is working. Because
this is also something that Nova could totally unknowingly break to that
flow since we have no CI coverage for it (we don't have those cinder 3rd
party CI jobs running against nova changes).
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
