On 27/08/2014 17:06, Daniel P. Berrange wrote:
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.
Regards,
Daniel
Sorry for taking the newbie approach here but can you explain me how to
do it in Juno?
I see that vif_driver is pointing to LibvirtGenericVIFDriver [1]but not
to a config option.
[1]
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py
BR,
Itzik
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
