BUG-5685: Register BGP Application Peer Cluster Singleton Service 05/42905/7
authorClaudio D. Gasparini <cgaspari@cisco.com>
Wed, 10 Aug 2016 12:53:28 +0000 (14:53 +0200)
committerMilos Fabian <milfabia@cisco.com>
Tue, 16 Aug 2016 19:34:34 +0000 (19:34 +0000)
commit0aabee8976574d2765248f134d4292e345adcb83
tree91ec5757aab6f9d88bcf288c6e36b4322eb39e16
parent259daaeb2ad7ebf70308abc0a098ab2ba096b375
BUG-5685: Register BGP Application Peer Cluster Singleton Service

Register BGP Application Peer Cluster Singleton Service.
When running on clustering, it was need it to have different
configuration per instance to avoid conflicts.
Now all instance can have same configuration,
since cluster service provider take cares of make active
the one is running on Leader Cluster. If Leader goes down,
the instance from the new Leader will become active.

Change-Id: I5316a50b5ceaf54c838018860baefc5ae326465b
Signed-off-by: Claudio D. Gasparini <cgaspari@cisco.com>
bgp/rib-impl/src/main/java/org/opendaylight/controller/config/yang/bgp/rib/impl/BGPApplicationPeerModule.java
bgp/rib-impl/src/main/java/org/opendaylight/protocol/bgp/rib/impl/ApplicationPeer.java
bgp/rib-impl/src/main/java/org/opendaylight/protocol/bgp/rib/impl/config/AppPeer.java
bgp/rib-impl/src/test/java/org/opendaylight/protocol/bgp/rib/impl/PeerTest.java