Libvirt release 0.9.11 has added support for Open vSwitch so it is no
longer required to use bridge compatibility mode! Fedora 17 has 0.9.11
included.
If you have brcompat enabled disable it.
Configuration basically consists of adding the following line to a
interface setup in bridge mode with the bridge being a OVS bridge.
<virtualport type='openvswitch'/>
Here are a few links to point you in the right direction.
Configuring a domain's network interface to use Open vSwitch
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=INSTALL.Libvirt;hb=HEAD
Additional information on Open vSwitch Hypervisor integration.
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=IntegrationGuide;hb=HEAD
If you have a version of libvirt older than 0.9.11 you will still need to use bridge compatibility mode as described in the previous post http://binarybitme.blogspot.com/2011/09/using-open-vswitch-with-libvirt-and.html
So does this replace the need for fake bridges when creating VLANs? It would be great if all of the network config could be done within Libvirt. I can't see how you can scale to hundreds of VLANs for doing something like IaaS with the current method of seperate fake bridges.
ReplyDeleteAs far as I know the current support only adds the TAP interface to the vswitch and you cannot define any configuration options through libvirt. So you will still need fake bridges. The only way I can see to scale with Open vSwitch would be integration with something like libvirt as you describe or a OpenFlow controller that integrates. I believe Open vSwitch support is going to be added(already has been?) to oVirt and platforms like OpenStack are also integrating it.
Delete