[#TRNSPRTPCE-543] Update device-renderer YANG model to use a-end-api-info and z-end-api-info containers in service-path rpc

Manage 10GE and 1GE OTN services in configurations with intermediate otn-switch (TRNSPRTPCE-541) [TRNSPRTPCE-543] Update device-renderer YANG model to use a-end-api-info and z-end-api-info containers in service-path rpc 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:	None

Type:

Sub-task

Priority:

Medium

Reporter:

Gilles Thouenon

Assignee:

Unassigned

Resolution:

Done

Votes:

Labels:

None

Remaining Estimate:

0 minutes

Time Spent:

2 days

Original Estimate:

Not Specified

Description

Modify the device-renderer yang model to be able to use the a-end-api-info and z-end-api-info containers in service-path rpc, as it is the case for the otn-service-path rpc.
By this end, it will be possible to manage the sapi/dapi during the OTU interface creation on the same way as it is of the ODU interfaces.

Comments

Comment by Gilles Thouenon [ 10/Dec/21 ]

see change 97833: Manage ODU4 services over multiple OTU4 | https://git.opendaylight.org/gerrit/c/transportpce/+/97833

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

[TRNSPRTPCE-543] Update device-renderer YANG model to use a-end-api-info and z-end-api-info containers in service-path rpc Created: 06/Oct/21 Updated: 10/Dec/21 Resolved: 10/Dec/21