Controller initiated connections always connect to one manager 58/27458/1
authorAnil Vishnoi <vishnoianil@gmail.com>
Fri, 25 Sep 2015 04:19:01 +0000 (09:49 +0530)
committerAnil Vishnoi <vishnoianil@gmail.com>
Fri, 25 Sep 2015 17:49:26 +0000 (17:49 +0000)
commit75b981ae4337a9849073e5ea4bbeb6901b67bd83
tree6d8cd385de5ddc30fa78c1c283a979f7f28a1652
parent65f5eca88489ba7941a5843e1a3703c5af3db6ee
Controller initiated connections always connect to one manager
listening in ptcp: mode. In clustered mode, all the three controller
will connect to the device, and in case any of the connection will flip
that instance will remove OvsdbNode from operational data store because
it will see only one manager in manager list. But because switch is
listening in passive mode, there can be multiple connection to same manager.
To handle this scenario, this patch adds number_of_connection attribute
to OvsdbNodeAugmentation to maintain the number of active connection to
specific manager. In case of switch initiated connection this value is
going to be 1 for each manager, but in case switch listening in passive
mode, this value will represent active connections (extraced from
Manager tables status column n_connections attributes).

Change-Id: I910104a5109b5bed6af7786a7692c617bd4305b7
Signed-off-by: Anil Vishnoi <vishnoianil@gmail.com>
southbound/southbound-api/src/main/yang/ovsdb.yang
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/SouthboundMapper.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/transactions/md/OvsdbManagersRemovedCommand.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/transactions/md/OvsdbNodeRemoveCommand.java