[BGPCEP-980] Cleanup TopologyReference lifecycle Created: 23/Sep/21 Updated: 24/Jan/24 |
|
| Status: | Confirmed |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | None |
| Fix Version/s: | 0.20.7 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pick-next, pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | OSGi deps | ||||||||
| Description |
|
BgpTopologyDeployerImpl provides a bridge which registers TopologyReference with OSGi Service Registry. Document the entire lifecycle and use cases which are dependent on this working and provide an alternative which does not depend on OSGi. |
| Comments |
| Comment by Robert Varga [ 16/Jan/23 ] |
|
This relates to 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. Aside both of them into the same ClusterSingletonService I do not see a possible way out. Perhaps, what we need is a static binding, where pcep-tunnel-provider starts the same instances and ... let CSS policy sort out co-location. |
| Comment by Robert Varga [ 16/Jan/23 ] |
|
Sorry, this is the wrong issue. |