BUG-5685: Register BGP Application Peer Cluster Singleton Service 24/44124/1
authorClaudio D. Gasparini <cgaspari@cisco.com>
Wed, 10 Aug 2016 12:53:28 +0000 (14:53 +0200)
committerMilos Fabian <milfabia@cisco.com>
Wed, 17 Aug 2016 07:10:43 +0000 (07:10 +0000)
commitff6f162a257a423d8a0c99271f8b0c52d84d2e57
tree00ef68ef6c42493ad40e08726311700627b16669
parentdb8996e377c2e6eadf0d9b6117c11e66f5e5d043
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>
(cherry picked from commit 0aabee8976574d2765248f134d4292e345adcb83)
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