...

The clamp functional entity provides the capability to manage runtime control loops.  It provides the capaiblity to

•  configure DCAE applications of the control loop
• Associate policies to the DCAE application
• Configure the oprations to be taken by the cotnrol loop (by creating/updating/deleting operational policies)
• Deploy/un-deploy control loop flow (blueprints) to DCAE
• Control loop visulization. 

Clamp Relise on Policy to communite to App-C/VF-C/SDN-C/SO in runtime, hence these are not part of CLAMP 

2. CLAMP API definitions

CLAMP provides the following interfaces:

...

• Selecting the control loop flow
• entering configuration policy paramaters
• entering operational policy parameters
• Managing lifecycle of DCAE conrol flow blueprint 

...

 Display and update:

xxxxx

Note:   xxxI interface is a CLMAP internal interface.  xxxxE interface is a SDCE external interface

The current API documents can be found at:

• The provided UI interfaces are found at: CLAMP latest user guide

• CLAMP internal APIs can be found: clamp swagger pdf

CLAMP consumes the following Interfaces:

...

Portel is as common capability used by other components, hence not a architectural functional entitiy in itself.

Portal is a GUI platform that provides the ability to integrate different ONAP platform GUIs into a centralized portal.

It provides:

• The capability to allow other ONAP components to run within their own infrastructure while providing common management services and capabitilities in a centralised way
• Provides common capablities such as application onboarding and management, centralized access management and hosting application widgets
• Provides SDK capabilities to access portal capabilities

2. API definitions

Portal does not in itself provide APIs to other ONAP components, the Portal users do.

Clamp however provides multi-language support.

The multilanguage support provides:

• Login user langage settins
• Update user langage settings
• Language options to user
• Ability to add/remove and query supported languages.

 33. Component Description:

A more detailed figure and description of the component.

...

4. known system limitations

Runtime: None

Clamp data redundancy is dependant on kubernetes and the persisten volume.

Clamp appliation redundancy HA reliease on kubernetes

5. Used Models

Clamp uses the following models:

• please fill in (and references if possible)
• << include model that you recieve from SDC >>
• << Include the model that you configure in the policy >>
•  

6. System Deployment Architecture

Clamp consists of 4 containers:

• CLAMP container
• MariaDB container
• Kibana ontainer
• E_Search ontainer
• LogStash container 

...

 7. References

...

: none

Language capability limitations:

• Language support for different screens
• Portal applications that do not use the portal SDK will not get multi-language support. 

5. Used Models

none

6. System Deployment Architecture

None.  Dependant on the user.

...