Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-11 Thread
On Tue, Jul 12, 2011 at 2:35 AM, Ben Pfaff  wrote:

> On Tue, Jul 12, 2011 at 02:28:04AM +0800, ??? wrote:
> > my situation:
> >   with KVM, both HOST and GUESTs work fine.
> >   with XEN, HOST's configuration is okay, but GUESTs (aka Dom-U), can't
> > start as normal.
> >
> > could anyone of you give me some examples, or just hint?
>
> I don't use Xen outside of XenServer, so I don't have hints.
>
> I keep hoping that someone will submit a set of Xen integration
> scripts or instructions.  No one has yet.
>

Well, I'll keep studying how to make it work... hope someone could share
his/her experience with Xen,

anyway, you do really help a lots, thanks for your help, thanks!!!
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-11 Thread Ben Pfaff
On Tue, Jul 12, 2011 at 02:28:04AM +0800, ??? wrote:
> my situation:
>   with KVM, both HOST and GUESTs work fine.
>   with XEN, HOST's configuration is okay, but GUESTs (aka Dom-U), can't
> start as normal.
> 
> could anyone of you give me some examples, or just hint?

I don't use Xen outside of XenServer, so I don't have hints.

I keep hoping that someone will submit a set of Xen integration
scripts or instructions.  No one has yet.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-11 Thread
On Tue, Jul 12, 2011 at 12:32 AM, Ben Pfaff  wrote:

> On Sun, Jul 10, 2011 at 04:45:23AM +0800, ??? wrote:
> > Is these commands right for Dom-0's configuration?
>
> Looks good.
>
> > If it were right for Dom-0, what will be my next step for Dom-U's network
> > configuration, any suggestion?
>
> Normally to configure a DomU you would add it to the bridge:
>
>ovs-vsctl add-port vbr0 vif0.0
>
> and then do the remaining configuration (ifconfig or dhclient) inside
> the DomU.
>

I've tried all the steps again and agin today.

OVS with KVM, all the step are fine, works perfectly, both HOST and GUESTs.

with the commands, mentioned in INSTALL.bridge document, all networks looks
fine.

but when I try to fight with XEN, I got confused, I don't know which scripts
I should modified.

in the directory " /etc/xen/scripts/* " there are so many scripts may impact
the network startup,

my situation:
  with KVM, both HOST and GUESTs work fine.
  with XEN, HOST's configuration is okay, but GUESTs (aka Dom-U), can't
start as normal.

could anyone of you give me some examples, or just hint?

I would appreciate if you could give some hints, thanks for your help.


Thanks.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-11 Thread Ben Pfaff
On Sun, Jul 10, 2011 at 04:45:23AM +0800, ??? wrote:
> Is these commands right for Dom-0's configuration?

Looks good.

> If it were right for Dom-0, what will be my next step for Dom-U's network
> configuration, any suggestion?

Normally to configure a DomU you would add it to the bridge:

ovs-vsctl add-port vbr0 vif0.0

and then do the remaining configuration (ifconfig or dhclient) inside
the DomU.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-09 Thread
On Sun, Jul 10, 2011 at 4:11 AM, Ben Pfaff  wrote:

> It's probably a bridge port on a Linux bridge.  You need to disable
> whatever is creating that and make it use Open vSwitch instead.
>
> You need to do that before anything else will make sense.
>


Thanks for answering my question, that's really help for me a lot, Ben.

After disable Linux bridge, it goes smoothly as I expect.


Here is my steps:

After the steps mention in INSTALL.Linux

$ ovs-vsctl list-br
to make sure there is no virtual bridge created by OVS

$ /sbin/ifconfig
then I got the devices info:
- eth0
- vif0.0

# su -

# ifconfig eth0 0.0.0.0

# ovs-vsctl add-br vbr0

# ovs-vsctl add-port vbr0 eth0

# ovs-vsctl add-port vbr0 vif0.0

--- for Static IP:

# ifconfig vbr0 aa.bb.cc.dd netmask 255.255.255.0 up

# route add default gw aa.bb.cc.254

--- for DHCP:

# dhclient vbr0


then, follow the steps INSTALL.Bridge

Is these commands right for Dom-0's configuration?


If it were right for Dom-0, what will be my next step for Dom-U's network
configuration, any suggestion?


Again, thanks a lot !
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-09 Thread Ben Pfaff
On Sun, Jul 10, 2011 at 03:24:37AM +0800, 沒 wrote:
> On Sun, Jul 10, 2011 at 2:36 AM, Ben Pfaff  wrote:
> 
> > On Sun, Jul 10, 2011 at 02:26:01AM +0800, 沒 wrote:
> > > * first question *
> > > if I want to make Domain-0 link to be connected, which port should I
> > attach
> > > to the virtual bridge... eth0? or peth0?
> >
> > I don't understand this question.  You have one Ethernet port.  Attach
> > that one to vbr0.  Where does the other one come from?
> >
> 
> yes, I have a ethernet port named eth0 (when it is start without XEN kernel)
> 
> with XEN kernel startup, original eth0 was renamed as peth0, and comes out a
> fake one "eth0"

It's probably a bridge port on a Linux bridge.  You need to disable
whatever is creating that and make it use Open vSwitch instead.

You need to do that before anything else will make sense.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-09 Thread
On Sun, Jul 10, 2011 at 2:36 AM, Ben Pfaff  wrote:

> On Sun, Jul 10, 2011 at 02:26:01AM +0800, 沒 wrote:
> > * first question *
> > if I want to make Domain-0 link to be connected, which port should I
> attach
> > to the virtual bridge... eth0? or peth0?
>
> I don't understand this question.  You have one Ethernet port.  Attach
> that one to vbr0.  Where does the other one come from?
>

yes, I have a ethernet port named eth0 (when it is start without XEN kernel)

with XEN kernel startup, original eth0 was renamed as peth0, and comes out a
fake one "eth0"

and the "vbr0" is the name of my virtual bridge, created by the command "
ovs-vsctl add-br vbr0 "


>
>
> * second question *
> > do I need to attach "vif0.0" to the virtual bridge "vbr0"? (vif0.0 ->
> > interface of Domain0's eth0)
> > or there is no need to do so, just attach eth0 / peth0?
>
> If you want packets from vif0.0 to be able to reach eth0, and vice
> versa, then attach both of them to the same bridge.
>

so, I need to attach vifX.Y to my vbr0, and peth0 as well, am I correct?


> > * third question *
> > how can I attach "vif1.0" to "vbr0" before Domain-1 is been created?
>
> Normally you would attach vif1.0 to vbr0 after Domain-1 is created.
>

but, here is the point, (mention in Q4 reply)
how can VMM (Virtual Machine Manager) start a VM with a virtual bridge which
is created by OVS ?


> > * forth question *
> > with KVM support, INSTALL.KVM says that need to add scripts ovs-ifup /
> > ovs-ifdown,
> > then, with XEN support system, do we need to write scripts for ifup /
> ifdown
> > commands?
>
> Yes, you need to make the corresponding changes to Xen.
>

I've try many times, but I failed, VMM gave me error messages says:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/createnet.py", line 351, in
finish
self.conn.create_network(xml)
  File "/usr/share/virt-manager/virtManager/connection.py", line 743, in
create_network
net.create()
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 866, in create
if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirtError: cannot create bridge 'virbr1': Package not installed


thanks for your reply
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-09 Thread Sébastien Riccio

On 09.07.2011 20:51, Ben Pfaff wrote:

On Sat, Jul 09, 2011 at 08:44:34PM +0200, Sébastien Riccio wrote:

Actually i'm interested to this question too. I'm trying to modify
xen network scripts in
order to have it bind the vif to the right bridge and with the right
vlan tag (if using a
bridge with trunk ports).

It's a question that comes up repeatedly, but we don't get a lot of
answers.

If you come up with good working scripts or instructions, we'd be happy
to include them with OVS.



I'm not that far from the solution, but still working on it to build 
scripts that work
out of the box and work for almost every situations, such as vifs bound 
to "normal"
virtual switches and, vifs bound to trunk virtual switchs with the right 
vlan tag,

internal networks between virtual machines, etc.

If I can get something that works well, I'll post it here with pleasure.


___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-09 Thread Ben Pfaff
On Sat, Jul 09, 2011 at 08:44:34PM +0200, Sébastien Riccio wrote:
> Actually i'm interested to this question too. I'm trying to modify
> xen network scripts in
> order to have it bind the vif to the right bridge and with the right
> vlan tag (if using a
> bridge with trunk ports).

It's a question that comes up repeatedly, but we don't get a lot of
answers.

If you come up with good working scripts or instructions, we'd be happy
to include them with OVS.

___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-09 Thread Sébastien Riccio

On 09.07.2011 20:44, Sébastien Riccio wrote:
Actually i'm interested to this question too. I'm trying to modify xen 
network scripts in
order to have it bind the vif to the right bridge and with the right 
vlan tag (if using a

bridge with trunk ports).

I found that slackware has some interesting scripts here:

http://palembang-slackers.org/linuxupdate/pub/slackware/addon/slackbuilds/13.1/network/openvswitch/xen/ 



but I dont really understand how they get it to work, especially for 
the vlan part.


They have a $tag check in vif-openvswitch but the xen configuration 
files don't allow the use of the tag attribute

for a vif:

example vif definition:
vif = [ 'ip=10.111.5.10, bridge=trunk0, tag=85, vifname=vm1.0' ]

myhost# xm create -c /cloud/data2/configs/vm1.cfg
Using config file "/cloud/data2/configs/vm1.cfg".
Error: Invalid vif option: tag

Althought I think that this topic is more xen oriented and maybe 
should be addressed
the the xen mailing lists, I just wanted to share that info and know 
if someone around

has ideas or experience with xen (not citrix's one) + openvswitch.

Sébastien

On 09.07.2011 20:36, Ben Pfaff wrote:

On Sun, Jul 10, 2011 at 02:26:01AM +0800, 沒 wrote:

* first question *
if I want to make Domain-0 link to be connected, which port should I 
attach

to the virtual bridge... eth0? or peth0?

I don't understand this question.  You have one Ethernet port.  Attach
that one to vbr0.  Where does the other one come from?


* second question *
do I need to attach "vif0.0" to the virtual bridge "vbr0"? (vif0.0 ->
interface of Domain0's eth0)
or there is no need to do so, just attach eth0 / peth0?

If you want packets from vif0.0 to be able to reach eth0, and vice
versa, then attach both of them to the same bridge.


* third question *
how can I attach "vif1.0" to "vbr0" before Domain-1 is been created?

Normally you would attach vif1.0 to vbr0 after Domain-1 is created.


* forth question *
with KVM support, INSTALL.KVM says that need to add scripts ovs-ifup /
ovs-ifdown,
then, with XEN support system, do we need to write scripts for ifup 
/ ifdown

commands?

Yes, you need to make the corresponding changes to Xen.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss



___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss



Sorry for the top post
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-09 Thread Sébastien Riccio
Actually i'm interested to this question too. I'm trying to modify xen 
network scripts in
order to have it bind the vif to the right bridge and with the right 
vlan tag (if using a

bridge with trunk ports).

I found that slackware has some interesting scripts here:

http://palembang-slackers.org/linuxupdate/pub/slackware/addon/slackbuilds/13.1/network/openvswitch/xen/

but I dont really understand how they get it to work, especially for the 
vlan part.


They have a $tag check in vif-openvswitch but the xen configuration 
files don't allow the use of the tag attribute

for a vif:

example vif definition:
vif = [ 'ip=10.111.5.10, bridge=trunk0, tag=85, vifname=vm1.0' ]

myhost# xm create -c /cloud/data2/configs/vm1.cfg
Using config file "/cloud/data2/configs/vm1.cfg".
Error: Invalid vif option: tag

Althought I think that this topic is more xen oriented and maybe should 
be addressed
the the xen mailing lists, I just wanted to share that info and know if 
someone around

has ideas or experience with xen (not citrix's one) + openvswitch.

Sébastien

On 09.07.2011 20:36, Ben Pfaff wrote:

On Sun, Jul 10, 2011 at 02:26:01AM +0800, 沒 wrote:

* first question *
if I want to make Domain-0 link to be connected, which port should I attach
to the virtual bridge... eth0? or peth0?

I don't understand this question.  You have one Ethernet port.  Attach
that one to vbr0.  Where does the other one come from?


* second question *
do I need to attach "vif0.0" to the virtual bridge "vbr0"? (vif0.0 ->
interface of Domain0's eth0)
or there is no need to do so, just attach eth0 / peth0?

If you want packets from vif0.0 to be able to reach eth0, and vice
versa, then attach both of them to the same bridge.


* third question *
how can I attach "vif1.0" to "vbr0" before Domain-1 is been created?

Normally you would attach vif1.0 to vbr0 after Domain-1 is created.


* forth question *
with KVM support, INSTALL.KVM says that need to add scripts ovs-ifup /
ovs-ifdown,
then, with XEN support system, do we need to write scripts for ifup / ifdown
commands?

Yes, you need to make the corresponding changes to Xen.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss



___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss


Re: [ovs-discuss] Question about setting Open vSwitch on top of CentOS with XEN support

2011-07-09 Thread Ben Pfaff
On Sun, Jul 10, 2011 at 02:26:01AM +0800, 沒 wrote:
> * first question *
> if I want to make Domain-0 link to be connected, which port should I attach
> to the virtual bridge... eth0? or peth0?

I don't understand this question.  You have one Ethernet port.  Attach
that one to vbr0.  Where does the other one come from?

> * second question *
> do I need to attach "vif0.0" to the virtual bridge "vbr0"? (vif0.0 ->
> interface of Domain0's eth0)
> or there is no need to do so, just attach eth0 / peth0?

If you want packets from vif0.0 to be able to reach eth0, and vice
versa, then attach both of them to the same bridge.

> * third question *
> how can I attach "vif1.0" to "vbr0" before Domain-1 is been created?

Normally you would attach vif1.0 to vbr0 after Domain-1 is created.

> * forth question *
> with KVM support, INSTALL.KVM says that need to add scripts ovs-ifup /
> ovs-ifdown,
> then, with XEN support system, do we need to write scripts for ifup / ifdown
> commands?

Yes, you need to make the corresponding changes to Xen.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss