Hello Dimitris, you beat me to the answer. That's exactly how it works.
Cheers, Jaime On Wed, Mar 21, 2012 at 1:24 PM, Dimitris Theodorou <[email protected]>wrote: > A misunderstanding on my part. Ovswitch, unlike the Linux Bridge driver, > needs only one bridge to function. > If for example you have two VMs in the same host, and want them to be in > different VLANs (e.g vlan 1 and 2), with Linux bridges you accomplish that > with > > vm nic to physical nic > vm1:eth0 ---- vnet0 ---- br0 ---- eth0.1 > vm2:eth0 ---- vnet1 ---- br1 ---- eth0.2 > > In ovswitch you have > > vm nic to ovs bridge > vm1:eth0 ---- vnet0 ---(tag=1)--- ovs-br0 > vm2:eth0 ---- vnet1 ---(tag=2)--- ovs-br0 > > ovs bridge to physical nic > ovs-br0 ---(tags=all)--- eth0 > > If this is how OpenNebula suggests using ovswitch, configuring the ovs > bridge is part of installing and configuring ovswitch on the host. Then you > need to specify the ovs bridge in your network configurations. > > ______________________________**_________________ > Users mailing list > [email protected] > http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**org<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org> > -- Jaime Melis Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | [email protected]
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
