[Openstack] Grizzly libvirt volume drivers all in single file "volume.py"?

Brad Goodman brad at bradgoodman.com
Tue Jul 2 12:31:22 UTC 2013

I am trying to write a volume driver for a new/unique storage type
uncovered by the existing ones.

I have a Cinder driver working fine - but I am now working on adding the
nova/libvirt component of it (for Nova clients to connect into).

It appears that (unlike in Cinder) - ALL of the drivers are in a single
file "volume.py" and the libvirt_volume_drivers list options all call the
classes from it.

Any attempt I have made to call a driver in another file results in the
libvirt.driver module itself to fail to load.

Is there some (odd) reason why all the drivers are placed in a single file?
Will it continue to be mandated to do it this why? Is there a way around
this that I am missing?

This seems broken and wrong for so many different reasons...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130702/e1bfd59b/attachment.html>

More information about the Openstack mailing list