...
| Priority | Use Case | Owner | Projects or functional requirements impacted for Dublin | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size | Project's Impact: Test Only (TO), Code (C) | Committed (C)/ Partially Committed (P) or not (N) per impacted project | If Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | M4 Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
1-regression 3-enhancements | vFW | Policy/(APPC) HPA | vFirewall Use Case Upgrade | XS | All: Test Only except Policy APPC(TO) | Policy: Committed
| Policy: Committed | AT&T | ||||
| 1 | vDNS | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
| 1 | VoLTE | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
| 1 | vCPE with or without TOSCA | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
| 2 | CCVPN Use Case(Dublin) High priority:1, SD-WAN Multi-site to Multi-site service creation; 2, Service change: add or delete a site;3, close loop intelligent surveillance | SDC, SO, SDN-C,OOF,ExternalAPI, UUI, ESR,Modeling,M-cloud, VFC, DCAE, Policy, Holmes | CCVPN Use Case (Dublin) | AAI: M | AAI: TO DCAE: TO ExtAPI: TO? Multi-VIM:? | SDC: Partially committed based on Chinamobile/ZTE/Vodafone contribution SO: Committed based on the contributions from CMCC, ZTE and VDF for the main flows SDN-C/CCSDK : Committee based on contributions from Huawei and ZTE VF-C: Committed Usecase-UI: Committed Holmes | SDC: not enough resources | Dev/Test privided by Chinamobile, Vodafone, Huawei, ZTE, WindRiver, VMWare, Intel, Lenovo, ChinaTelecom, Fujitsu | ||||
| 2 | 5G | SDC, SO, VNFSDK, AAI, DCAE, SDNC,CCSDK,VID, PORTAL, AAI/ESR, VFC,APPC, DMaaP | 5G Use Case | AAI: M | SDC: Committed based on Nokia/Ericsson/Amdocs contribution DCAE: Committed based on Ericsson contribution for 5G - Bulk PM (Casablanca carry-over items) and Wipro contribution on - 5G - OOF and PCI SO: Partial Committed based on the contributions from Nokia (to be confirmed) AAI: Partially committed CCSDK/SDN-C : Committed to Tosca ingest changes PORTAL: Partial committed VID: Partial committed | SO: Resource commitment to be confirmed AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability PORTAL: Targets only the top menu integration required for 5G use case functions from VID and SDC/AAI VID: No enhancements dev | ||||||
| 0 | BBS | David Perez Caparros | DCAE, ExternalAPI, Modeling, SO | BBS Broadband Service Use Case (Dublin) | PRH - 5G Use Case | AAI: TO | DCAE: Committed based on contribution from Huawei, TechM and Nokia ExternalAPI: Committed SO: Committed based on the contributions from Nokia /Huawei? | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability | Nokia, Swisscom, Huawei |
...
| Priority | 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) | SO: Support testing effort, changes are likely in. SDN-C: test support only VFC:Committed UUI:Committed VID: Committed based on ATT resources | ||||||
| 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) | SDC & SO: Partially committed (based on solution and TechM contribution) | SDC and SO : Stretch goal | ||||||
| 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 | MultiCloud + Demos | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | |||||||||
| 2 | Change Management Dublin Extensions | Ajay Mahimkar | SDC, SO, VID, OOF, Policy, AAI, SO, OOF, AAI, APPC/SDNC | Change Management Dublin Extensions | AAI: Small | APPC(C: done by Orange) | SDC: N SO: Partially committed based on ATT resources APPC: C SDNC: N AAI: Partially committed VID: Committed based on Nokia resources | SDC: no resources 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 | Orange, AT&T | |||
| 3 | Model driven Control Loop Design (part of Close Loop sub-committee) | SDC, DCAE, CLAMP, Policy | Ease of creating analytic components and on-boarding DCAE micro services | SDC: TBD DCAE: Partial Commit CLAMP: Committed APPC: Committed | DCAE: Not all requirement can be committed due to resource constraint | AT&T, Nokia | ||||||
| 3 | Fine-Grained Placement Service (F-GPS) | Multi-Cloud, OOF | https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2 | |||||||||
| 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 | |||||||||
| 4 | Alloted Network Function | ??? | ??? |
...