As a CLAMP developer, I want to be able to generalize parsing of blueprint, so that CLAMP can detects the micro-service which are part of the flow and present the GUI(via the corresponding policy-model). using the GUI the user will be able to create/deploy policy(based on the policy model).

(see DCAEGEN2 linked Jira issue for the details about the blueprint specification needed
to retrieve the info needed)

the different element to be implemented should be:

1. parse the blueprint to detect the sequence of micro-service.
2. create the drawing with a sequence of simple boxes with the name of the micro-service. the default collector can now be removed.
3. ensure that by clicking on a box, the GUI to configure the config policy(based on the policy model) is shown and used to deploy the config policy.

CoS:

• Modules should be extracted from DCAE blueprint
• Extracted module should be used to generate SVG  XML.
• Model should be saved to DB from CSAR installer
• Each generated block (microservice) should know it's model id
• After selecting block model id should be used to retrieve model
• Retrieved model must be passed to new logic generating UI from model

To check:

• Possibly we can have whole model combined with block. Not just id.

Questions:

1. How microservices should be connected? (O->O->)?
2. " the default collector can now be removed" - are we sure about that?
   1. It has to stay