...
| Priority | M1 Scorecard | TSC M1 Approval | Functional Requirement | Owner | Project Impacted | Link(s) to HLD/LLD if any | 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 | M4 Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | Consistent ID of a Cloud Region (Dublin) | Bin Yang | SDNC & APPC , VID, SO, UUI, VFC, OOF | Consistent ID of a Cloud Region (Dublin) | APPC(TO, code already exists), SDN-C: test support only | SO: Support testing effort, changes are likely in. VFC:Committed UUI:Committed VID: Committed based on ATT resources | AT&T China Mobile | |||||||
| 2 | Continuation of HPA (Dublin) | Alexander Vul | Components used by vFW, vDNS, vCPE, VoLTE | Continuation of HPA (Dublin) | AAI: TO | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability | ||||||||
| 2 | Scaling Use Case (Dublin) | Scott Blandford | Main focus on DCAE/CLAMP & Policy | Scaling Use Case (Dublin) | CLAMP: Committed (Based on TechM resource commitment) Policy: Committed (Based on TechM Resource Commitment) | |||||||||
| 0 | K8S based Cloud Region Support | Multi-Cloud, AAI, SDC, SO | K8S based Cloud Region Support | AAI: TO | SDC & SO: Committed based on Intel/VMWare contribution AAI: Partially committed | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability | Intel, VMWare | |||||||
| 3 | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | Multi-Cloud, Demo | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | MultiVIM/Cloud: partially committed based on VMware's contribution | VMware | |||||||||
| 2 | Change Management Dublin Extensions | Ajay Mahimkar | APPC, SDNC, OOF, Policy, A&AI, SDC, SO, VID | Change Management Dublin Extensions | APPC (C), SDNC (C), OOF (C), Policy (TO), A&AI (TO), SDC (TO), VID (C) | APPC: Committed (Orange for Traffic Migration) SDNC: Committed (Ericsson for 5G Software Upgrade using NetConf) OOF: Committed (Orange for Traffic Migration, and AT&T for Schedule Optimization) Policy: test only - per Ajay no need for dev for this release A&AI - test only SDC - test only SO: Partially committed based on AT&T resources (for Flexible designer and orchestrator) VID: Committed based on Nokia resources | SDC: not enough resources, stretch goal SDNC: no resources SO: Scope of the changes and effort to be estimated. AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability OOF:
| Orange, AT&T, Ericsson | ||||||
| 3 | Model Driven Control Loop Design (Close Loop sub-committee) | DCAE, CLAMP, Policy | Model driven Control Loop Design | DCAE: AT&T Committed CLAMP: Committed Policy: Committed | DCAE: One requirement cannot be committed due to resource constraint, and it is a needed requirement | AT&T, Nokia | ||||||||
| 3 | Self Serve Control Loop (Closed Loop Subcommittee) | Scott Blandford | DCAE, Policy, SDC | Model driven Control Loop Design This is a stretch goal for Dublin. We are still trying to align resources so that this can be accomplished this release | DCAE: Stretch Goal Policy: Stretch Goal SDC: Stretch Goal | DCAE Resource constraints Policy: Resource Constraints SDC: Resource Contrstraints | AT&T | |||||||
| 3 | Fine-Grained Placement Service (F-GPS) | Multi-Cloud, OOF | OOF: Committed MultiVIM/Cloud: Committed End-to-end Use Case Integration: Stretch Goal (due to several workflow changes) | IBM, AT&T, VMware (Architecture/Modelling), Intel (Architecture), | ||||||||||
| 3 | Modularity | SO, SDC, VFC, APPC, SDNC | https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2 | SDC: Not committed APPC: Not committed SO: Committed based on the code from R3 SDNC: Not committed VFC: Partially committed | SDC: no resources, not enough info APPC: no resources SDNC: no resources VFC: optimize DB microservice | |||||||||
| 3 | ETSI Alignment (SO plug-in) | SO, SDC, AAI, External API | https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2 | SDC: Partially committed (based on Ericsson contribution) SO: Committed (SOL003) based on contribution from Nokia and Ericcson AAI: Not Committed | SDC: no resources SO: SOL005 Under discussion with Verizon. AAI: no resources | |||||||||
| 4 | OSAM/PNF | ??? | ??? | |||||||||||
| 4 | TOSCA Task Force | ??? | https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2 | OOF: Policy Tosca model API and ONAP CLI integration | Intel | |||||||||
| 4 | Alloted Network Function | ??? | ??? | |||||||||||
| 3 | VSP Compliance Check | SDC | VSP Compliance Check within SDC (Dublin) | SDC: Committed based on contribution from VF, Huawei and Iconnectiv | Vodafone, iconectiv, huawei |
...