...
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The
...
Microservice Bus function provides service registration, discovery and communication services for microservices as well as a gateway for internal & External communication for the services:
Register communication services
Discover communication services
Manage communication between microservices
OOM connects to MSB to register and update service information when it instantiates service endpoints.
Question: How do we differentiate between when to use MSB vs When to use DMaaP?
- Create control loop from DCAE blueprint sent by SDC
- Create configuration policy from the policy Tosca sent by SDC
- Configure DCAE applications of the control loop
- Associate µService configuration policies to the DCAE application
- Configure the operations to be taken by the control loop (by creating/updating/deleting operational policies)
- Deploy/un-deploy control loop flow (blueprints) to DCAE
- Control loop visualization.
CLAMP relies on Policy to communicate to App-C/VF-C/SDN-C/SO in runtime, hence these are not part of CLAMP
2. API definitions
CLAMP provides MSB provides the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities | |||
|---|---|---|---|---|---|
| CLAMPEMSBE-1 | Control Loop Lifecycle Management Interface. | A user interface for:
| Registration and Discovery interface | The registration and discovery interface provides the following capabilities:
| |
| MSBE-2 | Service Request Interfaces | Provides the capability to deliver and recieve a service request and subsequent communication. | |||
| MSBE-3 | MSB Admin Interface | Provides the ability to administer policy and routing for the service requests. | CLAMPE-2 | Control loop dashboard. User interface to show the overall status of the control loop through DMAAP events | Display and update: Events received and actions taken on the control loop. |
Note: xxxI interface is a Component internal interface. xxxxE interface is a component 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
MSB CLAMP consumes the following Interfaces:
| Interface Name | Purpose Reason For Use | ||
|---|---|---|---|
| SDCE-6 | To receive the Control Loop Blueprint from SDCTo receive | ||
| PolicyE-2 | To create and configure the closed Loop Operational Policies and Configuration policies(DCAE Aps. Config.) | ||
| DCAEE-x | Retrieve DCAE appplication status | ||
| N/A | N/A | DCAEE-y | Deploy/remove DCAE application.
3. Component Description:
...
4. known system limitations
Runtime: None
Clamp data redundancy is dependent on Kubernetes and the persistent volume.
Clamp application redundancy HA relies on Kubernetes
MSB API gateway has been tested in this scenario:
- Client(wrk) --> MSB API gateway --> Test service(Tomcat)
- Test machine (client, msb and test service): 8 cpu Core, 8G memory
- Network 10000M
The test result is 50000 request per second.
5. Used Models
Clamp uses the following models:
...
6. System Deployment Architecture
This needs to be updated, what should be here?
MSB Clamp consists of 5 containers:
...
7. New Capabilities in this Release
This release, CLAMP MSB adds the following Capabilities:
...
- add policy-model to the SDC distributionautomatic rendering of configuration policy UI based on the distributed policy model
- better rending of the display of the control loop flow based on the distributed blueprint
- enhanced internal model to better support model driven approach.
8. References
8. References
- Microservice Bus API Documentation
- CLAMP Overview & User Guide: https://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html
- CLAMP internal interfaces: https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf