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-4 transportpce <p>Add a filed called link status that should be marked as up or down based in the protocol value (up to indicate the pce that path is available for service and down to indicate that path is not available).</p> <p> </p> <p>superseded by <a href="https://jira.opendaylight.org/browse/TRNSPRTPCE-46" title="Manage Link admin-state in topology" class="issue-link" data-issue-key="TRNSPRTPCE-46"><del>TRNSPRTPCE-46</del></a></p> TRNSPRTPCE-4

The link ROADM to ROADM is not automatically deleted when the ROADM is disconnected

Bug Medium Verified Done Olivier Renais Ahmed Triki Tue, 26 Jun 2018 15:25:36 +0000 Fri, 3 Sep 2021 13:16:32 +0000 Wed, 10 Oct 2018 12:22:13 +0000 0 4 <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=svachhani" class="user-hover" rel="svachhani">svachhani</a> isn't it already fixed ? </p> <p>Yes it is already fixed. </p> <p>thanks , we can close it then, <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=orenais" class="user-hover" rel="orenais">orenais</a> can you update it and excel sheet after review.</p> <p>Sorry missed it. Could you point to the gerrit changes associated to that. We had several discussions about this, and my feeling was that we had a workaround , but that at the end the status was not modified. Expected behavior is the following. 1) we create a link with in the OMS attributes a clfi and spanloss-base according to the info we have in an external database that gives the inventory of links. 2) The Controller finds the source and LLDP info on neighbors during topology building. It shall then check consistency between measured span loss and spanloss-base and fills what misses (spanloss-current) if consistent. 3) if a link is broken, from a notification on LLDP status change, it shall only change the admin or operationnal-state of the link, but not delete it, so that we don't need to repopulate the spanloss-base (used for the link engineering) as in first step.</p> <p>The opened issue was addressed by the merge request. Current version of code is adding a new link into network model based on LLDP notification and deleting it from network model based on LLDP notification which was agreed  at that tine. Code is already merged into Master. I think we can close this issue and open another one if you think it needs more features. </p> <p>This bug highlighted prior to integration in Fluorine has been resolved. However proposed solution leads to other issues. Created <a href="https://jira.opendaylight.org/browse/TRNSPRTPCE-46" title="Manage Link admin-state in topology" class="issue-link" data-issue-key="TRNSPRTPCE-46"><del>TRNSPRTPCE-46</del></a> to address the corresponding issue</p> Duplicate TRNSPRTPCE-46 Relates TRNSPRTPCE-12 Development Rank 0|i03gna:zr Sprint Sprint 3 Sprint 5