Re: [Need Help] Arbitrary connection port is part of the node-id
Prateek Garg (prategar) <prategar@...>
I have implemented this change and submitted the same:
Summary of changes:
The overall idea is to use the system-id for iid of ovsdb node when system-id is present in external-ids of the open-vswitch when connection in tcp mode. This is because the port changes when ovs reconnects to controller in tcp mode. Further, in all other scenarios the old way would be used.
From: Edward Warnicke <hagbard@...>
Date: Friday, April 24, 2015 at 8:50 PM
To: "Amit Mandke (ammandke)" <ammandke@...>
Cc: Prateek Garg <prategar@...>, "ovsdb-dev@..." <ovsdb-dev@...>
Subject: Re: [ovsdb-dev] [Need Help] Arbitrary connection port is part of the node-id
If we do not receive the initial dump of the DB... we aren't getting anything to work at all... it s a fundamental failure.
And always remember that OVSDB can connect to us unsolicted... so we will always have to deal with ovsdb instances that we *didn't* create the connection for. This is another reason that the solution I'm advocating for here is good... it works consistently in active and passive mode.
On Fri, Apr 24, 2015 at 7:08 PM, Amit Mandke (ammandke) <ammandke@...> wrote: