[NETVIRT-1066] Iterating through non-L2VLAN interfaces in L3VPN Tunnel Interface State listener Created: 18/Jan/18 Updated: 08/Apr/18 Resolved: 08/Apr/18 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | Oxygen |
| Type: | Bug | Priority: | Medium |
| Reporter: | Hanamantagoud Kandagal | Assignee: | Hanamantagoud Kandagal |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
L3VPN application listens on TunnelInterfaceStateListener to handle tunnel states. Whenever tunnel states change i.e say (a) UP --> DOWN or DOWN --> UP, (b) Add/Delete L3VPN needs to iterate through list of ports/Interfaces on a given DPN and appropriate manage the L3VPN flows. DpnToInterfaceList operational DS managed by Interface Manager doesn't store the type of interfaces. Its required to be enhanced to store the type of each interfaces i.e L2VLAN / Tunnel / Other , so that application interested can handle only required type of interfaces in them.
|
| Comments |
| Comment by Michael Vorburger [ 01/Feb/18 ] |
|
ehvkand FYI we just merged https://git.opendaylight.org/gerrit/#/c/63160/ during genius weekly.. does this mean this bug can be closed, or that the merge of that change in genius enables you to now do more about it in netvirt, so this should stay open? |
| Comment by Hanamantagoud Kandagal [ 02/Feb/18 ] |
|
Hi Michael , I see that , review https://git.opendaylight.org/gerrit/#/c/63160/ is not yet merged. Sam is running gate job for genius and netvirt changes together. Once both genius and netvirt patches are merged , i will close this bug. |
| Comment by Sam Hague [ 06/Apr/18 ] |
|
Hanamantagoud is this still an issue? |
| Comment by Hanamantagoud Kandagal [ 08/Apr/18 ] |
|
Hi Sam, This issue has been fixed. I am closing this Jira now. |