Done
Details
Assignee
Former userFormer user(Deactivated)Reporter
Former userFormer user(Deactivated)Requirement Type
SpecificationTSC Priority
4Arch Review
Not requiredScope Status
Original ScopeT-Shirt Size
MRC0 Scorecard
Not used for this releaseRC0 Approval
Not used for this releaseFix versions
Priority
HighEpic Name
Control Loop in TOSCA LCM improvement
Details
Details
Assignee
Former user
Former user(Deactivated)Reporter
Former user
Former user(Deactivated)Requirement Type
Specification
TSC Priority
4
Arch Review
Not required
Scope Status
Original Scope
T-Shirt Size
M
RC0 Scorecard
Not used for this release
RC0 Approval
Not used for this release
Fix versions
Priority
Epic Name
Control Loop in TOSCA LCM improvement
Created October 19, 2021 at 12:06 PM
Updated May 16, 2022 at 3:42 PM
Resolved May 9, 2022 at 5:49 PM
Description of Use Case / Requirement:
CLAMP (Control Loop Automation Management Platform) functionalities, recently moved to Policy project , want to provide a Control Loop Lifecycle management architecture. A control Loop is a key concept for Automation and assurance Use Cases and remain a top priority for ONAP as an automation platform. This requirement wants to improve Control Loop LCM architecture focusing on an abstract CL management logic , providing a common CL Design time catalogue with a generic CL definition,isolating CL logic vs ONAP component logic and elaborate API to integrate with other design systems as well as 3PP component integration. PoCs have been progressed in ONAP Rel G and H in this area, CL LCM redesign has reached a relevant viable set of features and it is ready to be moved in Rel I to mainstream as part of the Policy framework.
Owners (one of these should be the Assignee - use @ notation):
,
Link to HLD/LLD (if any):
https://wiki.onap.org/display/DW/R9+Control+Loop+in+TOSCA+LCM
Dependency Relationships with Other Projects:
N/A
Project (ONAP Component #1) IMPACT: TO/C
Impact Type: TO/C
Company Engagement: Ericsson
Resources: 5 (People)
Support Status: S
Integration Leads (use @ notation):