Adding Tri-states to the connection manager locality check. 65/1265/1
authorMadhu Venugopal <vmadhu@cisco.com>
Wed, 18 Sep 2013 13:04:10 +0000 (06:04 -0700)
committerMadhu Venugopal <vmadhu@cisco.com>
Wed, 18 Sep 2013 13:04:10 +0000 (06:04 -0700)
commitbaf00b337b0d54a1aa5a83f5b125470e2a856bdd
tree6f1aa47f32dce87e5045203746af17f1cc38567a
parent37fa8d2f9fa05c29005df8cb39e71ead95de13a9
Adding Tri-states to the connection manager locality check.

As of now, the connection manager's isLocal() provides a binary true/false for a locality.
But is missing a key state of not-connected. This is now included as part of a new API (getLocalityStatus).
Retaining the isLocal as a deprecated method to be removed later once all the users have migrated.

Change-Id: I0feddf2a86770740f441060bd411f28d1bb15610
Signed-off-by: Madhu Venugopal <vmadhu@cisco.com>
opendaylight/connectionmanager/api/src/main/java/org/opendaylight/controller/connectionmanager/ConnectionLocality.java [new file with mode: 0644]
opendaylight/connectionmanager/api/src/main/java/org/opendaylight/controller/connectionmanager/IConnectionManager.java
opendaylight/connectionmanager/implementation/src/main/java/org/opendaylight/controller/connectionmanager/internal/ConnectionManager.java
opendaylight/connectionmanager/implementation/src/main/java/org/opendaylight/controller/connectionmanager/scheme/AbstractScheme.java
opendaylight/forwardingrulesmanager/implementation/src/main/java/org/opendaylight/controller/forwardingrulesmanager/internal/ForwardingRulesManager.java