Details
-
Epic
-
Status: Done
-
High
-
Resolution: Done
-
None
-
None
-
PoC - TOSCA Defined Control Loop and Control Loop Components
-
Requirement (DEPRECATED)
-
PoC
-
Not yet performed
-
Reduced Scope
-
M
-
Not used for this release
-
Not used for this release
Description
Description of Use Case / Requirement:
TOSCA Defined Control Loop aim to provide Control Loop Service among different ONAP components with a model driven way and using a common catalogue and a common artifact based on TOSCA.
The PoC shall focus on:
- Demonstrate Control loops defined and deployed using TOSCA
- Use a design time catalogue for Control Loops for a complete storage of all the artifacts from different DT systems
- Show design time systems can populate the Design Time control loop catalogue
-DCAE-MOD interacting with the design time catalogue
-SDC interacting with the design time catalogue
- Show TOSCA defined control loops being onboarded and deployed
Owners (one of these should be the Assignee - use @ notation):
Link to HLD/LLD (if any):
Dependency Relationships with Other Projects:
Project Impact (Test Only (TO), Code (C)):
Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.
Integration Leads (use @ notation):
Company Engagement: Ericsson
Attachments
Issue Links
- is blocked by
-
CLSC-9 TOSCA Workflows
-
- In Progress
-
- relates to
-
REQ-478 PoC - TOSCA Defined Control Loop on Honolulu Release
-
- In Progress
-
-
POLICY-2900 Update policy-models TOSCA handling with Control Loop Entities
-
- Closed
-
- mentioned in
-
Page Loading...