This group is locked. No changes can be made to the group while it is locked.
Re: Arbitrary connection port is part of the node-id
Edward Warnicke <hagbard@...>
The config/operational synch is best handled a little differently.
When you try to config an ovsdb-node to connect... you don't *really* know the systemid... just the IP:port.
The way we solved this for bridges, and the way I'd advocate solving it here is:
1) If you are configing a ovsdb-node, write its iid to the external-ids of the openvswitch table
2) When you get an openvswitch table, if it has an iid in its external-ids, use that in the operational data store as its iid
3) If you don't get an iid in its external-ids... use some reasonable heuristic to contruct one.
For #3... I don't currently see a reason *not* to use systemid presuming its guaranteed unique and we contruct some kind of reasonable
Uri from it.
On Tue, Apr 21, 2015 at 1:09 PM, Prateek Garg (prategar) <prategar@...> wrote: