[TRNSPRTPCE-628] ODU connection name is too long Created: 02/Mar/22 Updated: 20/Sep/23 Resolved: 29/Sep/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Phosphorus |
| Type: | Story | Priority: | High |
| Reporter: | Balagangadhar Bathula | Assignee: | Balagangadhar Bathula |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 2 days | ||
| Original Estimate: | 2 days | ||
| Description |
|
Currently when an ODU connection between the network side and the client side is provisioned, it concats the service name to these interfaces and it becomes too long. Though the current MSA does not have any limitation on the string length, it would be preferred not keep it too long. In fact some devices in the lab do complain about being that long. In the long run, when the string length limitations are brought in, it could be problematic.
|
| Comments |
| Comment by Balagangadhar Bathula [ 31/May/22 ] |
|
This change is merged in: https://git.opendaylight.org/gerrit/c/transportpce/+/100830 |
| Comment by Balagangadhar Bathula [ 16/Aug/22 ] |
|
There has been a bug in the code. The service-name was dropped from the lower-order OTN interfaces. This prevents from creating lower order network-side interfaces.
Reopening this issue to fix the code. Drop the service name only from the odu-connection name but not from the interfaces.
For example: 1) XPDR1-NETWORK1-ODU4-[serviceName] 2) XPDR-CLIENT1-ODU4-[serviceName] 3) XPDR-CLIENT1-ODU4-x-XPDR1-NETWORK1-ODU4 (odu-connection)
|