The diagram below outlines the architecture of the TOSCA defined control loop management.

A TOSCA file contains the descriptor of the control loop. The entire control loop definition, including references to required artifacts, are included in the TOSCA file. The TOSCA file may be packaged in a CSAR, which also includes further artifacts that are required to deploy and instantiate a control loop.

1: Overall Architecture

Liam Fallon to pad out

2: Control Loop Modelling

Joseph O'Leary to pad out this section

2.1: Control Loop TOSCA file definition

2.1: Modelling from TOSCA to Deployment Data in Run Time Catalogue

2.2: Modelling from TOSCA to Instance Data Run Time Catalogue

3: APIs and Sequence Diagrams

3.1: Deployment

Ajay Deep Singh to pad out this section

3.1.1: Deployment REST API

3.1.2: Deployment Sequence Diagrams

3.2: Instantiation

Robertas Rimkus to pad out this section

3.2.1: Instantiation REST API

3.2.2: Instantiation Sequence Diagrams

3.2.3: Instantiation DMaaP API

3.2.4: Instantiation Participant API

3.3: Monitoring

3.3.1: Monitoring REST API

3.3.2: Monitoring Sequence Diagrams

3.3.3: Monitoring DMaaP API

3.3.4: Monitoring Participant API

4: Design

4.1: Server Side

4.1.1 Database Schema and JPA

4.1.2: TOSCA Processing

4.1.3: Instance Control

4.1.4: Execution Monitoring

4.2: Participant Side

4.2.1: Participant Agent

4.2.2: Policy Participant Agent

4.2.3: CDS Participant Agent

4.2.4: DCAE Participant Agent

4.2.5: SO Participant Agent

4.3: Client Side

4.3.1: Client SDK: Composition of Control Loop Tosca

4.3.2: Client User Interface

5: MVP

5.1: Goals

5.2: Limitations