Hello,
IIUIC we have to attach OVS bond to an OVS bridge, so it would look like
this:
$ ovs-vsctl -- \
add-br br0 -- \
--fake-iface add-bond br0 bond1 eth0 eth1 -- \
--fake-iface add-bond br0 bond2 eth2 eth3
# attach VMs to the bridge
(eth0+eth1=bond1)--br0--VMs
(eth2+eth3=bond2)---/
And therefore VMs would be able to reach bond2, which is the problem.
What makes more sense, to create multiple OVS bridges (one for each
physical iface/bond) or some OF rules (if it is even possible).
TL;DR: we want to be able to setup two OVS bondings which are not able to
see each other.
Thanks,
Petr
2016-04-04 18:10 GMT+02:00 Scott Lowe <[email protected]>:
> Please see my response below.
>
>
> > On Apr 4, 2016, at 6:22 AM, Petr Horacek <[email protected]> wrote:
> >
> > Hello,
> >
> > we handle following networking (example) scenario with Linux bridges:
> >
> > (eth0+eth1=bond1)--bridge--VMs
> > (eth2+eth3=bond2)
> >
> > We want to do the same with OVS. What is the best way to do that?
> >
> > a) We can create multiple OVS bridges, but that would increase
> complexity of our code.
> > b) We can use one OVS bridge and define OpenFlow rules (how?) to hide
> the traffic.
>
>
> Hi Petr, maybe it's because I haven't had enough coffee yet, but why
> wouldn't the following accomplish what you need?
>
> (eth0+eth1=bond1)--OVS bridge--VMs
> (eth2+eth3=bond2)
>
> Can you elaborate a bit on exactly what you're trying to accomplish? That
> might help us help you.
>
> --
> Scott
>
>
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
