[OPNFLWPLUG-1112] Do not use odl-controller-blueprint Created: 29/Sep/21  Updated: 07/Feb/24

Status: In Progress
Project: OpenFlowPlugin
Component/s: pt
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Unresolved 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 CONTROLLER-2000 Deprecate odl-controller-blueprint Confirmed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
OPNFLWPLUG-1113 Migrate applications/southbound-cli t... Sub-task Confirmed  

 Description   

Use of Blueprint overall and the ODL extension specifically is being phased out. There are is a ton of bundles in OFP which use them.
There are different classes of users:
1. Karaf CLI, these should be migrated to Karaf annotations
2. users of odl:use-default-for-reference-types=true, these should be plain removed
3. users of odl:type, which should be migrated to OSGi SCR (if feasible)
4. users of odl:rpc-implementation, which should be migrated to explicit Rpc(Provider)Service use
5. users of odl:action-provider, which should be migrated to explicit use of Action(Provider)Service use
6. users of odl:clustered-app-config, these will need to be migrated once we have an easy migration path

This obviously requires additional analysis and is a prime opportunity for cleaning up any lifecycle issues there may be.


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