Details
-
Epic
-
Status: Done
-
High
-
Resolution: Done
-
None
-
Control Loop in TOSCA LCM
-
Specification
-
Not required
-
Reduced Scope
-
L
-
Not used for this release
-
Not used for this release
Description
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 (Policy) IMPACT: TO/C
- Impact Type: TO/C
- Company Engagement: Ericsson
- Resources: 4 (People)
- Support Status: S
Integration Leads (use @ notation):
Attachments
Issue Links
- blocks
-
POLICY-3560 ControlLoop Integration Tests
-
- Closed
-
- clones
-
REQ-1 ONAP Requirement Template
-
- To Do
-
- relates to
-
POLICY-3168 DCAE interaction for Helm service deployment
-
- Closed
-