Dell - Internal Use - Confidential
I was trying OpenStack (Kilo) – ODL (Lithium) integration & could correlate few of the issues you are facing with mine.
My 2 cents,
To check if your config / setup helps achieve the intended, try manually configuring controller addresses on the ovs; but ideally you may not have to.
AFAIK, ovsdb clustering (HA support) is yet to be added
Could you create & share a simple block diagram – not sure if I visualize your blocks & the sequencing correctly (as in
ovsdb plugin from all controllers behind haproxy)?
From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Michal Skalski
Sent: Tuesday, July 14, 2015 7:01 PM
Subject: [ovsdb-dev] mdsal clustering
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:
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
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?
ovsdb-dev mailing list