[BGPCEP-952] Remove blueprint from PCEP extensions Created: 12/May/21  Updated: 04/Jul/23  Resolved: 17/Jan/23

Status: Resolved
Project: bgpcep
Component/s: PCEP
Affects Version/s: None
Fix Version/s: 0.19.0

Type: Task Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Blocks
blocks BGPCEP-961 Remove blueprint from pcep-spi Resolved
Relates
relates to BGPCEP-962 Remove blueprint from pcep-impl Resolved
Sub-Tasks:
Key
Summary
Type
Status
Assignee
BGPCEP-969 Remove blueprint from pcep-ietf-stateful Sub-task Resolved Robert Varga  
BGPCEP-968 Remove blueprint from ietf-p2mp-te-lsp Sub-task Resolved Robert Varga  
BGPCEP-1018 Remove blueprint from autobandwidth-e... Sub-task Resolved Robert Varga  
BGPCEP-967 Remove blueprint from pcep-segment-ro... Sub-task Resolved Robert Varga  
Epic Link: OSGi deps

 Description   

PCEP extensions seem to be using same registry pattern as bgp-parser-spi dictated. Analyze them and convert them to OSGi DS whiteboard.



 Comments   
Comment by Robert Varga [ 21/Nov/21 ]

There are a number of configuration knobs we are dealing here with, which are global configuration, but really should not be. While the configuration layout is hosted by the extensions, they should be instantiated in pcep-topology-provider's namespace, so they can be manipulated for each individual topology and in fact on a per-peer basis.
So we should first deal with BGPCEP-992 to rehost dispatcher configuration and then also rehost the extension configuration. This essentially means that PCEP extensions are pulled in by topology-api, but since they can be configured, that should not be a major problem.

Generated at Wed Feb 07 19:14:34 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.