...
•CLAMP interfaces with the following ONAP Components: SDC, DCAE and Policy.
- SDC : Rest based interface exposed by the SDC
- DCAE: Rest based interface exposed by DCAE
- Policy: Rest based interface (the Policy team provide a "jar" to handle the communication).
•CLAMP is separated in 2 areas:
- Design Time(Cockpit/UI to define the templates)
- Templates are pushed to SDC. The template format is TOSCA blueprint, those blueprints will be pushed/provisioned, by SDC, to DCAE orchestration engine.
- policies(operational policies) are pushed/provisioned towards the Policy Component of ONAP. (those policies will be triggered by DCAE during Closed Loop operations).
- 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)
- 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)
There is a plan to move the design part of CLAMP towards the "DCAE design Studio" inside SDC, but this won't be in R1, see below:
...