Currently, control loops are VNF oriented, more specifically on VNF orchestration use cases. Here, we are examining how the control loop concept and implementation might be expanded so that it could be used to support PNF use cases.
There are many PNF use cases that are inherently Control Loop "friendly" and can be described in terms of a Monitor→Analyse→Plan→Act autonomic (MAPE) control loop. Such loops are supported today in ONAP control loop for certain VNF orchestration use cases.
Some Proof of concepts have been implemented using PNFs in ONAP, but to date this has been achieved by "pretending" that the PNF is a VNF and adapting one of the existing Control Loop implementations such as the vCPE one to execute the logic of the PNF use case.
The problem statement is "to explicitly support PNFs, PNFs and PNF/VNF use cases in ONAP".
There are a number of categories of PNF related use cases that could be addressed by ONAP control loop support:
Investigate further the boundaries between control loop/blueprint definition at design time and CLAMP capability to configure DCAE application in a control loop (control loop initiation tool)
Allow update of control loops at runtime
add a selected node instance to a control loop
Create a new control loop extending an existing control loop behavior
Ericsson, ......
To bring in direct support for PNFs into ONAP control loops.
The following projects could be impacted.
SDC
A&AI
Modelling
Policy
CLAMP
Controllers
DCAE
Can I update an existing DCAE ms blueprint when a new Control loop is created ?
Can I have multiple Control Loops using the same DCAE ms ?
Further questions: