Versions Compared

Old Version 1

changes.mady.by.user Saul Gill

Saved on

compared with

New Version 2

changes.mady.by.user Saul Gill

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page for general findings around the investigation of the optimal path for CLAMP and Tosca Control Loop Integration.

Tosca handling in CLAMP vs Tosca Control Loop - Findings

  1. CSAR contains the DCAE blueprint to be used to deploy to DCAE but also contains a reference to a microservice policy type. CLAMP, on startup, pulls all the policy types and pulls them periodically after that. Clamp creates LOOP TEMPLATES from in its database from the blueprints. CLAMP uses the reference from the CSAR to associate the relevant microservice policy type with a loop template. Thus, CLAMP knows which monitoring policy type to use for creation of a Loop instance.
  2. As shown in "src/main/java/org/onap/policy/clamp/loop/deploy/DcaeDeployParameters.java", multiple microservices per blueprint may not be supported by CLAMP. How much work would be required to support multiple BPs?