libvirt: Add a Quobyte Volume Driver in Nova

Registered by Silvan Kaiser

Add a Nova volume driver for the storage system "Quobyte USP", allowing to mount images residing in Quobyte USP in Nova VMs.

First step is allowing VM images stored on a Quobyte USP to be mounted in a VM during startup. Follow up is unmounting, which is done when shutting down the VM.
Implementation has begun as submitted in Change-Id: Ica1820031f1fc8b66d7ed7fe76ffeb985cf0ef35 (

Corresponding blueprint for the cinder driver:

Blueprint information

John Garbutt
Silvan Kaiser
Silvan Kaiser
Series goal:
Accepted for kilo
Milestone target:
milestone icon 2015.1.0
Started by
Silvan Kaiser
Completed by
John Garbutt

Related branches



Please submit a nova-spec for this kind of addition. We need to discuss how this will be tested, vs the impact on the code base. Be sure the reference an approved cinder spec --johnthetubaguy 19th November 2014

Thanks for the input! It was my impression that a spec is not really required (after reading No relevant API / architecture changes intended. Cinder blueprint had a spec requested by someone but afaiu this was not followed up because of the strong closeness to the Cinder GlusterFS driver who is already present. Do you really think a spec is required?
(Note: I added blueprint & code links to the description.) --kaisers 21th Nov 2014

Note: Spec was added after some further discussion and is available via spec link above and link below on the whiteboard!

You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)

Gerrit topic:,topic:spec/quobyte-nova-driver,n,z

Addressed by:
    Add a Quobyte Volume Driver in Nova

Gerrit topic:,topic:gerrit_submit_cherrypicked,n,z

Addressed by:
    Created Nova driver for Quobyte USP

Gerrit topic:,topic:bp/quobyte-nova-driver,n,z

Gerrit topic:,topic:bp/s,n,z

FYI: The corresponding cinder driver was merged prior to k-1 milestone -- kaisers 12th Jan 2015

Sorry, we have now hit the non-priority feature freeze for kilo. Please resubmit your spec for the L release. -- ttx on behalf of johnthetubaguy 5th Feb 2015

I'm currently in contact with core reviewers who are in this moment approving the change set (see Addressed by: and our current talk on #openstack-nova)!!! --kaisers (alias casusbelli) 5th Feb 2015

Driver code was merged into master 2015-02-10. What exactly happens to this blueprint, now? -- kaisers 11th Feb 2015

Apprently this was merged in violation of the blueprint freeze, but still restoring to kilo-3 for documentation reasons. --johnthetubaguy 16th Feb 2015

Apparently not all the code is up for review yet, despite being in NeedsCodeReview, so marking this a partially complete. --johnthetubaguy 16th Feb 2015

Seems to be a state confusion? All code is up and merged, state is 'implemented'.
Currently the Cinder CI that will also test the nova driver is in the works. But there is no other change set planned for this blueprint from my side. -- kaisers 17th Feb 2015

OK, I was miss informed, seems all the code has merged (in violation of the feature freeze), this is fully complete. --johnthetubaguy 17th Feb 2015


Work Items

This blueprint contains Public information 
Everyone can see this information.