In Nova, what is the default vif-driver for xen using libvirt?

asked 2017-03-21 20:33:28 -0500

minimike gravatar image

Hello

My question is for Mitaka and Newton. some days ago, I've tried to setup XEN 4.8 (with libxenlight) with libvirt-backend and openvswitch on an compute node. XEN and openvswitch without libvirt works absolute impressive. So I thought it would be easy to set it up on an OpenStack-Compute-Host. Ok I have to use libvirt but who cares... So far I had no success. With neutron and openvswitch I had no one problem. But if nova should asign an interface to an openvswitch-bridge something has used the wrong network-scripts. After all. by manipulating scripts from xen itself, it was to be able to setup an interface of an VM to the ovs-bridge br-int. So I've gived it up to try it later... All with XEN 4.8 libvirt nova and neutron would work if I would use an linux-bridge instead of openvswitch. But this is not an option :)

Today I've tested something and read more and more documentation and I've found something

DEPRECATED: The XenAPI VIF driver using XenServer Network APIs. # Provide a string value representing the VIF XenAPI vif driver to use for plugging virtual network interfaces. # Xen configuration uses bridging within the backend domain to allow all VMs to appear on the network as individual hosts. Bridge interfaces are used to create a XenServer VLAN network in which the VIFs for the VM instances are plugged. If no VIF bridge driver is plugged, the bridge is not made available. This configuration option takes in a value for the VIF driver. # Possible values: # * nova.virt.xenapi.vif.XenAPIOpenVswitchDriver (default) * nova.virt.xenapi.vif.XenAPIBridgeDriver (deprecated) # Related options: # * vlan_interface * ovs_integration_bridge (string value) This option is deprecated for removal since 15.0.0. Its value may be silently ignored in the future. Reason: There are only two in-tree vif drivers for XenServer. XenAPIBridgeDriver is for nova-network which is deprecated and XenAPIOpenVswitchDriver is for Neutron which is the default configuration for Nova since the 15.0.0 Ocata release. In the future the "use_neutron" configuration option will be used to determine which vif driver to use. vif_driver = nova.virt.xenapi.vif.XenAPIOpenVswitchDriver

By Mitaka (Ubuntu 16.04) and Newton (Debian 9) what is the default driver in nova for interfaces to attach to an bridge they will be managed bei neutron? Could I use the class nova.virt.xenapi.vif.XenAPIOpenVswitchDriver with libxenlight and libvirt? Or is it exclusive for XenServer from Citrix? This time I would like to ask before. Just to create a plan :)

edit retag flag offensive close merge delete