Page Comparison

...

ATTENDEES

NOTES

• Metadata Driven Control Loops
  • Liam: Setting up a chain of microservices is gist of this requirement
  • Martial: CLAMP gets that via SDC, CLAMP configures each piece of the chain, submit the blueprint to DCAE. After that, the dashboard just collects information.
    • Would like to extend CLAMP to be able to massage the flow received from SDC, to decide if a uS is to be shared vs deployed for that control loop. CLAMP needs a UI for that, and DCAE to accept that new deployment. DCAE inventory exposes an API to send a new blueprint.
    • Make a model for different interface for deployment of blueprints and other actions, so they are generic.
  • Liam: Would like to add in other components, like Machine Learning/AI
  • Timo: DCAE is drifting towards being a generic orchestrator. ONAP already has these.
  • Timo: Suggestion that maybe it is best to model the Control Loops as TOSCA Topology Templates. Can be translated by DCAE Controller into a Blueprint. Parts should be able to run externally from ONAP/DCAE etc. Support from orchestrator for instantiating these pieces.
  • Timo: Content of the CSAR, show CSAR examples
• Self Serve
  • Vijay: DCAE delivered in Dublin a new tool that solves the blueprint generation problem for a single uS.
    • Need to add the new Policy Model generation into that DCAE tool.
    • Adam: Used TOSCA-Lab, not sure everyone needs to use it. Hard to create a JSON without a specification, don't know what TOSCA-Lab will produce.
    • Vijay: DCAE-DS needs to be adapted to support composite services. Need to close gap on what the new blueprint generator tool. eg. support same translation.
    • Ofir: DCAE-DS uses TOSCA-Lab to generate the files, just as it did in Casablanca. Are you suggestion to use blueprint generator?
      • Would like a meeting to understand the blueprint generator API

RECORDING