Hi,
A further investigation by Amit has revealed that the system uuid is automatically set by the OVS so we can use it out of the box to identify an OVS instance. To see the external ID you can invoke the following cli:

ovs-vsctl --columns=external-ids list open_vswitch

looks like a win/win situation to me...:o)

Thanks,
Sharon.
________________________________________
From: ovsdb-dev-bounces@... [ovsdb-dev-bounces@...] on behalf of Sharon Aicler (saichler)
Sent: Monday, April 20, 2015 3:41 PM
To: Flavio Fernandes
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] Arbitrary connection port is part of the node-id

In that case you are kind of "gambling" that two of your dockers won't choose the same arbitrary port...:o)
In any case, we can't have the ID of an element arbitrary change all the time...As a quick and dirty fix, i would drop the port (and the "behind a NAT" scenario) so ovsdb id's would be predictable and not change per connection (it can even change in run-time if there was some network connectivity issue)...

A more suitable solution is probably generating and assigning a uuid to each of the managed instances, if one does not exist...a quick googling i found the following cli method:

ovs-vsctl set open_vswitch . external-ids:system-id='"${UUID}"'


Thanks,
Sharon.
________________________________________
From: Flavio Fernandes [ffernand@...]
Sent: Monday, April 20, 2015 1:25 PM
To: Sharon Aicler (saichler)
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] Arbitrary connection port is part of the node-id

On Apr 20, 2015, at 3:24 PM, Sharon Aicler (saichler) <saichler@...> wrote:

Hi,
Sorry, but does't a docker has a unique ip?

yes and no. ;) I’m used to see docker behind nat on the vm that hosts the containers. Then, from
'outside' the vm, various ovs instances reached using the same ip, but different ports. Like this:

docker run -p 16640:6640 blablabla
docker run -p 16641:6640 blablabla
docker run -p 16642:6640 blablabla
…

— flavio

________________________________________
From: Flavio Fernandes [ffernand@...]
Sent: Friday, April 17, 2015 4:23 AM
To: Sharon Aicler (saichler)
Cc: ovsdb-dev@...
Subject: Re: [ovsdb-dev] Arbitrary connection port is part of the node-id

On Apr 16, 2015, at 6:53 PM, Sharon Aicler (saichler) <saichler@...> wrote:

Hi all,
The node-id of an ovs bridge contains the arbitrary port of the outgoing connection instance and looks something like the following:
ovsdb://10.156.48.239:39490/bridge/br-ex

This creates an issue if i place something in the configuration store and the connection goes down due to some reason, the node-id will change each time the connection is lost or I restart ODL/OVSDB.
Any reason for this? can't we just use the ip? i don't think you can run two instances of OVS in the same VM…

Hi Sharon,

That is not true. I’ve seen a VM with many OVS instances running; mostly in a docker environment.

But I see your point. When OVS is connecting to ODL (i.e. active method) the port is not predictable. When ODL connects to
an OVS (passive mode), ODL will need to know that port, tho; so the solution to this problem should ideally work on both
scenarios.

— flavio

Thanks,
Sharon.
_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev