...
| draw.io Diagram | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
1 Terminology
This section describes the terminology used in the system.
...
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Following the ONAP Reference Architecture, the architecture has a Design Time part and a Runtime part.
...
At runtime, interaction between ONAP platform services and application microservices are relatively unconstrained, so interactions between Control Loop Elements for a given Control Loop Instance remain relatively unconstrained. A proposal to support access-controlled access to and between ONAP services will improve this. This can be complemented by intercepting and controlling services accesses between Control Loop Elements for Control Loop Instances for some/all Control Loop types.
...
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
At design time, the Control Loop type definition specifies the type of API gateway configuration that should be supported at Control Loop and Control Loop Element levels.
...
Additional isolation and execution-environment sandboxing can be supported depending on the Control Loop Element Type. For example: ONAP policies for given Control Loop Instances/Types can be executed in a dedicated PDP engine instances; DCAE or K8S-hosted services can executed in isolated namespaces or in dedicated workers/clusters; etc..
4.4 Security and Multi Tenancy
...
...
5 APIs and Protocols
The APIs and Protocols used by CLAMP for Control Loops are described on the pages below:
- System Level Dialogues
- Defining Control Loops in TOSCA for CLAMP
- REST APIs for CLAMP Control LoopsAutomation Composition
- The CLAMP Control Loop Automation Composition Participant Protocol
6 Design and Implementation
...