...
•CLAMP is separated in 2 areas, which are currently (in seed code) both supported by a single application:
- Design Time(Cockpit/UI to define to Configure the templates)
- the Templates are pushed to (service template) are defined in DCAE-D and distributed to CLAMP by SDC. The template templates format is TOSCA blueprint, those blueprints will be pushed/provisioned. Aside of the service template the corresponding blueprint is also generated by DCAE-D and pushed, by SDC, to DCAE orchestration engine.
- policies (configuration and operational policies) are pushed/provisioned towards the Policy Component of ONAP. (those policies will be triggered by DCAE during Closed Loop operations).
- The DCAE team needs to provide models to Policy team in order for the Configuration policy to be built.
- Run time(DCAE-Policy, grabbing events and triggering policies based actions)
- In the first release of CLAMP, the triggering to deploy(and then effectively start the closed loop) a blueprint will be manual (via CLAMP cockpit) an automatic deployment based on an event will come in future release.
- The CLAMP cockpit will support the following action at runtime:
- start (start the provisioned Closed Loop on DCAE)
- stop (stop a provisioned Closed loop on DCAE)
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| Same as Beijing | API exposed by SDC to get list of Alarms and service information's | Date for which the API is reviewed and agreed | Already available | Link toward the detailed API description |
| Same as Beijing | SDC Client used to get service template (describing control loop flow) and blueprint id( to know which blueprint has been distributed to DCAE for this Control Loop template) | Already available | ||
| Same as Beijing | API exposed by Policy to create/update policies | Already available | ||
| Same as Beijing | API exposed by DCAE to start/stop a Closed Loop | Already available | ||
| Same as Beijing | API exposed by DCAE to trigger the deployment/undeployment of a Control Loop template | Already available | ||
| Same as Beijing | API exposed by DCAE to get status of a Closed Loop | Already available |
...