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/BGPCEP-980 bgpcep <p>BgpTopologyDeployerImpl provides a bridge which registers TopologyReference with OSGi Service Registry.</p> <p>Document the entire lifecycle and use cases which are dependent on this working and provide an alternative which does not depend on OSGi.</p> BGPCEP-980

Cleanup TopologyReference lifecycle

Improvement Medium Confirmed Unresolved Unassigned Robert Varga pick-next pt Thu, 23 Sep 2021 12:46:24 +0000 Wed, 24 Jan 2024 15:54:32 +0000 0.20.7 BGP 0 4 <p>This relates to <a href="https://jira.opendaylight.org/browse/BGPCEP-965" title="Remove blueprint from pcep-tunnel-provider" class="issue-link" data-issue-key="BGPCEP-965"><del>BGPCEP-965</del></a>. pcep-tunnel-provider is listening for local instances and registers them.</p> <p>This essentially means that in a cluster where both pcep-topology and pcep-tunnel provider are present, for each instance they end up being co-located.</p> <p>Aside both of them into the same ClusterSingletonService I do not see a possible way out.</p> <p>Perhaps, what we need is a static binding, where pcep-tunnel-provider starts the same instances and ... let CSS policy sort out co-location.</p> <p>Sorry, this is the wrong issue.</p> Issue split BGPCEP-959 Development Epic Link BGPCEP-881 Rank 0|i03zlr: