You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Functional Requirements 

Functional RequirementsOwner

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 projectsIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotes
CLAMP refactoring the blueprint in order to support shared microservices

CLAMP

DCAE

CLAMP refactoring the blueprint in order to support shared microservices







BPG for TOSCA workflowsMichela Bevilacqua

DCAE

CLAMP


BPG for TOSCA workflows







Dynamically changing control loops on-the-fly during runtime

eg Profiles



possibly already covered







CLAMP to support PNF (non-VNF) Control Loops

  • May get covered by Dublin PNF

CLAMP

Policy

CLAMP to support PNF (non-VNF) Control Loops







Policy Design using Filters (targets) and Triggers

Policy

DCAE

CLAMP


Policy Design using Filters (targets) and Triggers







VES Event Registration

CLAMP

DCAE

VES Event Registration







CL Event format standardization to VES

POLICY

DCAE 

Control Loop Event Standarization using VES







Event based Common API for Control Loop Operations


POLICY

Controllers


Event based Common Notification messaging format for Control Loop Operations










  • No labels