On Tue, Aug 26, 2014 at 05:02:10PM +0300, Itzik Brown wrote:
> Hi,
> Following the conversation [1]:
> My understanding was that the way to use out of the tree vif_driver is to
> set vif_driver option in nova.conf
> until there is a better way to support such cases but the commit [2] removed
> this option.
> Can someone clarify the current status (i.e. what is the current way to do
> it ) in Juno?

For Juno the vif_driver option still exists & can be used.

It is only deleted in the Kilo release.

The recommendation is that people working on new VIF drivers should do
so on a branch of the Nova repo, so that the can modify the libvirt VIF
driver code to support their needs, rather than try to write a completely
isolated out of tree impl. This is an approach that will need to be taken
regardless in order to submit the VIF driver for review and merge to Nova.

|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

OpenStack-dev mailing list

Reply via email to