On Mon, 27 May 2013 11:08:31 +0800, bill4carson <bill4car...@gmail.com> wrote:

Hi, HuntXu

On 2013年05月27日 10:42, huntxu wrote:
On Mon, 27 May 2013 10:30:28 +0800, bill4carson <bill4car...@gmail.com> wrote:

Hi, All

As we konw, ovs-vsctl add-br br0 ; ovs-vsctl add-port br0 is used to create an bridge and add a port into it While after I creating several such kind bridges, can I specify how those bridges are connected to each other
using openvswith to make a simple network topology?


This has been already well documented in the FAQ.

"Q: How do I connect two bridges?" in the Basic Configuration section.


I'm quite new to openvswitch and SDN, so sorry for stupid questions.
Thanks for your info :), I just git pull my tree, found below descriptions:

330 A: First, why do you want to do this? Two connected bridges are not 331 much different from a single bridge, so you might as well just have
  332    a single bridge with all your ports on it.
  333
  334    If you still want to connect two bridges, you can use a pair of
  335    patch ports.  The following example creates bridges br0 and br1,
336 adds eth0 and tap0 to br0, adds tap1 to br1, and then connects br0
  337    and br1 with a pair of patch ports.
  338
  339        ovs-vsctl add-br br0
  340        ovs-vsctl add-port br0 eth0
  341        ovs-vsctl add-port br0 tap0
  342        ovs-vsctl add-br br1
  343        ovs-vsctl add-port br1 tap1
  344        ovs-vsctl \
  345            -- add-port br0 patch0 \
  346            -- set interface patch0 type=patch options:peer=patch1 \
  347            -- add-port br1 patch1 \
  348            -- set interface patch1 type=patch options:peer=patch0

Actually, I'm afraid this is not what I want, I mean the "patch ports" things.

What do you want exactly? Aren't you going to connect two bridges together,
or I've misunderstood something?

In my understanding, openvswitch provide means to create an virtual bridge, and method to add ports into this bridge, most importantly, virtual machine could use tap interface to attach into this bridge, which means a remote controller will be able to manipulate all the flow coming/leaving this bridge's ports as below:

ovs-ofctl add-flow br0 nw_src=220.181.111.147,actions=drop

In short words, this bridge is isolated from other bridges created in the same manner, only if we could define how those bridges are connected to each other, to be more precisely, like connecting bridge A port x to bridge B port y to make
a network topology much like the real world.


Patch ports are used for connecting bridges. After you connect two bridges
with a pair of patch ports, you could use 'ovs-ofctl show [bridge]' to get the
respective port number of each of the patch port pair. And that presents a
connection between port x of bridge A to port y of bridge B.

I'm not sure I put my thoughts clearly, and appreciate any inputs through.



--
regards,
hunt
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to