[TRNSPRTPCE-182] Populate OTN link in topology Created: 07/Jan/20  Updated: 03/Sep/21  Resolved: 18/May/20

Status: Verified
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Highest
Reporter: Olivier Renais Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 3 weeks
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates TRNSPRTPCE-199 OTN Topo update from Renderer Verified
Epic Link: OTN support

 Description   

OTN services are created sequentially. This implies needed supporting services are present and supporting links have been populated in the topology to allow path calculation. Thus we need to populate OTN link in topology after OTN service has been succesfully provisionned. This stories includes the creation of all methods required in both OTN Renderer as well as Topology management. Link discovery based on accepted SAPI and DAPI on the interfaces has been put temporarly aside because SAPI and DAPI are optional parameters that may or may not be in the device models depending on the vendors.

Evaluation indicators:

  • code published on master branch , not necessarily merged

Generated at Wed Feb 07 20:42:27 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.