I am following the cookbook at http://openvswitch.org/?page_id=146 . I don't
want to create one single bridge, but I want to be able to have open
vswitches running on different hosts and still be able to talk to each
other. In short, I want to remove the eth0 - eth0 connection mentioned in
the cookbook and replace it with a tunnel if possible, so that a VM on host1
can communicate with a VM on host2.

On Tue, Jul 12, 2011 at 11:18 PM, Nicholas Bastin <[email protected]>wrote:

> On Wed, Jul 13, 2011 at 01:40, Aniruddha Laud <[email protected]>
> wrote:
> > I want to connect two instances of openvswitches running on different
> hosts.
> > vde_switch has a way to do this using dpipe and vde_plug where it creates
> a
> > tunnel between the two hosts. I read the cookbook, but I don't see any
> such
> > option in openvswitch. The cookbook mentions that the hosts need to have
> a
> > direct connection using actual NICs. Am I missing something? Thanks.
>
> I'm not quite sure I understand what you mean by "connect two
> instances".  Do you mean treat them as a single bridge?  You can
> connect almost anything that creates an interface at the OS level to
> an OVS bridge, so you could make a tunnel between two bridges, but
> treating them (internally) as one bridge is much more complex - and
> potentially not that necessary.  What can you accomplish with one
> bridge that you can't accomplish with two?  (Especially if they are
> openflow controlled?)
>
> --
> Nick
>
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to