Re: [Need Help] Arbitrary connection port is part of the node-id
Amit Mandke (ammandke) <ammandke@...>
It sounds tricky, cause once you register for callbacks you can’t be sure of the sequence of all the updates right? Or even guaranty if each update would be processed?
So essentially you are letting go a sure-shot event where you received the connection to store the OVSDB node and relying on the future updates to create it.
I am not sure if that is the best thing to do.
From: Edward Warnicke <hagbard@...>
Date: Friday, April 24, 2015 at 11:07 AM
To: "Prateek Garg (prategar)" <prategar@...>
Cc: "ovsdb-dev@..." <ovsdb-dev@...>
Subject: Re: [ovsdb-dev] [Need Help] Arbitrary connection port is part of the node-id
I had an idea last night as I was falling asleep that might be interesting.
How about we create the ovsdb-node in operational with the OpenVSwitchUpdateCommand (which should get tripped with the original dump of data from ovsdb on connect) rather than invoking OvsdbNodeCreatedCommand in the OvsdbConnectionInstance() constructor. That way you have access to the info you need, don't have to do a select (and thus a new round trip) etc.
On Wed, Apr 22, 2015 at 3:40 PM, Prateek Garg (prategar) <prategar@...> wrote: