Versions Compared

Key

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

Overview

A PoC  has been proposed in Rel G timeframe to demonstrate the possibility to adopt a model driven approach in the definition of a control loop and its compoments using a common catalogue for any control loop artifacts and a common format and language for these artifacts (using TOSCA).

Goals

  • Demonstrate Control loops can be defined and deployed using TOSCA
  • Use a design time catalogue for Control Loops for a complete storage of all the artifacts from different DT systems
  • Show design time systems can populate the Design Time control loop catalogue

-DCAE-MOD interacting with the design time catalogue

-SDC interacting with the design time catalogue

  • Show TOSCA defined control loops being onboarded and deployed


A Release requirement has been defined for this PoC in Rel G: REQ-402

Longterm Roadmap

"Knowledge" is a key component for automation and control loops. 

A common knowledge can be used for Monitor, Analyze, Plan and Execute functions.


In Rel G we want to start to address in a PoC the aspect of the catalogue where multiple ONAP components could be involved in the Design Time phase.


A longterm strategy needs to apply the common "knowledge" concept to the entire Control Loop Lifecycle.  

Business Requirements


Participating Companies

Ericsson

AT&T


Contributions

Metadata Driven Control Loops


  • Inputs to Control Loop Subcommittee 2020/07/01:

DCAEMOD_CLAMP and Policy interworking_2020_07_01.pptx

cloop_dcae_2020_07_01.zip


Impacts

Project

Impact

Notes



Create a TOSCA definition for a Control Loop (and its components)


Create Design Time Catalogue for control loops



Create REST interface towards Design Time Catalogue



Build interaction between SDC and Design Time Catalogue


Build interaction between DCAE-MOD and Design Time Catalogue


Build interaction between Design Time Catalogue and Run Time CLAMP

Project Commitment

Project

Commitment

Notes