Wei-Chih Chen (陳偉志)
2011-Jun-15 10:13 UTC
[Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Hello Everyone,
I am new with XCP.
I''ve setup several hosts with* XCP 1.0* and manage it through XenCenter
and
command console.
Each host has two NICs, one (xenbr0) connected to a physical switch for
Internet (said sw1), the other (xenbr3) connected to a physical switch for
internal network (said sw2).
I am trying to setup VMs and VLANs on xenbr3.
I created a virtual bridge by "ovs-vsctl add-br brvlan2 xenbr3 2"
Then add a port (portvlan2) to brvlan2:
ovs-vsctl add-port brvlan2 portvlan2 tag=2
ifconfig vlan2 192.168.33.200
Now the problem is that I do know how to attach portvlan2 to VM.
Could someone give me simple steps to setup VLANs using Open vSwitch and
attach them to VMs?
Moreover, the newly created bridges are not shown in XenCenter.
If I use xe network-create, the newly created network can be shown in
XenCenter.
Is this because XenCenter uses xe command and does NOT support to show Open
vSwitch?
The question I wonder most is what is the difference to configure XCP
network using *xe* and *ovs-* commands?
Thanks a lot. :)
Regards,
Wayne
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Todd Deshane
2011-Jun-16 00:08 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
On Wed, Jun 15, 2011 at 6:13 AM, Wei-Chih Chen (陳偉志) <wcchen.tw@gmail.com> wrote:> Hello Everyone, > > I am new with XCP. > I''ve setup several hosts with XCP 1.0 and manage it through XenCenter and > command console. > Each host has two NICs, one (xenbr0) connected to a physical switch for > Internet (said sw1), the other (xenbr3) connected to a physical switch for > internal network (said sw2). > > I am trying to setup VMs and VLANs on xenbr3. > I created a virtual bridge by "ovs-vsctl add-br brvlan2 xenbr3 2" > Then add a port (portvlan2) to brvlan2: > ovs-vsctl add-port brvlan2 portvlan2 tag=2 > ifconfig vlan2 192.168.33.200 > Now the problem is that I do know how to attach portvlan2 to VM. > Could someone give me simple steps to setup VLANs using Open vSwitch and > attach them to VMs? > > Moreover, the newly created bridges are not shown in XenCenter. > If I use xe network-create, the newly created network can be shown in > XenCenter. > Is this because XenCenter uses xe command and does NOT support to show Open > vSwitch? > The question I wonder most is what is the difference to configure XCP > network using xe and ovs- commands? >You are going to want to use the xe commands related to networking. See http://docs.vmd.citrix.com/XenServer/5.6.0fp1/1.0/en_gb/reference.html#networking-concepts Hope that helps. Thanks, Todd> Thanks a lot. :) > > Regards, > > Wayne > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jun-16 01:53 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
On Thu, Jun 16, 2011 at 8:08 AM, Todd Deshane <todd.deshane@xen.org> wrote:> On Wed, Jun 15, 2011 at 6:13 AM, Wei-Chih Chen (陳偉志) > <wcchen.tw@gmail.com> wrote: > > Hello Everyone, > > > > I am new with XCP. > > I''ve setup several hosts with XCP 1.0 and manage it through XenCenter and > > command console. > > Each host has two NICs, one (xenbr0) connected to a physical switch for > > Internet (said sw1), the other (xenbr3) connected to a physical switch > for > > internal network (said sw2). > > > > I am trying to setup VMs and VLANs on xenbr3. > > I created a virtual bridge by "ovs-vsctl add-br brvlan2 xenbr3 2" > > Then add a port (portvlan2) to brvlan2: > > ovs-vsctl add-port brvlan2 portvlan2 tag=2 > > ifconfig vlan2 192.168.33.200 > > Now the problem is that I do know how to attach portvlan2 to VM. > > Could someone give me simple steps to setup VLANs using Open vSwitch and > > attach them to VMs? > > > > Moreover, the newly created bridges are not shown in XenCenter. > > If I use xe network-create, the newly created network can be shown in > > XenCenter. > > Is this because XenCenter uses xe command and does NOT support to show > Open > > vSwitch? > > The question I wonder most is what is the difference to configure XCP > > network using xe and ovs- commands? > > > > You are going to want to use the xe commands related to networking. > > See > http://docs.vmd.citrix.com/XenServer/5.6.0fp1/1.0/en_gb/reference.html#networking-concepts > > Hope that helps. > > Thanks, > Todd > > > > Thanks a lot. :) > > > > Regards, > > > > Wayne > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/ >Thank you, Todd. The document helps a lot for XenServer network concepts and xe command control. However, I would like to try Open vSwitch because it supports more features like OpenFlow, NetFlow. It is possible for me to use these features in the future. Is it able to use full features of Open vSwitch in XCP 1.0? Or XCP has not included and combined Open vSwitch completely, and it is not suggested to use Open vSwitch in XCP 1.0? Thanks. Regards, Wayne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jun-16 03:34 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Hello Everyone, Citrix provides *vSwitch Controller* to manage network across hosts. However, it seems requiring XenServer Advanced edition, and downloading vSwitch Controller requires My Citrix account. Is vSwitch Controller essential for XCP to control and use full functions of Open vSwitch? The point is that I can not figure out the relationship of - XCP vs XenServer Free/Advanced Edition - On XCP, original Linux network vs Open vSwitch - For configuring network, XenCenter vs xe commands vs ovs- commands - For using Open vSwitch, ovs- commands vs vSwitch Controlle Sorry for so many questions. Thanks! Regards, Wayne On Thu, Jun 16, 2011 at 9:53 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote:> > > On Thu, Jun 16, 2011 at 8:08 AM, Todd Deshane <todd.deshane@xen.org>wrote: > >> On Wed, Jun 15, 2011 at 6:13 AM, Wei-Chih Chen (陳偉志) >> <wcchen.tw@gmail.com> wrote: >> > Hello Everyone, >> > >> > I am new with XCP. >> > I''ve setup several hosts with XCP 1.0 and manage it through XenCenter >> and >> > command console. >> > Each host has two NICs, one (xenbr0) connected to a physical switch for >> > Internet (said sw1), the other (xenbr3) connected to a physical switch >> for >> > internal network (said sw2). >> > >> > I am trying to setup VMs and VLANs on xenbr3. >> > I created a virtual bridge by "ovs-vsctl add-br brvlan2 xenbr3 2" >> > Then add a port (portvlan2) to brvlan2: >> > ovs-vsctl add-port brvlan2 portvlan2 tag=2 >> > ifconfig vlan2 192.168.33.200 >> > Now the problem is that I do know how to attach portvlan2 to VM. >> > Could someone give me simple steps to setup VLANs using Open vSwitch and >> > attach them to VMs? >> > >> > Moreover, the newly created bridges are not shown in XenCenter. >> > If I use xe network-create, the newly created network can be shown in >> > XenCenter. >> > Is this because XenCenter uses xe command and does NOT support to show >> Open >> > vSwitch? >> > The question I wonder most is what is the difference to configure XCP >> > network using xe and ovs- commands? >> > >> >> You are going to want to use the xe commands related to networking. >> >> See >> http://docs.vmd.citrix.com/XenServer/5.6.0fp1/1.0/en_gb/reference.html#networking-concepts >> >> Hope that helps. >> >> Thanks, >> Todd >> >> >> > Thanks a lot. :) >> > >> > Regards, >> > >> > Wayne >> > >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xensource.com >> > http://lists.xensource.com/xen-users >> > >> >> >> >> -- >> Todd Deshane >> http://www.linkedin.com/in/deshantm >> http://www.xen.org/products/cloudxen.html >> http://runningxen.com/ >> > > Thank you, Todd. > The document helps a lot for XenServer network concepts and xe command > control. > > However, I would like to try Open vSwitch because it supports more features > like OpenFlow, NetFlow. > It is possible for me to use these features in the future. > Is it able to use full features of Open vSwitch in XCP 1.0? > Or XCP has not included and combined Open vSwitch completely, and it is not > suggested to use Open vSwitch in XCP 1.0? > > Thanks. > > Regards, > > Wayne > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2011-Jun-16 15:28 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
On Wed, Jun 15, 2011 at 11:34 PM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote:> Hello Everyone, > > Citrix provides vSwitch Controller to manage network across hosts. > However, it seems requiring XenServer Advanced edition, and downloading > vSwitch Controller requires My Citrix account. > Is vSwitch Controller essential for XCP to control and use full functions of > Open vSwitch? >This is a commercial controller from Citrix. Open source controllers based on NOX (http://noxrepo.org/) could provide similar functionality.> The point is that I can not figure out the relationship of > > XCP vs XenServer Free/Advanced EditionBasically XCP is an open source version of XenServer Free, but adding additional functionality to XCP can and has been done.> On XCP, original Linux network vs Open vSwitchI think Open vSwitch is the default now right? There is a command to switch to it, if not> For configuring network, XenCenter vs xe commands vs ovs- commandsXenCenter is a front end to xe, xe is a frontend to xapi. using ovs commands directly is not a good idea if you want to use the frontends since it would confuse xapi.> For using Open vSwitch, ovs- commands vs vSwitch Controlle >ovs commands support a baseline of functionality for controlling things, but if you want something more robust/advancded check out the status of nox-based open source controllers or consider looking into a commercial controller. The Open vSwitch users list is very responsive to questions. XCP is very much evolving. Start with these: http://www.xen.org/products/cloudxen.html and http://blog.xen.org/index.php/2011/06/05/xcp-on-ubuntu/ Hope that helps some. Thanks, Todd> Sorry for so many questions. > Thanks! > > Regards, > > Wayne > > On Thu, Jun 16, 2011 at 9:53 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote: >> >> >> On Thu, Jun 16, 2011 at 8:08 AM, Todd Deshane <todd.deshane@xen.org> >> wrote: >>> >>> On Wed, Jun 15, 2011 at 6:13 AM, Wei-Chih Chen (陳偉志) >>> <wcchen.tw@gmail.com> wrote: >>> > Hello Everyone, >>> > >>> > I am new with XCP. >>> > I''ve setup several hosts with XCP 1.0 and manage it through XenCenter >>> > and >>> > command console. >>> > Each host has two NICs, one (xenbr0) connected to a physical switch for >>> > Internet (said sw1), the other (xenbr3) connected to a physical switch >>> > for >>> > internal network (said sw2). >>> > >>> > I am trying to setup VMs and VLANs on xenbr3. >>> > I created a virtual bridge by "ovs-vsctl add-br brvlan2 xenbr3 2" >>> > Then add a port (portvlan2) to brvlan2: >>> > ovs-vsctl add-port brvlan2 portvlan2 tag=2 >>> > ifconfig vlan2 192.168.33.200 >>> > Now the problem is that I do know how to attach portvlan2 to VM. >>> > Could someone give me simple steps to setup VLANs using Open vSwitch >>> > and >>> > attach them to VMs? >>> > >>> > Moreover, the newly created bridges are not shown in XenCenter. >>> > If I use xe network-create, the newly created network can be shown in >>> > XenCenter. >>> > Is this because XenCenter uses xe command and does NOT support to show >>> > Open >>> > vSwitch? >>> > The question I wonder most is what is the difference to configure XCP >>> > network using xe and ovs- commands? >>> > >>> >>> You are going to want to use the xe commands related to networking. >>> >>> See >>> http://docs.vmd.citrix.com/XenServer/5.6.0fp1/1.0/en_gb/reference.html#networking-concepts >>> >>> Hope that helps. >>> >>> Thanks, >>> Todd >>> >>> >>> > Thanks a lot. :) >>> > >>> > Regards, >>> > >>> > Wayne >>> > >>> > >>> > _______________________________________________ >>> > Xen-users mailing list >>> > Xen-users@lists.xensource.com >>> > http://lists.xensource.com/xen-users >>> > >>> >>> >>> >>> -- >>> Todd Deshane >>> http://www.linkedin.com/in/deshantm >>> http://www.xen.org/products/cloudxen.html >>> http://runningxen.com/ >> >> Thank you, Todd. >> The document helps a lot for XenServer network concepts and xe command >> control. >> >> However, I would like to try Open vSwitch because it supports more >> features like OpenFlow, NetFlow. >> It is possible for me to use these features in the future. >> Is it able to use full features of Open vSwitch in XCP 1.0? >> Or XCP has not included and combined Open vSwitch completely, and it is >> not suggested to use Open vSwitch in XCP 1.0? >> >> Thanks. >> >> Regards, >> >> Wayne >> > > >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jun-17 06:50 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Dear Todd and Everyone, On Thu, Jun 16, 2011 at 11:28 PM, Todd Deshane <todd.deshane@xen.org> wrote:> On Wed, Jun 15, 2011 at 11:34 PM, Wei-Chih Chen <wcchen.tw@gmail.com> > wrote: > > Hello Everyone, > > > > Citrix provides vSwitch Controller to manage network across hosts. > > However, it seems requiring XenServer Advanced edition, and downloading > > vSwitch Controller requires My Citrix account. > > Is vSwitch Controller essential for XCP to control and use full functions > of > > Open vSwitch? > > > > This is a commercial controller from Citrix. Open source controllers > based on NOX (http://noxrepo.org/) could provide similar > functionality. >NOX looks helpful. I will try this. Is vSwitch Controller designed dedicatedly to Open vSwitch? It seems that the term "vSwitch" means Open vSwitch in vSwitch Controller User Guide. Is this correct?> > > The point is that I can not figure out the relationship of > > > > XCP vs XenServer Free/Advanced Edition > > Basically XCP is an open source version of XenServer Free, but adding > additional functionality to XCP can and has been done.> > On XCP, original Linux network vs Open vSwitch > > I think Open vSwitch is the default now right? There is a command to > switch to it, if not >Yes. Command "xe-switch-network-backend openvswitch" can enable it.> > > For configuring network, XenCenter vs xe commands vs ovs- commands > > XenCenter is a front end to xe, xe is a frontend to xapi. using ovs > commands directly is not a good idea if you want to use the frontends > since it would confuse xapi. >In the future, I may need to develop programs to automatically configure network through ovs command. I would like to make sure that *whether XCP 1.0 has completely integrated Open vSwitch.* What does "it would confuse xapi" mean? Does it mean I may confuse between operations and results of ovs command and XenCenter? Or it means that ovs command may affect xapi and cause some problems?> > > For using Open vSwitch, ovs- commands vs vSwitch Controlle > > > > ovs commands support a baseline of functionality for controlling > things, but if you want something more robust/advancded check out the > status of nox-based open source controllers or consider looking into a > commercial controller. >Accordingly, it is more convenient for me to control through open source/commercial controllers. But if I work hard, I am still able to acquire the same features using ovs command only, without aid of these controllers, right?> > The Open vSwitch users list is very responsive to questions. >OK!> > XCP is very much evolving. Start with these: > > http://www.xen.org/products/cloudxen.html > and > http://blog.xen.org/index.php/2011/06/05/xcp-on-ubuntu/ > > Hope that helps some. > > Thanks, > Todd > > Thanks for lots of information. :)> > Sorry for so many questions. > > Thanks! > > > > Regards, > > > > Wayne > > > > On Thu, Jun 16, 2011 at 9:53 AM, Wei-Chih Chen <wcchen.tw@gmail.com> > wrote: > >> > >> > >> On Thu, Jun 16, 2011 at 8:08 AM, Todd Deshane <todd.deshane@xen.org> > >> wrote: > >>> > >>> On Wed, Jun 15, 2011 at 6:13 AM, Wei-Chih Chen (陳偉志) > >>> <wcchen.tw@gmail.com> wrote: > >>> > Hello Everyone, > >>> > > >>> > I am new with XCP. > >>> > I''ve setup several hosts with XCP 1.0 and manage it through XenCenter > >>> > and > >>> > command console. > >>> > Each host has two NICs, one (xenbr0) connected to a physical switch > for > >>> > Internet (said sw1), the other (xenbr3) connected to a physical > switch > >>> > for > >>> > internal network (said sw2). > >>> > > >>> > I am trying to setup VMs and VLANs on xenbr3. > >>> > I created a virtual bridge by "ovs-vsctl add-br brvlan2 xenbr3 2" > >>> > Then add a port (portvlan2) to brvlan2: > >>> > ovs-vsctl add-port brvlan2 portvlan2 tag=2 > >>> > ifconfig vlan2 192.168.33.200 > >>> > Now the problem is that I do know how to attach portvlan2 to VM. > >>> > Could someone give me simple steps to setup VLANs using Open vSwitch > >>> > and > >>> > attach them to VMs? >Sorry for back to my original question. *How to attach VLAN/virtual bridge to VMs on XCP?*> >>> > > >>> > Moreover, the newly created bridges are not shown in XenCenter. > >>> > If I use xe network-create, the newly created network can be shown in > >>> > XenCenter. > >>> > Is this because XenCenter uses xe command and does NOT support to > show > >>> > Open > >>> > vSwitch? > >>> > The question I wonder most is what is the difference to configure XCP > >>> > network using xe and ovs- commands? > >>> > > >>> > >>> You are going to want to use the xe commands related to networking. > >>> > >>> See > >>> > http://docs.vmd.citrix.com/XenServer/5.6.0fp1/1.0/en_gb/reference.html#networking-concepts > >>> > >>> Hope that helps. > >>> > >>> Thanks, > >>> Todd > >>> > >>> > >>> > Thanks a lot. :) > >>> > > >>> > Regards, > >>> > > >>> > Wayne > >>> > > >>> > > >>> > _______________________________________________ > >>> > Xen-users mailing list > >>> > Xen-users@lists.xensource.com > >>> > http://lists.xensource.com/xen-users > >>> > > >>> > >>> > >>> > >>> -- > >>> Todd Deshane > >>> http://www.linkedin.com/in/deshantm > >>> http://www.xen.org/products/cloudxen.html > >>> http://runningxen.com/ > >> > >> Thank you, Todd. > >> The document helps a lot for XenServer network concepts and xe command > >> control. > >> > >> However, I would like to try Open vSwitch because it supports more > >> features like OpenFlow, NetFlow. > >> It is possible for me to use these features in the future. > >> Is it able to use full features of Open vSwitch in XCP 1.0? > >> Or XCP has not included and combined Open vSwitch completely, and it is > >> not suggested to use Open vSwitch in XCP 1.0? > >> > >> Thanks. > >> > >> Regards, > >> > >> Wayne > >> > > > > Regards,Wayne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
<admin@xenhive.com>
2011-Jun-17 16:23 UTC
RE: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
When somebody says "it would confuse xapi", they mean you should always go through the XAPI when configuring things on XenServer or XCP. If you try to go around the XAPI (using other tools or by editing configuration files directly), then it is possible to cause a lot of unpredictable problems to occur. For example, if you configure network outside of the XAPI, you may run into weird problems where the networking may not properly follow a VM when you live migrate a VM from one node to another. So as a general rule, you really want to be sure to do everything through the XAPI (or use a tool that goes through the XAPI). -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists. xensource.com] On Behalf Of Wei-Chih Chen Sent: Friday, June 17, 2011 1:51 AM To: Todd Deshane Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch Dear Todd and Everyone, On Thu, Jun 16, 2011 at 11:28 PM, Todd Deshane <todd.deshane@xen.org> wrote: On Wed, Jun 15, 2011 at 11:34 PM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote:> Hello Everyone, > > Citrix provides vSwitch Controller to manage network across hosts. > However, it seems requiring XenServer Advanced edition, and downloading > vSwitch Controller requires My Citrix account. > Is vSwitch Controller essential for XCP to control and use full functionsof> Open vSwitch? >This is a commercial controller from Citrix. Open source controllers based on NOX (http://noxrepo.org/) could provide similar functionality. NOX looks helpful. I will try this. Is vSwitch Controller designed dedicatedly to Open vSwitch? It seems that the term "vSwitch" means Open vSwitch in vSwitch Controller User Guide. Is this correct?> The point is that I can not figure out the relationship of > > XCP vs XenServer Free/Advanced EditionBasically XCP is an open source version of XenServer Free, but adding additional functionality to XCP can and has been done.> On XCP, original Linux network vs Open vSwitchI think Open vSwitch is the default now right? There is a command to switch to it, if not Yes. Command "xe-switch-network-backend openvswitch" can enable it.> For configuring network, XenCenter vs xe commands vs ovs- commandsXenCenter is a front end to xe, xe is a frontend to xapi. using ovs commands directly is not a good idea if you want to use the frontends since it would confuse xapi. In the future, I may need to develop programs to automatically configure network through ovs command. I would like to make sure that whether XCP 1.0 has completely integrated Open vSwitch. What does "it would confuse xapi" mean? Does it mean I may confuse between operations and results of ovs command and XenCenter? Or it means that ovs command may affect xapi and cause some problems?> For using Open vSwitch, ovs- commands vs vSwitch Controlle >ovs commands support a baseline of functionality for controlling things, but if you want something more robust/advancded check out the status of nox-based open source controllers or consider looking into a commercial controller. Accordingly, it is more convenient for me to control through open source/commercial controllers. But if I work hard, I am still able to acquire the same features using ovs command only, without aid of these controllers, right? The Open vSwitch users list is very responsive to questions. OK! XCP is very much evolving. Start with these: http://www.xen.org/products/cloudxen.html and http://blog.xen.org/index.php/2011/06/05/xcp-on-ubuntu/ Hope that helps some. Thanks, Todd Thanks for lots of information. :)> Sorry for so many questions. > Thanks! > > Regards, > > Wayne > > On Thu, Jun 16, 2011 at 9:53 AM, Wei-Chih Chen <wcchen.tw@gmail.com>wrote:>> >> >> On Thu, Jun 16, 2011 at 8:08 AM, Todd Deshane <todd.deshane@xen.org> >> wrote: >>> >>> On Wed, Jun 15, 2011 at 6:13 AM, Wei-Chih Chen (陳偉志) >>> <wcchen.tw@gmail.com> wrote: >>> > Hello Everyone, >>> > >>> > I am new with XCP. >>> > I''ve setup several hosts with XCP 1.0 and manage it through XenCenter >>> > and >>> > command console. >>> > Each host has two NICs, one (xenbr0) connected to a physical switchfor>>> > Internet (said sw1), the other (xenbr3) connected to a physical switch >>> > for >>> > internal network (said sw2). >>> > >>> > I am trying to setup VMs and VLANs on xenbr3. >>> > I created a virtual bridge by "ovs-vsctl add-br brvlan2 xenbr3 2" >>> > Then add a port (portvlan2) to brvlan2: >>> > ovs-vsctl add-port brvlan2 portvlan2 tag=2 >>> > ifconfig vlan2 192.168.33.200 >>> > Now the problem is that I do know how to attach portvlan2 to VM. >>> > Could someone give me simple steps to setup VLANs using Open vSwitch >>> > and >>> > attach them to VMs?Sorry for back to my original question. How to attach VLAN/virtual bridge to VMs on XCP?>>> > >>> > Moreover, the newly created bridges are not shown in XenCenter. >>> > If I use xe network-create, the newly created network can be shown in >>> > XenCenter. >>> > Is this because XenCenter uses xe command and does NOT support to show >>> > Open >>> > vSwitch? >>> > The question I wonder most is what is the difference to configure XCP >>> > network using xe and ovs- commands? >>> >>>> >>> You are going to want to use the xe commands related to networking. >>> >>> See >>>http://docs.vmd.citrix.com/XenServer/5.6.0fp1/1.0/en_gb/reference.html#netwo rking-concepts>>> >>> Hope that helps. >>> >>> Thanks, >>> Todd >>> >>> >>> > Thanks a lot. :) >>> > >>> > Regards, >>> > >>> > Wayne >>> > >>> > >>> > _______________________________________________ >>> > Xen-users mailing list >>> > Xen-users@lists.xensource.com >>> > http://lists.xensource.com/xen-users >>> > >>> >>> >>> >>> -- >>> Todd Deshane >>> http://www.linkedin.com/in/deshantm >>> http://www.xen.org/products/cloudxen.html >>> http://runningxen.com/ >> >> Thank you, Todd. >> The document helps a lot for XenServer network concepts and xe command >> control. >> >> However, I would like to try Open vSwitch because it supports more >> features like OpenFlow, NetFlow. >> It is possible for me to use these features in the future. >> Is it able to use full features of Open vSwitch in XCP 1.0? >> Or XCP has not included and combined Open vSwitch completely, and it is >> not suggested to use Open vSwitch in XCP 1.0? >> >> Thanks. >> >> Regards, >> >> Wayne >> >Regards, Wayne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2011-Jun-18 04:57 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
On Fri, Jun 17, 2011 at 2:50 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote:> NOX looks helpful. I will try this. > Is vSwitch Controller designed dedicatedly to Open vSwitch? > It seems that the term "vSwitch" means Open vSwitch in vSwitch Controller > User Guide. Is this correct?Yes, the vSwitch backend for XenServer/XCP is the Open vSwitch -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jun-18 09:10 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Dear Todd, admin, Everyone, Thank you for replying. This information is very important. However, it also confuses me. [?] "The term "vSwitch" means Open vSwitch in vSwitch Controller User Guide" and we can use ovs- commands to control Open vSwitch. Do these imply vSwitch Controller controls Open vSwitch through ovs- commands? (In other words, is vSwitch Controller a frontend to ovs- commands?) If yes, then vSwitch Controller would confuse XAPI because it does NOT go through XAPI. How does Citrix provide a commercial controller that may cause these problems? @@ So far, the followings are what I think: There are two kinds of XCP network: 1. *Original Linux network*: XenCenter (GUI tool)-> xe command-> XAPI (Thanks for information from Todd) -> Linux network 2. *Open vSwitch* (default for XCP): vSwitch Controller (commercial GUI tool)-> ovs- command-> Open vSwitch (prone to problems)>From aspects of stability, scalability and the amount of features provided,which one is recommended? Perhaps I misunderstand something. I am grateful to anyone for making these clear. :) Thank you very much. Regards, Wayne (From admin@xenhive.com:) When somebody says "it would confuse xapi", they mean you should always go through the XAPI when configuring things on XenServer or XCP. If you try to go around the XAPI (using other tools or by editing configuration files directly), then it is possible to cause a lot of unpredictable problems to occur. For example, if you configure network outside of the XAPI, you may run into weird problems where the networking may not properly follow a VM when you live migrate a VM from one node to another. So as a general rule, you really want to be sure to do everything through the XAPI (or use a tool that goes through the XAPI). On Sat, Jun 18, 2011 at 12:57 PM, Todd Deshane <todd.deshane@xen.org> wrote:> On Fri, Jun 17, 2011 at 2:50 AM, Wei-Chih Chen <wcchen.tw@gmail.com> > wrote: > > NOX looks helpful. I will try this. > > Is vSwitch Controller designed dedicatedly to Open vSwitch? > > It seems that the term "vSwitch" means Open vSwitch in vSwitch Controller > > User Guide. Is this correct? > > Yes, the vSwitch backend for XenServer/XCP is the Open vSwitch > > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/ >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2011-Jun-18 14:51 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
On Sat, Jun 18, 2011 at 5:10 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote:> Dear Todd, admin, Everyone, > > Thank you for replying. > This information is very important. However, it also confuses me. [?] > > "The term "vSwitch" means Open vSwitch in vSwitch Controller User Guide"and we can use ovs- commands to control Open vSwitch. > Do these imply vSwitch Controller controls Open vSwitch through ovs- > commands? > (In other words, is vSwitch Controller a frontend to ovs- commands?) >No, I don''t think it does. the vSwitch Controller is proprietary, but likely it used the OpenFlow protocol to control the underlying Open vSwitch switches.> If yes, then vSwitch Controller would confuse XAPI because it does NOT go > through XAPI. > How does Citrix provide a commercial controller that may cause these > problems? @@ > >See above.> So far, the followings are what I think: > There are two kinds of XCP network: > 1. *Original Linux network*: XenCenter (GUI tool)-> xe command-> XAPI > (Thanks for information from Todd) -> Linux network > 2. *Open vSwitch* (default for XCP): vSwitch Controller (commercial GUI > tool)-> ovs- command-> Open vSwitch (prone to problems) >This second one is not quite right. It should read: some vSwitch Controller (commercial from companies like Citrix or open source using NOX)-> OpenFlow protocol-> Open vSwitch switches> From aspects of stability, scalability and the amount of features provided, > which one is recommended? >Either use the XenCenter/OpenXenManager front ends or xe command directly to manage the network. OR Use a commercial or open source controller that is designed to interact properly with XCP/xapi/Open vSwitch. Don''t use ovs commands directly since that will likely make the xapi configuration be incorrect.> Perhaps I misunderstand something. > I am grateful to anyone for making these clear. :) > > Thank you very much. > Regards, > Wayne > > (From admin@xenhive.com:) > When somebody says "it would confuse xapi", they mean you should always go > through the XAPI when configuring things on XenServer or XCP. If you try to > go around the XAPI (using other tools or by editing configuration files > directly), then it is possible to cause a lot of unpredictable problems to > occur. For example, if you configure network outside of the XAPI, you may > run into weird problems where the networking may not properly follow a VM > when you live migrate a VM from one node to another. So as a general rule, > you really want to be sure to do everything through the XAPI (or use a tool > that goes through the XAPI). > > > On Sat, Jun 18, 2011 at 12:57 PM, Todd Deshane <todd.deshane@xen.org>wrote: > >> On Fri, Jun 17, 2011 at 2:50 AM, Wei-Chih Chen <wcchen.tw@gmail.com> >> wrote: >> > NOX looks helpful. I will try this. >> > Is vSwitch Controller designed dedicatedly to Open vSwitch? >> > It seems that the term "vSwitch" means Open vSwitch in vSwitch >> Controller >> > User Guide. Is this correct? >> >> Yes, the vSwitch backend for XenServer/XCP is the Open vSwitch >> >> >> -- >> Todd Deshane >> http://www.linkedin.com/in/deshantm >> http://www.xen.org/products/cloudxen.html >> http://runningxen.com/ >> > >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jun-18 15:59 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Dear Todd and Everyone, On Sat, Jun 18, 2011 at 10:51 PM, Todd Deshane <todd.deshane@xen.org> wrote:> > > On Sat, Jun 18, 2011 at 5:10 AM, Wei-Chih Chen <wcchen.tw@gmail.com>wrote: > >> Dear Todd, admin, Everyone, >> >> Thank you for replying. >> This information is very important. However, it also confuses me. [?] >> >> "The term "vSwitch" means Open vSwitch in vSwitch Controller User Guide"and we can use ovs- commands to control Open vSwitch. >> Do these imply vSwitch Controller controls Open vSwitch through ovs- >> commands? >> (In other words, is vSwitch Controller a frontend to ovs- commands?) >> > > No, I don''t think it does. the vSwitch Controller is proprietary, but > likely it used the OpenFlow protocol to control the underlying Open vSwitch > switches. > > >> If yes, then vSwitch Controller would confuse XAPI because it does NOT go >> through XAPI. >> How does Citrix provide a commercial controller that may cause these >> problems? @@ >> >> > See above. > > >> So far, the followings are what I think: >> There are two kinds of XCP network: >> 1. *Original Linux network*: XenCenter (GUI tool)-> xe command-> XAPI >> (Thanks for information from Todd) -> Linux network >> 2. *Open vSwitch* (default for XCP): vSwitch Controller (commercial GUI >> tool)-> ovs- command-> Open vSwitch (prone to problems) >> > > This second one is not quite right. > > It should read: > some vSwitch Controller (commercial from companies like Citrix or open > source using NOX)-> OpenFlow protocol-> Open vSwitch switches > > >> From aspects of stability, scalability and the amount of features >> provided, which one is recommended? >> > > Either use the XenCenter/OpenXenManager front ends or xe command directly > to manage the network. > > OR > > Use a commercial or open source controller that is designed to interact > properly with XCP/xapi/Open vSwitch. > > Don''t use ovs commands directly since that will likely make the xapi > configuration be incorrect. > >Thank you. Clear concepts and useful information. :) I have to choose one from the two:>From openvswitch.org, Open vSwitch provides many features (such as NetFlow,Fine-grained min/max rate QoS) that original Linux network can not reach, because I do not see these features described in XenServer 5.6 FP1 Administrator Guide. It seems that Open vSwitch is more powerful. In my future environment, there may be a large number of hosts, and VMs need to migrate to another host with its original network settings (scalability and VM mobility issues). Management, performance and security are also important issues. In the consideration of the above requirements, Open vSwitch seems better for me. Or does anyone have other suggestions? Thanks.> > >> Perhaps I misunderstand something. >> I am grateful to anyone for making these clear. :) >> >> Thank you very much. >> Regards, >> Wayne >> >> (From admin@xenhive.com:) >> When somebody says "it would confuse xapi", they mean you should always go >> through the XAPI when configuring things on XenServer or XCP. If you try to >> go around the XAPI (using other tools or by editing configuration files >> directly), then it is possible to cause a lot of unpredictable problems to >> occur. For example, if you configure network outside of the XAPI, you may >> run into weird problems where the networking may not properly follow a VM >> when you live migrate a VM from one node to another. So as a general rule, >> you really want to be sure to do everything through the XAPI (or use a tool >> that goes through the XAPI). >> >> >> On Sat, Jun 18, 2011 at 12:57 PM, Todd Deshane <todd.deshane@xen.org>wrote: >> >>> On Fri, Jun 17, 2011 at 2:50 AM, Wei-Chih Chen <wcchen.tw@gmail.com> >>> wrote: >>> > NOX looks helpful. I will try this. >>> > Is vSwitch Controller designed dedicatedly to Open vSwitch? >>> > It seems that the term "vSwitch" means Open vSwitch in vSwitch >>> Controller >>> > User Guide. Is this correct? >>> >>> Yes, the vSwitch backend for XenServer/XCP is the Open vSwitch >>> >>> >>> -- >>> Todd Deshane >>> http://www.linkedin.com/in/deshantm >>> http://www.xen.org/products/cloudxen.html >>> http://runningxen.com/ >>> >> >> > > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/ >Regards, Wayne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2011-Jun-19 01:33 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
On Sat, Jun 18, 2011 at 11:59 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote:> I have to choose one from the two: > From openvswitch.org, Open vSwitch provides many features (such as NetFlow, Fine-grained min/max rate QoS) that original Linux network can not reach, because I do not see these features described in XenServer 5.6 FP1 Administrator Guide. > It seems that Open vSwitch is more powerful. > > In my future environment, there may be a large number of hosts, and VMs need to migrate to another host with its original network settings (scalability and VM mobility issues). > Management, performance and security are also important issues. > In the consideration of the above requirements, Open vSwitch seems better for me. Or does anyone have other suggestions?I think Open vSwitch-based solutions are what you are going to want to use. I suggest that you also read up on OpenFlow and OpenStack Here are some good resources: http://networkheresy.wordpress.com/ http://wiki.openstack.org/Network https://blueprints.launchpad.net/quantum/+spec/quantum-openvswitch-plugin Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jun-19 01:39 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Dear Todd, Thank you! You help me a lot. [?] Regards, Wayne On Sun, Jun 19, 2011 at 9:33 AM, Todd Deshane <todd.deshane@xen.org> wrote:> On Sat, Jun 18, 2011 at 11:59 AM, Wei-Chih Chen <wcchen.tw@gmail.com> > wrote: > > I have to choose one from the two: > > From openvswitch.org, Open vSwitch provides many features (such as > NetFlow, Fine-grained min/max rate QoS) that original Linux network can not > reach, because I do not see these features described in XenServer 5.6 FP1 > Administrator Guide. > > It seems that Open vSwitch is more powerful. > > > > In my future environment, there may be a large number of hosts, and VMs > need to migrate to another host with its original network settings > (scalability and VM mobility issues). > > Management, performance and security are also important issues. > > In the consideration of the above requirements, Open vSwitch seems better > for me. Or does anyone have other suggestions? > > I think Open vSwitch-based solutions are what you are going to want to use. > > I suggest that you also read up on OpenFlow and OpenStack > > Here are some good resources: > > http://networkheresy.wordpress.com/ > http://wiki.openstack.org/Network > https://blueprints.launchpad.net/quantum/+spec/quantum-openvswitch-plugin > > Thanks, > Todd > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/ >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jul-04 11:05 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Hello Everyone, Sorry that I still have many questions about network of XCP 1.0 . Can Linux Bridge and Open vSwitch coexist and work at the same time? The command "xe-switch-network-backend openvswitch" enables vSwitch. This means *"just turn on vSwitch" or "turn on vSwitch and turn off Linux Bridge"?* "A network is a virtual Ethernet switch on a XenServer host." *Does the virtual Ethernet switch the same as the virtual bridge created by "ovs-vsctl add-br"?*>From administrator''s guide, there are 4 types of network in XenServer.It seems that only cross-server private network needs Open vSwitch, which is managed by vSwitch Controller. (Another 3 networks use Linux bridge?) However, XCP does not support cross-server private network. I think it is because vSwitch Controller is a commercial product. Does this mean Citrix does not provide XCP users a way/tool to control Open vSwitch? Or* Citrix does not plan to bring benefits of Open vSwitch to XCP, therefore does not integrate Open vSwitch and XCP completely?* XCP users only have to use ovs- commands (from Todd and admin@xenhive.com, ovs commands may confuse XAPI) or OpenFlow controllers to complete what vSwitch Controller does? Thanks a lot. Regards, Wayne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
George Shuklin
2011-Jul-04 17:18 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
I could not reply to all question but look to the /etc/xensource/scripts/vif - it contain shell script executed by xapi during vif-plug/unplug operations. В Пнд, 04/07/2011 в 19:05 +0800, Wei-Chih Chen пишет:> Sorry that I still have many questions about network of XCP 1.0 . > > Can Linux Bridge and Open vSwitch coexist and work at the same time? > The command "xe-switch-network-backend openvswitch" enables vSwitch. > This means "just turn on vSwitch" or "turn on vSwitch and turn off > Linux Bridge"? > > "A network is a virtual Ethernet switch on a XenServer host." > Does the virtual Ethernet switch the same as the virtual bridge > created by "ovs-vsctl add-br"? > > From administrator''s guide, there are 4 types of network in XenServer. > It seems that only cross-server private network needs Open vSwitch, > which is managed by vSwitch Controller. > (Another 3 networks use Linux bridge?) > However, XCP does not support cross-server private network. > I think it is because vSwitch Controller is a commercial product. > Does this mean Citrix does not provide XCP users a way/tool to control > Open vSwitch? > Or Citrix does not plan to bring benefits of Open vSwitch to XCP, > therefore does not integrate Open vSwitch and XCP completely? > XCP users only have to use ovs- commands (from Todd and > admin@xenhive.com, ovs commands may confuse XAPI) or OpenFlow > controllers to complete what vSwitch Controller does?_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jul-05 12:20 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Dear George and Everyone, I''ve checked that script. It surprises me that it uses ovs-vsctl. I thought XAPI controls Linux bridge directly instead of using newly integrated ovs- commands. However, it seems that some of xe commands (XAPI) also use ovs- commands. Therefore, some contents mentioned in this discussion list before has to be modified*?** 1. Original Linux network: XenCenter (GUI tool)-> xe command-> XAPI -> Linux Bridge or Open vSwitch (depeding on what is configured ? ) 2. (from Todd) some vSwitch Controller (commercial from companies like Citrix or open source using NOX)-> OpenFlow protocol-> Open vSwitch switches * On Tue, Jul 5, 2011 at 1:18 AM, George Shuklin <george.shuklin@gmail.com>wrote:> I could not reply to all question but look to > the /etc/xensource/scripts/vif - it contain shell script executed by > xapi during vif-plug/unplug operations. > > В Пнд, 04/07/2011 в 19:05 +0800, Wei-Chih Chen пишет: > > > Sorry that I still have many questions about network of XCP 1.0 . > > > > Can Linux Bridge and Open vSwitch coexist and work at the same time? > > The command "xe-switch-network-backend openvswitch" enables vSwitch. > > This means "just turn on vSwitch" or "turn on vSwitch and turn off > > Linux Bridge"? > > > > "A network is a virtual Ethernet switch on a XenServer host." > > Does the virtual Ethernet switch the same as the virtual bridge > > created by "ovs-vsctl add-br"? >*It seems they are the same? *The original problem is virtual bridges created with ovs-vsctl directly can not be shown in XenCenter. It is said using ovs- commands is not recommended. Therefore, if the *virtual Ethernet switch* and the *virtual bridge created by "ovs-vsctl add-br"* are the same, I can first create virtual switches through XAPI (i.e. XenCenter or xe commands). Then the remaining managements are done through *XAPI or OpenFlow* (if XAPI does not support this configuration). Is the method correct?> > > > From administrator''s guide, there are 4 types of network in XenServer. > > It seems that only cross-server private network needs Open vSwitch, > > which is managed by vSwitch Controller. > > (Another 3 networks use Linux bridge?) > > However, XCP does not support cross-server private network. > > I think it is because vSwitch Controller is a commercial product. > > Does this mean Citrix does not provide XCP users a way/tool to control > > Open vSwitch? > > Or Citrix does not plan to bring benefits of Open vSwitch to XCP, > > therefore does not integrate Open vSwitch and XCP completely? > > XCP users only have to use ovs- commands (from Todd and > > admin@xenhive.com, ovs commands may confuse XAPI) or OpenFlow > > controllers to complete what vSwitch Controller does? > > Thanks a lot.Regards, Wayne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2011-Jul-05 22:51 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
On Mon, Jul 4, 2011 at 7:05 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote:> Hello Everyone, > > Sorry that I still have many questions about network of XCP 1.0 . > > Can Linux Bridge and Open vSwitch coexist and work at the same time?No, the modules conflict.> The command "xe-switch-network-backend openvswitch" enables vSwitch. > This means "just turn on vSwitch" or "turn on vSwitch and turn off Linux > Bridge"?The latter.> > "A network is a virtual Ethernet switch on a XenServer host." > Does the virtual Ethernet switch the same as the virtual bridge created by > "ovs-vsctl add-br"? >which virtual Ethernet switch is being referred to here? OVS switches are compatible with standard linux bridges, but OVS adds more features. You may want to discuss the finer points of this with the ovs-discuss mailing list.> From administrator''s guide, there are 4 types of network in XenServer. > It seems that only cross-server private network needs Open vSwitch, which is > managed by vSwitch Controller. > (Another 3 networks use Linux bridge?) > However, XCP does not support cross-server private network. > I think it is because vSwitch Controller is a commercial product. > Does this mean Citrix does not provide XCP users a way/tool to control Open > vSwitch?Right, the Citrix vSwitch Controller is a commercial product (as far as I know). My guess is that it doesn''t come as a standalone product, but instead is included with the commercial (non-free) version of Citrix XenServer. You could ask in the Citrix XenServer forums for clarification/confirmation.> Or Citrix does not plan to bring benefits of Open vSwitch to XCP, therefore > does not integrate Open vSwitch and XCP completely?I think that it would be nice for the possibility of adding on the commercial controller to XCP, but as of now I don''t think there is any support for that.> XCP users only have to use ovs- commands (from Todd and admin@xenhive.com, > ovs commands may confuse XAPI) or OpenFlow controllers to complete what > vSwitch Controller does? >Right. At this point on XCP you are probably forced to roll your own controller solution. You should discuss this on the nox, openflow, and open vSwitch mailing lists for what your options are. see also: http://wiki.xen.org/xenwiki/XCP/XenServer_Feature_Matrix I don''t actually see the vSwitch controller on there as an item, but I think we should sort this point out and add it. Thanks, Todd> Thanks a lot. > > Regards, > Wayne > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2011-Jul-05 22:59 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
On Tue, Jul 5, 2011 at 8:20 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote:> Dear George and Everyone, > > I''ve checked that script. > It surprises me that it uses ovs-vsctl. > I thought XAPI controls Linux bridge directly instead of using newly > integrated ovs- commands. > However, it seems that some of xe commands (XAPI) also use ovs- commands. >When xe uses the ovs commands it is often working with the bridge as directly as it needs to (i.e. there are ovs commands that accomplish the desired result).> Therefore, some contents mentioned in this discussion list before has to be > modified? > 1. Original Linux network: XenCenter (GUI tool)-> xe command-> XAPI -> Linux > Bridge or Open vSwitch (depeding on what is configured ? ) > 2. (from Todd) some vSwitch Controller (commercial from companies like > Citrix or open source using NOX)-> OpenFlow protocol-> Open vSwitch switches > > On Tue, Jul 5, 2011 at 1:18 AM, George Shuklin <george.shuklin@gmail.com> > wrote: >> >> I could not reply to all question but look to >> the /etc/xensource/scripts/vif - it contain shell script executed by >> xapi during vif-plug/unplug operations. >> >> В Пнд, 04/07/2011 в 19:05 +0800, Wei-Chih Chen пишет: >> >> > Sorry that I still have many questions about network of XCP 1.0 . >> > >> > Can Linux Bridge and Open vSwitch coexist and work at the same time? >> > The command "xe-switch-network-backend openvswitch" enables vSwitch. >> > This means "just turn on vSwitch" or "turn on vSwitch and turn off >> > Linux Bridge"? >> > >> > "A network is a virtual Ethernet switch on a XenServer host." >> > Does the virtual Ethernet switch the same as the virtual bridge >> > created by "ovs-vsctl add-br"? > > It seems they are the same?> Then the remaining managements are done through XAPI or OpenFlow (if XAPI > does not support this configuration). > Is the method correct?I think this seems OK. Does the previous response that I sent answer this question better? Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jul-07 08:20 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Dear Todd and Everyone, On Wed, Jul 6, 2011 at 6:51 AM, Todd Deshane <todd.deshane@xen.org> wrote:> On Mon, Jul 4, 2011 at 7:05 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote: > > Hello Everyone, > > > > Sorry that I still have many questions about network of XCP 1.0 . > > > > Can Linux Bridge and Open vSwitch coexist and work at the same time? > > No, the modules conflict. > > > The command "xe-switch-network-backend openvswitch" enables vSwitch. > > This means "just turn on vSwitch" or "turn on vSwitch and turn off Linux > > Bridge"? > The latter. > > > > > > "A network is a virtual Ethernet switch on a XenServer host." > > Does the virtual Ethernet switch the same as the virtual bridge created > by > > "ovs-vsctl add-br"? > > > which virtual Ethernet switch is being referred to here? OVS switches > are compatible with standard linux bridges, but OVS adds more > features. You may want to discuss the finer points of this with the > ovs-discuss mailing list. >XenServer 5.6 FP1 Admin Guide (p.72) defines "network", which is one type of server-side software objects which represent networking entities. "*A network, which is a virtual Ethernet switch on a XenServer host. Network objects have a name and description, a globally unique UUID, and the collection of VIFs and PIFs connected to them.*" OK, I will discuss with ovs-discuss mailing list.> > From administrator''s guide, there are 4 types of network in XenServer. > > It seems that only cross-server private network needs Open vSwitch, which > is > > managed by vSwitch Controller. > > (Another 3 networks use Linux bridge?) > > However, XCP does not support cross-server private network. > > I think it is because vSwitch Controller is a commercial product. > > Does this mean Citrix does not provide XCP users a way/tool to control > Open > > vSwitch? > > Right, the Citrix vSwitch Controller is a commercial product (as far > as I know). My guess is that it doesn''t come as a standalone product, > but instead is included with the commercial (non-free) version of > Citrix XenServer. You could ask in the Citrix XenServer forums for > clarification/confirmation. > >From Citrix forum http://forums.citrix.com/message.jspa?messageID=1523064 ,it vSwitch Controller can be downloaded as a .xva file after log in My Citrix. I''ve donwloaded and imported as VM. However, it is started with errors: "This VM cannot be started, as its network interfaces could not be connected. One of the NICs is in use elsewhere.">From XenCenter, the field "Active" of any attached network is "No", butthose of other VMs are "Yes". Maybe I do not meet requirements of vSwitch Controller, and will try more. Or maybe it detects that the host is XCP and prevents from starting on free edition of XenServer > Or Citrix does not plan to bring benefits of Open vSwitch to XCP,> therefore > > does not integrate Open vSwitch and XCP completely? > > I think that it would be nice for the possibility of adding on the > commercial controller to XCP, but as of now I don''t think there is any > support for that. > > > XCP users only have to use ovs- commands (from Todd and > admin@xenhive.com, > > ovs commands may confuse XAPI) or OpenFlow controllers to complete what > > vSwitch Controller does? > > > > Right. At this point on XCP you are probably forced to roll your own > controller solution. You should discuss this on the nox, openflow, and > open vSwitch mailing lists for what your options are. >I am trying Beacon, which a Java-based OpenFlow controller, because my developing language is Java.> > see also: > http://wiki.xen.org/xenwiki/XCP/XenServer_Feature_Matrix > > I don''t actually see the vSwitch controller on there as an item, but I > think we should sort this point out and add it. >There is a feature "Distributed virtual switching management tool" at that wiki page. I think it is vSwitch Controller.> > Thanks, > Todd > > > Thanks a lot. > > > > Regards, > > Wayne > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/ >Thanks. Regards, Wayne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wei-Chih Chen
2011-Jul-07 08:34 UTC
Re: [Xen-users] [XCP] XCP network and VLAN by Open vSwitch
Dear Todd and Everyone, On Wed, Jul 6, 2011 at 6:59 AM, Todd Deshane <todd.deshane@xen.org> wrote:> On Tue, Jul 5, 2011 at 8:20 AM, Wei-Chih Chen <wcchen.tw@gmail.com> wrote: > > Dear George and Everyone, > > > > I''ve checked that script. > > It surprises me that it uses ovs-vsctl. > > I thought XAPI controls Linux bridge directly instead of using newly > > integrated ovs- commands. > > However, it seems that some of xe commands (XAPI) also use ovs- commands. > > > > When xe uses the ovs commands it is often working with the bridge as > directly as it needs to (i.e. there are ovs commands that accomplish > the desired result). > > > Therefore, some contents mentioned in this discussion list before has to > be > > modified? > > 1. Original Linux network: XenCenter (GUI tool)-> xe command-> XAPI -> > Linux > > Bridge or Open vSwitch (depeding on what is configured ? ) > > 2. (from Todd) some vSwitch Controller (commercial from companies like > > Citrix or open source using NOX)-> OpenFlow protocol-> Open vSwitch > switches > > > > On Tue, Jul 5, 2011 at 1:18 AM, George Shuklin <george.shuklin@gmail.com > > > > wrote: > >> > >> I could not reply to all question but look to > >> the /etc/xensource/scripts/vif - it contain shell script executed by > >> xapi during vif-plug/unplug operations. > >> > >> В Пнд, 04/07/2011 в 19:05 +0800, Wei-Chih Chen пишет: > >> > >> > Sorry that I still have many questions about network of XCP 1.0 . > >> > > >> > Can Linux Bridge and Open vSwitch coexist and work at the same time? > >> > The command "xe-switch-network-backend openvswitch" enables vSwitch. > >> > This means "just turn on vSwitch" or "turn on vSwitch and turn off > >> > Linux Bridge"? > >> > > >> > "A network is a virtual Ethernet switch on a XenServer host." > >> > Does the virtual Ethernet switch the same as the virtual bridge > >> > created by "ovs-vsctl add-br"? > > > > It seems they are the same? > > > > Then the remaining managements are done through XAPI or OpenFlow (if XAPI > > does not support this configuration). > > Is the method correct? > > I think this seems OK. Does the previous response that I sent answer > this question better? >Do you mean this? "*Either use the XenCenter/OpenXenManager front ends or xe command directly to manage the network.* * * *OR* * * *Use a commercial or open source controller that is designed to interact properly with XCP/xapi/Open vSwitch.*" My current requirements are VLANs. However, I need features of Open vSwitch in the future. And it takes time to study OpenFlow and controllers. Therefore, now, I plan to create networks of VLANs with Java SDK (XAPI). In the future, open source OpenFlow controller (current choice is Beacon) is adopted in order to meet more requirements.> > Thanks, > Todd > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/ >Thanks. Regards, Wayne _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users