CLAMP R7 - Architecture Review (done with Architecture team the 28th July 2020)

Project Overview
CLAMP is the place where you manage the runtime of the Control loop in ONAP:

1. you can configure the parameters of the µS composing the Control Loop:
   1. this is achieved by creating/updating/deleting policies (configuration policies).
   2. the above policies will be associated to the deployed µS
   3. Associate a Control Loop to a Service
2. you can configure the Operation to be taken by the Control Loop:
   1. this is achieved by creating/updating/deleting policies (operational policies).
3. you can deploy/un-deploy Control Loop flow(blueprint) to DCAE. 
4. 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).

New component capabilities for Guilin, i.e. the functional enhancements

1. None (waiting finalization of DCAE-MOD interface design to continue Self Serve Control-Loop)

New or modified interfaces

1. None.

Interface naming

CLAMP supports the following interfaces:

1. Control Loop Life Cycle Management User interface (LCM UI) for, refer to CLAMPE1 in architecture description(ARC CLAMP Component Description - Guilin and ARC CLAMP Component Description - Guilin (R7) Release (New)):
   1. selecting the Control Loop flow.
   2. selecting the Service/VNF to be associated with the Flow 
   3. entering configuration policy parameter.
   4. entering operational policy parameter.
   5. manage lifecycle of DCAE blueprint (Control Loop flow).
2. 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 - Guilin and ARC CLAMP Component Description - Guilin (R7) Release (New)). 

Reference to the interfaces

1. for the UI see readthedocs(obviously still under development for Dublin) : CLAMP latest user guide

2. internal interface are available via swagger : clamp swagger pdf

What are the system limits

1. 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.

2. DB redundancy/HA relies on kubernetes and persistent volume. mariaDB cluster can be a future improvement

3. Application redundancy/HA relies on kubernetes.

Involved use cases, architectural capabilities or functional requirements

1. scaling use cases (Test only for CLAMP)

2. Self Serve Control Loop: Self Serve Control Loops v2 (design only in Guilin for CLAMP)

3. Support of Native Policy(Test Only for CLAMP)
4. Support of Policy Filtering(Test Only for CLAMP)

Listing of new or impacted models used by the project (for information only)

1. None.