Just a few notes to add to this discussion. The Xen Cloud Platform (XCP) and Citrix XenServer both have Open vSwitch integration.
Also, as of Xen 4.1 the bridge scripts within Xen are deprecated in favor of using bridging with the distro (or alternatively Open vSwitch). See: http://wiki.xensource.com/xenwiki/Xen4.1 http://wiki.xensource.com/xenwiki/MigrationGuideToXen4.1%2B http://wiki.xensource.com/xenwiki/HostConfiguration/Networking Also the Xen LiveCD project is planning to add Open vSwitch support, so there is also a potential for collaboration there. Finally, as ovs heads into mainline Linux, it'll become easier to integrate ovs into a distro solution based on Xen. Xen.org would be happy to take patches for Xen 4.1+ (xen-unstable would probably be the best place) that add the necessary Open vSwitch support (if anything is needed on the Xen side of things to support it). Guests can just recognize the Open vSwitch bridges as bridges and things for the most part should just work. Please report any issues, questions to the Xen-users mailing list and patches and bugs to Xen-devel as appropriate. Thanks, Todd On Sun, Apr 3, 2011 at 8:16 AM, Jason Long <[email protected]> wrote: > Hi Joseph, > > This is extremely helpful, thank you. I need VLAN support so I'll start > digging into the scripts. If you want to share any of your changes I am > sure that would save me some time! > > Jason > > > > On 4/1/11 3:16 PM, Joseph Glanville wrote: >> Hi Jason >> >> I recently integrated Open vSwitch with Xen. >> >> There are 2 possible routes, the choice boils down to what level of >> customisation you need. >> >> The first is to load the bridge compatiblity module as part of OVS and >> the Xen scripts will work out of the box. >> Ideal for testing and simple deployments. >> >> This can be easily done by following the instructions in INSTALL.bridge >> >> Secondly you can modify the /etc/xen/scripts* to use ovs-vsctl to >> setup the bridge ports and apply flow rules on port creation with >> ovs-ofctl etc. >> I recommend this path if you require the use of VLANs, any kind of >> flow control etc. >> >> The specific scripts you need to modify are >> /etc/xen/scripts/vif-bridge and if you don't make it obselete by >> pushing the ip link set <vif> up back into vif-bridge then you need to >> edit the setup_bridge_port function in >> /etc/xen/scripts/xen-networking-common. >> >> I hope that sheds some light on what is required, don't hesitate to >> ping back if you require more help. >> >> Kind regards, >> Joseph. >> >> On 2 April 2011 08:27, Jason Long <[email protected]> wrote: >>> Hi, >>> >>> I want to try out open vswitch with xen. I followed the instructions in >>> INSTALL.Linux. Everything went good. The module is loaded, ovsdb-server >>> is running, ovs-switchd is running, and I setup a bridge named br0 to >>> include physical port eth1. >>> >>> Now what is the best way to make xen use open vswitch?? It runs network >>> scripts when xend starts that invoke brctl to setup a bridge and create >>> virtual interfaces. >>> >>> Do I have to edit the scripts to use ovs-vsctl? Or can I bypass the xen >>> scripts and map interfaces manually? >>> >>> Any pointers or links would be helpful. Thanks! >>> >>> Jason > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss > -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
