This page describes the TOSCA Control PoCs executed in the Guilin and Honolulu releases. Please refer to the TOSCA Control Loops in CLAMP (Not current, see ONAP Documentation) wiki page for the development work in Istanbul.

Details of the demo for this PoC are available here: Participant Full Pipeline PMSH Deployment Demo - How to run...

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 components using a common catalogue for any control loop artifacts and a common format and language for these artifacts (using TOSCA).


Interested to get more information or contribute ?  

Key contacts: Michela Bevilacqua ; Liam Fallon ; Fei Zhang

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


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 in Rel H

Presentation to ARCHCOM: APP LCM_ARCHCOM_REL H_20201201.pdf

Architecture and Design wiki page

Impacts in Rel H


Rel H PoC ticket: REQ-478 - Getting issue details... STATUS

ARCHCOM ticket: ONAPARC-652 - Getting issue details... STATUS

PoC is hosted by Policy project

Contributions in Rel G

Demo at ONAP Virtual Event

Metadata Driven Control Loops

DCAEMOD_CLAMP and Policy interworking_2020_07_01.pptx

cloop_dcae_2020_07_01.zip

Impacts in Rel G

Release requirement for this PoC in Rel G: REQ-402

Jira tracking in ARCHCOM: ONAPARC-605 

PoC is hosted by CLAMP project

Project

Impact

Notes

CLAMP

CLAMP-888

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

CLAMP-889

Create Design Time Catalogue for control loops

CLAMP

CLAMP-890

Create REST interface towards Design Time Catalogue

CLAMP

CLAMP-891

Build interaction between SDC and Design Time Catalogue
CLAMP

CLAMP-892

Build interaction between DCAE-MOD and Design Time Catalogue
CLAMP

CLAMP-893

Build interaction between Design Time Catalogue and Run Time CLAMP


Team Calendar

  1. EDIT THE CALENDAR

    Customise the different types of events you'd like to manage in this calendar.

    #legIndex/#totalLegs
  2. RESTRICT THE CALENDAR

    Optionally, restrict who can view or add events to the team calendar.

    #legIndex/#totalLegs
  3. SHARE WITH YOUR TEAM

    Grab the calendar's URL and email it to your team, or paste it on a page to embed the calendar.

    #legIndex/#totalLegs
  4. ADD AN EVENT

    The calendar is ready to go! Click any day on the calendar to add an event or use the Add event button.

    #legIndex/#totalLegs
  5. SUBSCRIBE

    Subscribe to calendars using your favourite calendar client.

    #legIndex/#totalLegs

  • No labels