Control Loop Subcommittee

Initial Proposal:

Initial Meeting will start in December 2017

Wednesdays 3pm UTC (10am EST) TENTATIVE - Looking to find a spot that does not conflict with DST or other sub committees

TBD -

Coordinate the projects involved in implementation of Control Loop for the use cases in each release.

Wiki – One-stop wiki page that can organize all the architectural and flow diagrams expected for the Use Cases targeted for a Release.
Architectural Diagram – Work with Architecture Sub Committee to provide architecture diagrams for Control Loop Design, Instantiation and Runtime Execution.
Flow Diagrams – Work with the relevant project teams to provide Flow Diagrams for creating Control Loops during Design Time Service Design and Flow Diagrams for Control Loop Runtime Instantiation and Execution.
Model definition (In coordination with Modeling, VNFSDK, VNF Requirements Sub Committees) – Coordinate the models for VNF Vendor Recommendations for Control Loops, Models for DCAE Microservices, Models for Policy Configuration/Operational Control Loop Policies, etc.
Project Requirements – Work with required Project teams to ensure commitments and deliverables for Control Loop Use Cases for a release. The Core teams are DCAE/CLAMP/Policy, but ultimately most projects are involved (APPC/VFC/SO/Dmaap/SDC/AAI to name a few).
Integration Testing Requirements – Work with the integration test team to build E2E Testing Scripts for Control Loop Design, Instantiation and Runtime Execution
Documentation Requirements – Work with the documentation team to build documentation on how the community can build, design and test Control Loops.

Pamela Dragosh - AT&T Research

Grzegorz Tysczka - Orange