Project Overview
CLAMP is the place where you manage the runtime of the Control loop in ONAP:- you can configure the parameters of the µS composing the Control Loop:
- this is achieved by creating/updating/deleting policies (configuration policies).
- the above policies will be associated to the deployed µS
- Associate a Control Loop to a Service
- you can configure the Operation to be taken by the Control Loop:
- this is achieved by creating/updating/deleting policies (operational policies).
- you can deploy/un-deploy Control Loop flow(blueprint) to DCAE.
- in separated/independent Docker containers, you have the "Control Loop Dashboard" which is an ELK stack dedicated to display DMAAP messages related to runtime control loop messages (from DCAE/Policy/APPC).
- you can configure the parameters of the µS composing the Control Loop:
New component capabilities for Guilin, i.e. the functional enhancements
enhancement of the model driven approach for Control Loops
- continue Frankfurt work and integrate DCAE-MOD flow
- Use of DCAE-MOD Control Loop flow retrieved from DCAE inventory
- associate Control Loop Flow to Service received from SDC distribution
- enhance internal model to better support model driven approach
New or modified interfaces
- User interface generation will stay the same even though its generation method will change.
Interface naming
CLAMP supports the following interfaces:
- Control Loop Life Cycle Management User interface (LCM UI) for, refer to CLAMPE1 in architecture description(ARC CLAMP Component Description - Frankfurt):
- selecting the Control Loop flow.
- selecting the Service/VNF to be associated with the Flow
- entering configuration policy parameter.
- entering operational policy parameter.
- manage lifecycle of DCAE blueprint (Control Loop flow).
- Control Loop dashboard User Interface based on "Kibana" (ELK stack, completely independent from LCM UI), refer to CLAMPE2 in architecture description(ARC CLAMP Component Description - Frankfurt).
- Control Loop Life Cycle Management User interface (LCM UI) for, refer to CLAMPE1 in architecture description(ARC CLAMP Component Description - Frankfurt):
Reference to the interfaces
for the UI see readthedocs(obviously still under development for Dublin) : CLAMP latest user guide
internal interface are available via swagger : clamp swagger pdf
What are the system limits
none so far, CLAMP is not a in the path of runtime call, so it is not heavily hit by massive amount of call. So auto scaling is not really required
but could be added.DB redundancy/HA relies on kubernetes and persistent volume. mariaDB cluster can be a future improvement
Application redundancy/HA relies on kubernetes.
Involved use cases, architectural capabilities or functional requirements
scaling use cases
- Self Serve Control Loop: Self Serve Control Loops v2
Listing of new or impacted models used by the project (for information only)
None.