Bug 6337 - Handle string route-key from App Routes when Binary route-key is expected 93/43493/4
authorMilos Fabian <milfabia@cisco.com>
Tue, 9 Aug 2016 09:49:10 +0000 (11:49 +0200)
committerRobert Varga <nite@hq.sk>
Mon, 15 Aug 2016 08:27:49 +0000 (08:27 +0000)
commiteca666c067d809426fcb5936d559b3e08271f48f
treec4e9f849a8731e415b0f10adbc15b9e66ca5bb51
parent88b320be8c08b36c074a6a11e12dd5102228ad27
Bug 6337 - Handle string route-key from App Routes when Binary route-key is expected

Change binary typed route keys to string. Modify RIB support extensions to
encode key with Base64.

The binary type is decoded with Base64, where length is restricted.
The BGP application RIB allows user to originate a route
and binary typed route key is limiting user defined route keys to a
specific length (cut-off when does not fit).
Also using plain text for binary typed route keys is not correct.

The route-key type change is invisible in restconf output.

Change-Id: Ieab24705ceebe0b527b4ddae81a4109c9c250de0
Signed-off-by: Milos Fabian <milfabia@cisco.com>
bgp/evpn/src/main/java/org/opendaylight/protocol/bgp/evpn/impl/EvpnRibSupport.java
bgp/evpn/src/main/yang/bgp-evpn.yang
bgp/evpn/src/test/java/org/opendaylight/protocol/bgp/evpn/impl/EvpnRibSupportTest.java
bgp/l3vpn/src/main/java/org/opendaylight/protocol/bgp/l3vpn/AbstractVpnRIBSupport.java
bgp/l3vpn/src/main/yang/bgp-vpn.yang
bgp/l3vpn/src/test/java/org/opendaylight/protocol/bgp/l3vpn/ipv4/VpnIpv4RIBSupportTest.java
bgp/l3vpn/src/test/java/org/opendaylight/protocol/bgp/l3vpn/ipv6/VpnIpv6RIBSupportTest.java
bgp/labeled-unicast/src/main/java/org/opendaylight/protocol/bgp/labeled/unicast/AbstractLabeledUnicastRIBSupport.java
bgp/labeled-unicast/src/main/yang/bgp-labeled-unicast.yang
bgp/labeled-unicast/src/test/java/org/opendaylight/protocol/bgp/labeled/unicast/LabeledUnicastIpv4RIBSupportTest.java
bgp/labeled-unicast/src/test/java/org/opendaylight/protocol/bgp/labeled/unicast/LabeledUnicastIpv6RIBSupportTest.java