[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-API] Re: [Xen-devel] [XCP] new version available
Furthermore, you can still switch between the vswitch and linux bridging network subsystems by altering the file /etc/xensource/network.conf ("vswitch" or "bridge"). The default is now "vswitch", and eventually the linux bridging option will be removed. See http://openvswitch.org/ for more information about the vswitch. Cheers, Rob -----Original Message----- From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ian Campbell Sent: 19 January 2010 13:53 To: Marco Sinhoreli Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Dave Scott; xen-api@xxxxxxxxxxxxxxxxxxx Subject: Re: [Xen-API] Re: [Xen-devel] [XCP] new version available On Tue, 2010-01-19 at 13:43 +0000, Marco Sinhoreli wrote: > Hi all, > > The openvswitch is already enabled in XCP? Yes. > It could to change some > call in xapi or in network infrastructure like switches? If you are asking whether this change will cause an XCP host to try and configure/manage your physical switches then the answer is no. This change is purely to replace the Linux bridging implementation used on an XCP host with an openvswitch based solution. It doesn't change any XenAPI calls but it does necessarily change the implementation of the interactions between xapi and host's network subsystem. Mainly those changes are in ocaml/netdev/netdev.ml and in things like the interface-reconfigure and VIF hotplug scripts. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |