Supply correct tunnel type to retrieve tunnel interface name 59/72459/6
authoreupakir <kiran.n.upadhyaya@ericsson.com>
Wed, 30 May 2018 06:55:03 +0000 (12:25 +0530)
committerSam Hague <shague@redhat.com>
Mon, 11 Jun 2018 20:46:51 +0000 (20:46 +0000)
commit25881fca31b10310e1e110b3ff494c30aad442b4
tree38d0f70b4b81cee98b960db6284aa14dc4ba533e
parent3cd7360664b8b3e04e690592bb2cf4b2438b7d06
Supply correct tunnel type to retrieve tunnel interface name

A recent change in ITM RPC has changed the API to retrieve the tunnel
interface name. It now fetches the interface name based on the tunnel-type
provided by the called insteady of hardcoding the tunnel type to
MplsOverGRE.
L3VPN was always sending tunnel type as VxLAN when calling this RPC.
The BGP routes were not being translated to flows.
The fix supplies the correct tunnel-type to the RPC based on the encap
type of fibEntry

Change-Id: Id5159ce8bc1ff686defe9121c8b4b7edfd809bbf
Signed-off-by: eupakir <kiran.n.upadhyaya@ericsson.com>
fibmanager/api/src/main/java/org/opendaylight/netvirt/fibmanager/api/IFibManager.java
fibmanager/impl/src/main/java/org/opendaylight/netvirt/fibmanager/BaseVrfEntryHandler.java
fibmanager/impl/src/main/java/org/opendaylight/netvirt/fibmanager/FibManagerImpl.java
fibmanager/impl/src/main/java/org/opendaylight/netvirt/fibmanager/NexthopManager.java
vpnmanager/impl/src/main/java/org/opendaylight/netvirt/vpnmanager/TunnelInterfaceStateListener.java