[TRNSPRTPCE-586] Refactor transportpce-routing-constraint Created: 18/Jan/22  Updated: 20/Sep/23  Resolved: 08/Apr/22

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

Type: Story Priority: High
Reporter: Gilles Thouenon Assignee: Gilles Thouenon
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 weeks
Original Estimate: 3 days

Issue Links:
Blocks
blocks TRNSPRTPCE-515 Service Model 10.1 Verified

 Description   

Transportpce has internal yang models that are very close to official openROADM ones. As an example, transportpce-routing-constraints.yang is more or less equivalent to openroadm-routing-constraints.yang, but the pce-metric enumeration is specific to transportpce and used in several places in PCE.
Since structure uses in PCE uses transportpce model, and input comes from service models with finally the same strucutre but with different types, there are some dedicated code to convert one type to another.
Such things could be advantageously avoid using directly the official openROADM stucture.
For that, specific things as pce-metric must be moved to a common model for example.
Eventually, pce-metric should be also removed and replaced by equivalent metric from offical openROADM models.


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