CLAMP 2017-07-05 Meeting notes

30min

Policy, CLAMP, SDC, Holmes interactions

Ritwick, Martial, Pam, Guangrong, Lingli, Vijay

• Started presentation from Guangrong Fu about how CLAMP and Holmes interact at runtime

• Discussion about how Holmes is setup and instantiated

• Where should Holmes be (DCAE micro service and/or standalone)

• Concerns on which approach is taken and the work it implies (not only in Holmes)

• Decided to organize a call to go through the design time flow

30min

DCAE flow presentation

Vijay, Pam, Ritwick

On-boarding flow :

Each micro service that could be used within a closed loop need to be onboarded first

Each of them will provide a JSON file artifact that will on board the micro-service on DCAE through SDC

includes DMaaP topics, input, output,... specification file in preparation, that file is converted to TOSCA and loaded into SDC catalog

Design flow :

Template design

Closed loop templates are build with a designer after on-boarding (based on the input available from the on-boarding flow)

The template is a a general set of policies for DCAE components (configuration policies for the collectors etc...)

Service and Blueprint design

CLAMP then can create a closed loop blueprint for the closed loop using the CLAMP designer, it gets send to SDC and tested and then eventually distributed to DCAE, this blueprint includes multiple micro-service(chaining)

and their specific configuration that is then used as a basis for runtime

Runtime flow :

Once the blueprint generated is pushed to the DCAE controller, it then can be run from DCAE (as it includes the collection of microservices and chaining information to execute the loop)

CLAMP can trigger the start/stop of the closed loop