[TRNSPRTPCE-549] Handling link in T-API topology Created: 12/Oct/21  Updated: 17/Dec/21  Resolved: 15/Dec/21

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

Type: Story Priority: Medium
Reporter: Olivier Renais Assignee: Javier Errea
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day

Epic Link: T-API extended support

 Description   

The set of rpcs used to populate links between ROADMs and Xponders has been replicated to do the same thing with T-API topology. If it makes sense in the long term where T-API topology may includes some nodes coming from OpenROADM domain, but also some additional NEs coming from a T-API domain, in the short term, where T-API topology is a replication of the OR topology in the T-API format, we should try to import all existing links from the OR topology.

A listener shall be created on openroadm-topology so that links appearing in openroadm-topology are automatically populated.

Acceptance criteria : the code is submitted for review and does not bring any regression. Junit tests are complemented to address new features.


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