[TRNSPRTPCE-157] Openroadm service with routing include constraints Created: 04/Oct/19 Updated: 02/Mar/23 Resolved: 02/Mar/23 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Jonas Mårtensson | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Functional compliance to OR |
| Description |
|
The way routing include constraints are defined in TransportPCE (transportpce-routing-constraints.yang) is different from how they are defined in the OpenROADM service model (org-openroadm-routing-constraints.yang). It seems there is currently no mapping performed between the definitions so that it is not possible to request an OpenROADM service (rpc service-create) with routing include constraints. |
| Comments |
| Comment by Jonas Mårtensson [ 16/Jan/23 ] |
|
It seems this was fixed when replacing the internal tpce constraints model with the official openroadm model (https://git.opendaylight.org/gerrit/c/transportpce/+/99380)? |