[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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@xxxxxxxxx> 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@xxxxxxxxxxx, ovs commands may confuse XAPI) or OpenFlow
> controllers to complete what vSwitch Controller does?

Thanks a lot.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.