...
The goal of the work is to extend and enhance the current ONAP Control Loop support to provide a complete open-source framework for Control Loops. This will enhance the current support to provide TOSCA based Control Loop definition , and development, commissioning and run-time management. The participants that comprise a Control Loop and the metadata needed to link the participants together to create a Control Loop are specified in a standardized way using the OASIS TOSCA modelling language. The TOSCA description is then used to commission, instantiate, and manage the Control Loops in the run time system.
We consider Control Loops at Design Time and Run Time.
At Design Time, there are two capabilities to be supported:
- The capability to allow metadata for participants to be defined for use in control loops. This capability allows external users and systems (such as SDC or DCAE-MOD) to define participants that can take part in a control loop and to define the metadata that can be used on and configured on a participant when it is taking part in in a control loop. The post condition of an execution of this capability is that a participant is defined in the Control Loop Design Time Caltalogue together with sets of metadata that can be used with this participant in control loops.
- The capability to allow Control Loops to be composed. This capability allows users and other systems to create a control loop type by connecting a chain of participants together from the participants that are available in the Control Loop Design Time Catalogue. In an execution of this capability, a user will define the control loop chain, define the connections between participants, will select the correct metadata sets for each participant, and will define the overall control loop metadata. The post condition for an execution of this capability is a Control Loop definition in TOSCA stored in the Control Loop Design Time Catalogue.
The Control Loop today covers 3 phases:
1) Composition
POST_CONDITION: The Control Loop Definition is stored in CL DT Catalogue
2) Deployment to be renamed (as it is used in CLAMP to identify Instantiation phase) My first suggestion is to use Parametrization/Initialization
POST_CONDITION: The Control Loop Instance is stored in CL RT Catalogue
3) Instantiation
POST_CONDITION: The Control Loop Instance is deployed at RT
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...