VIF drivers for libvirt.
Bases: object
Generic VIF driver for libvirt networking.
Get VIF configurations for bridge type.
Ensure that the bridge exists, and add VIF to it.
Plug using PLUMgrid IO Visor Driver
Connect a network device to their respective Virtual Domain in PLUMgrid Platform.
Plug using hybrid strategy (same as OVS)
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 IVS port. Then boot the VIF on the linux bridge using standard libvirt mechanisms.
Plug into MidoNet’s network port
Bind the vif to a MidoNet virtual port.
No manual plugging required.
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.
Plug a VIF_TYPE_TAP virtual interface.
Create a fp netdevice interface with a vhostuser socket
Plug a VIF_TYPE_VHOSTUSER into an ovs bridge
Plug into Contrail’s network port
Bind the vif to a Contrail virtual port.
No manual unplugging required.
Unplug using PLUMgrid IO Visor Driver
Delete network device and to their respective connection to the Virtual Domain in PLUMgrid Platform.
Unplug the VIF by deleting the port from the bridge.
UnPlug using hybrid strategy (same as OVS)
Unhook port from IVS, unhook port from bridge, delete bridge, and delete both veth devices.
Unplug from MidoNet network port
Unbind the vif from a MidoNet virtual port.
No manual unplugging required.
UnPlug using hybrid strategy
Unhook port from OVS, unhook port from bridge, delete bridge, and delete both veth devices.
Unplug a VIF_TYPE_TAP virtual interface.
Delete a fp netdevice interface with a vhostuser socket
Unplug a VIF_TYPE_VHOSTUSER into an ovs bridge
Unplug Contrail’s network port
Unbind the vif from a Contrail virtual port.