[TRNSPRTPCE-540] Rationalize sapi/dapi configuration Created: 06/Oct/21 Updated: 10/Dec/21 Resolved: 10/Dec/21 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Phosphorus |
| Type: | Story | Priority: | Medium |
| Reporter: | Gilles Thouenon | Assignee: | Gilles Thouenon |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 week | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | End-to-end OTN service Management |
| Description |
|
To be able to configure correctly sapi and dapi fields during the OTU and ODU interface creation, it would be more convenient to use the AEndApiInfo and ZEndApiInfo containers available at the otn-service-path level, and generalizing that usage also for OTU creation at the service-path level. |