Control Loop Sub Committee Guilin Release Planning
Functional Requirements
Functional Requirements | Owner | Projects Impacted for Dublin | Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Priority (from SP perspective)? | Dependency (from/to) another project(s)
| T-Shirt Size (XS, S, M, L, XL)* | Project's Impact: Test Only (TO), Code (C) | Committed (C)/Partially Committed (P) or not (N) per Impacted projects | If Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
Self-Serve Control Loops - DCAE MOD continuation from Frankfurt | @Scott Blandford @Vijay Kumar | CLAMP DCAE POLICY | Highest | SDC - must still retain distribution of blueprints and other policy models. | XL |
|
|
| AT&T | Apr 22, 2020 Still planning final details. Will require G and H release. Will be changing out Apache Nifi in G (too much overhead). | |
CLAMP refactoring the blueprint in order to support shared microservices | @Gervais-Martial Ngueko
| CLAMP DCAE | CLAMP refactoring the blueprint in order to support shared microservices | Deferred to H Release |
|
|
|
|
|
| DCAE-MOD provides basic support for this. May roll this into DCAE-MOD |
TOSCA defined Control Loop | @Michela Bevilacqua [Ericsson] @Liam Fallon | DCAE CLAMP
| Highest |
|
|
|
|
| Ericsson | @Liam Fallon - Could we roll into DCAE-MOD? Internal testing with PMH - to see if it could work. | |
Dynamically changing control loops on-the-fly during runtime eg Profiles |
|
| possibly already covered |
|
|
|
|
|
|
|
|
CLAMP to support PNF (non-VNF) Control Loops
| @Liam Fallon | CLAMP Policy |
|
|
|
|
|
|
| Supported via CDS actor being integrated in Frankfurt and the OOF 5G Use Case. | |
Policy Design using Filters (targets) and Triggers | @Pamela Dragosh @Gervais-Martial Ngueko @Liam Fallon | Policy DCAE CLAMP
|
|
|
|
|
|
|
|
| |
VES Event Registration | @Eric Debeau @alok411
| CLAMP DCAE
|
| SDC ? Modeling ? |
|
|
|
|
| Apr 22, 2020 - may need to defer or remove. | |
CL Event format standardization to VES | @Vijay Kumar @alok411 @Former user (Deleted) @matthieu cauffiez
| POLICY DCAE | Low |
|
|
|
|
| AT&T Bell Canada | Need a use case to need a VES output to Policy. Alok has a draft. | |
Event based Common API for Control Loop Operations | @Pamela Dragosh @Rushmep @Former user (Deleted) @Liam Fallon
| POLICY Controllers
| Event based Common Notification messaging format for Control Loop Operations
| Low |
|
|
|
|
|
|
|
Distributed Control Loop Deployment
| ?
| DCAE CLAMP Controllers |
|
|
|
|
|
|
| Need a use case to drive this. | |
CLAMP create/deploy of native policies | @Jorge Hernandez @Gervais-Martial Ngueko | CLAMP POLICY | Medium |
| S |
|
|
| AT&T |
|