Ask Your Question

Grizzly libvirt volume drivers all in single file ""

asked 2013-06-28 15:38:44 -0600

BradG gravatar image

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 "" 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 modules 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...

edit retag flag offensive close merge delete

1 answer

Sort by ┬╗ oldest newest most voted

answered 2013-08-10 21:03:47 -0600

fifieldt gravatar image

Hi Brad,

This seems like a great discussion to have on the development mailing list:

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-06-28 15:38:44 -0600

Seen: 117 times

Last updated: Aug 10 '13