https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/TRNSPRTPCE-628 transportpce <p>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.</p> <p>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.</p> <p>In the long run, when the string length limitations are brought in, it could be problematic.</p> <p> </p> <p> </p> <p> </p> TRNSPRTPCE-628

ODU connection name is too long

Story High Verified Done Balagangadhar Bathula Balagangadhar Bathula Wed, 2 Mar 2022 03:16:02 +0000 Wed, 20 Sep 2023 15:27:07 +0000 Thu, 29 Sep 2022 09:33:43 +0000 Phosphorus 0 1 2 days 0 minutes 2 days <p>This change is merged in: <a href="https://git.opendaylight.org/gerrit/c/transportpce/+/100830" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/c/transportpce/+/100830</a></p> <p>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.</p> <p> </p> <p>Reopening this issue to fix the code. Drop the service name only from the odu-connection name but not from the interfaces.</p> <p> </p> <p>For example:</p> <p>1) XPDR1-NETWORK1-ODU4-<span class="error">&#91;serviceName&#93;</span></p> <p>2) XPDR-CLIENT1-ODU4-<span class="error">&#91;serviceName&#93;</span></p> <p>3) XPDR-CLIENT1-ODU4-x-XPDR1-NETWORK1-ODU4 (odu-connection)</p> <p> </p> <p> </p> Development Rank 0|i042to: Sprint Sprint 26 Sprint 27 Sprint 29 Story Points 2.0