[TRNSPRTPCE-548] T-API Topology update Created: 12/Oct/21 Updated: 10/Dec/21 Resolved: 19/Nov/21 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Phosphorus |
| Type: | Story | Priority: | High |
| Reporter: | Olivier Renais | Assignee: | Javier Errea |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 4 days | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | T-API extended support | ||||||||||||
| Description |
|
T-API topology is currently updated when new nodes are connected using a netconf listener. Propose to rationalize the behaviour and trigger topology update on OR topology changes or Portmapping changes. Acceptance criteria : the code introduced is proposed for review and does not bring regression. |
| Comments |
| Comment by Javier Errea [ 19/Nov/21 ] |
|
This was the implementation done for the TAPI topology population. Only when there is a PortMapping change detected, the T-API topology population will be triggered |