mdsal clustering


MichaƂ Skalski <michal@...>
 

Hi,

I'm trying to use OpenDaylight ovsdb integration with OpenStack Juno.
When I only have one odl controller it works ok, but I have some
problems when I try to activate odl-mdsal-clustering feature.
In my environment I have 3 odl controllers with IP addresses:
192.168.0.6, 192.168.0.7 and 192.168.0.8, on all of them I have
similar configuration like in this gist:
https://gist.github.com/michalskalski/36f2c21d52d28f7bf107
I put ovsdb plugin from all controllers behind haproxy which listen on
VIP address: 192.168.0.2

When I want to connect ovs to odl I use this command:
ovs-vsctl set-manager tcp:192.168.0.2:6640

so I use haproxy address and this is forwarded to one of the controllers.
For 5 vswitches which I tried connect only on some of them br-int
bridge was created by odl like for example here:

root@node-32:~# ovs-vsctl show
61ca43fb-1b76-4b38-8c46-04d11536ae54
Manager "tcp:192.168.0.2:6640"
is_connected: true
Bridge br-int
Controller "tcp:192.168.0.8:6653"
is_connected: true
fail_mode: secure
Port br-int
Interface br-int
type: internal
ovs_version: "2.3.1"

When I want to add new network or attach vm interfaces are not created on ovs.

Does someone have experience with mdsal clustering and ovsdb plugin
and can share examples of configuration?
Can we put ovsdb manager behind haproxy like I did? What about
openflow controller address for ovs bridges? Ovsdb plugin only add one
controller address, should I manualy add rest of controller addresses?
Maybe it is possible to put openflow controllers behind haproxy but
how told ovsdb manager to set specific address on ovs?

Regards
Michal

Join z.archive.ovsdb-dev@lists.opendaylight.org to automatically receive all group messages.