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-17 transportpce <p>Circuit-id on interfaces and ports can be used to link resources to provisioned services, and so help handling alarm correlation. The circuit-id shall be configured by the controller, when the interfaces and related ports are configured. This could also be configured after the service has been confirmed as operational (after the BER test), but we may want to limit the configuration operations. Propose to configure circuit-id with the service-name since this is a string, to have a direct mapping.</p> TRNSPRTPCE-17

Keep trace of service on configured elements

Improvement Low Verified Done Dhruv Bhardwaj Olivier Renais Fri, 13 Jul 2018 08:32:24 +0000 Fri, 3 Sep 2021 15:52:13 +0000 Fri, 3 Sep 2021 15:52:08 +0000 0 2 2 days 2 days <p>A single port(on degree)/OMS/OTS interfaces can be associated by multiple services, what's you suggestion there ? I can still submit patch fill in circuit-id for OTU/ODU/OCH/OCH(xpdr)/Ethernet/SRG-port/XPDR port since these interfaces are created per service.</p> <p>A failure on an interface supporting multiple services will affect all these services. This means in the correlation process the interface shall probably be handled with the highest priority, Thus I would recommend to configure the circuit-id of an oms/ots interface as a concatenation of the circui-id of the different services it supports with a well defined seperator, so that we can easily identifiy all affected services. The string maximum length not be a limitation to make this. If too complex/long to handle, please provide first patch focusing on interfaces supporting only 1 service. The addition of circuit-id on interfaces supporting multiple services can be done in a second step. Think we don't really need to order service-ids in the concatenated circuit-id</p> Development Rank 0|i03frz:0i000u Sprint Sprint 6 Sprint 7