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-578 transportpce <p>In PortMapping, the mapping corresponding to a traffic port of a Transponder is not always filled with the xpdr-node-types value "tpdr", as it is made with values mpdr or switch for an otn-xpdr.<br/> Having always this field with the correct value in PortMapping datastore could simplify downstream treatments, as for example in T-API topology management.<br/> Fill systematically this field whatever is the xpdr node type.</p> TRNSPRTPCE-578

Set tpdr in xponder-type of the mapping for Transponder

Bug Medium Verified Done Gilles Thouenon Gilles Thouenon Tue, 30 Nov 2021 14:38:14 +0000 Fri, 10 Dec 2021 14:20:29 +0000 Fri, 10 Dec 2021 06:51:49 +0000 Phosphorus Phosphorus 0 2 0 minutes 6 hours <p>This behavior comes from the fact that the xpdr-type had been introduced with release 2.0 of OpenROADM models. This field is contained in the xponder list which has not been forced as mandatory. So, when a xpdr node configuration contains that list of xponder, we can read this xpdr-type and set it in the mapping, but in our xpdra and xpdrc node configurations, we stayed with the same device configurations as in release 1.2.1, it means without this list of xponder. Since the xpdr-type was not present in the node configuration, it was neither set in the mapping.</p> <p>Since in version 1.x of OpenROADM models there was only tpdr as xponder node type, and OpenROADM recommends using the list of xponder from version 2.0, we can consider that if the xpdr device configuration does not contain any list of xponder, it is a Transponder, and thus we can set "tpdr" in the corresponding mapping.</p> <p>This approach looks fine to me. Thanks Gilles!</p> Development Rank 0|i03v91:9zzzzzzxzzzu Sprint Sprint 24