VIF drivers for libvirt.
Bases: nova.virt.vif.VIFDriver
VIF driver for Linux bridge.
Ensure that the bridge exists, and add VIF to it.
No manual unplugging required.
Bases: nova.virt.libvirt.vif.LibvirtBridgeDriver, nova.virt.libvirt.vif.LibvirtOpenVswitchDriver
VIF driver that uses OVS + Linux Bridge for iptables compatibility.
Enables the use of OVS-based Quantum plugins while at the same time using iptables-based filtering, which requires that vifs be plugged into a linux bridge, not OVS. IPtables filtering is useful for in particular for Nova security groups.
Plug using hybrid strategy
Create a per-VIF linux bridge, then link that bridge to the OVS integration bridge via a veth device, setting up the other end of the veth device just like a normal OVS port. Then boot the VIF on the linux bridge using standard libvirt mechanisms
UnPlug using hybrid strategy
Unhook port from OVS, unhook port from bridge, delete bridge, and delete both veth devices.
Bases: nova.virt.vif.VIFDriver
VIF driver for Open vSwitch that uses libivrt type=’ethernet’
Used for libvirt versions that do not support OVS virtual port XML (0.9.10 or earlier).
Unplug the VIF by deleting the port from the bridge.
Bases: nova.virt.vif.VIFDriver
VIF driver for Open vSwitch that uses integrated libvirt OVS virtual port XML (introduced in libvirt 0.9.11).
Pass data required to create OVS virtual port element
No action needed. Libvirt takes care of cleanup
Bases: nova.virt.vif.VIFDriver
VIF driver for Linux Bridge when running Quantum.
Unplug the VIF by deleting the port from the bridge.