...
| Priority | M1 Scorecard | TSC M1 Approval | M3 Scorecard | M3 TSC Approval | M4 Scorecard | TSC M4 Approval | Use Case | Owner(s) | 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, what are gaps/ project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1-regression 3-enhancements |
| Y |
Work done but test is blocked by VID/SO blockers - integration blockers | Y |
Blocked by Integration blocking issues | vFW | Policy/(APPC) HPA | vFirewall Use Case Upgrade | XS | All: Test Only except Policy APPC(TO) | Policy: Committed | Policy: Committed | AT&T | HPA Testing confirmed by INTEL | |||||||||||||||||||||||||||||||||
| 1 |
| Y |
Test blocked by VID/SO blockers - integration blockers | Y |
Blocked by Integration blocking issues | vDNS | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | HPA Testing confirmed by INTEL | |||||||||||||||||||||||||||||||||||
| 1 |
| Y |
Test blocked by VID/SO blockers - integration blockers | Y |
Blocked by Integration blocking issues | vCPE (Heat) | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | HPA Testing confirmed by INTEL | |||||||||||||||||||||||||||||||||||
| 2 |
| Y |
CCVPN Dublin Deliverables for API Freeze Milestone Checklist Multi-sites creation function will be partially implemented. (Has risks on implementation of coding and testing in SDC) - integration blockers | Y |
1. Almost all the coding work in each module has been delivered. (excepts Little work in SO and UUI still in progress, will be hand over ASAP. ) 2. Some remaining ending work will be done by this week. 3. No big risk for integration test. Multi-site creation function, service change function(add/delete a site), close loop bandwidth adjustment function will be tested in the integration test phase. | 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,MultiVIM/Cloud, VFC, Modeling, DCAE, Policy, Holmes, Consistent ID of a cloud region | CCVPN Use Case (Dublin) | AAI: M | AAI: TO DCAE: TO ExtAPI: TO Multi-VIM: Test support Holmes: C | SDC: Partially committed based on Chinamobile/ZTE/Vodafone/Fujitsu contribution SO: Committed based on the contributions from CMCC, ZTE and VDF for the main flows SDN-C/CCSDK : Committed based on contributions from Huawei and ZTE VF-C: Committed Modeling: Committed Usecase-UI: Committed Holmes: Committed based on Huawei and ZTE contribution Multi-VIM/Cloud: Committed based on VMware contribution Policy: Committed base on Huawei contribution ExtAPI: Committed as long as a serviceOrder is created, either for service creation or modification with full service characteristics and values. ExtAPI can not read service characteristic and service state from AAI which does not expose those informations. | Dev/Test provided by Chinamobile, Vodafone, Huawei, ZTE, WindRiver, VMWare, Intel, Lenovo, ChinaTelecom, Fujitsu | |||||||||||||||||||||||||||||||||||
| 2 |
| Y | Y |
Codes delivered and ready for integration tests. 5G - PNF Pre-Onboarding / Onboarding Development Status VNF-SDK-342 is still in progress (Jira) Agreed w Victor
| 5G: PNF Pre-onboarding Onboarding | SDC, VNFSDK, VNFRQTS (Docs) | 5G - PNF Pre-Onboarding & Onboarding | BBS | L | SDC: C VNFSDK: C | SDC: Committed based on Ericsson contribution VNFSDK: Committed based on Nokia contribution VNFRQTS: Committed based on Ericsson contribution | AT&T, Huawei, Ericsson, Nokia | PNF POB/OB U/C is now in development, requirements and architecture stage with high corporate commitment. | ||||||||||||||||||||||||||||||||||
| 2 |
| Y |
| Y |
| 5G: Bulk PM | DCAE, DMaaP, VNFRqmt | 5G - Bulk PM (Casablanca carry-over items) | 5G: PM Dictionary | DCAE: C DMaaP: C | DCAE: Committed based on Ericsson contribution DMaaP: Committed | AT&T, Ericsson, Nokia | Bulk PM is in development with high corporate commitment. | ||||||||||||||||||||||||||||||||||
| 2 |
| Y |
| Y |
Functionality delivered in all impacted projects, except one open issue in SO:
(Bug Fix we are aware of) | 5G: Config w/ NetConf | Oskar Malm | SDC, SO, SDNC, CCSDK, VNFRQTS | 5G - Configuration with NETCONF | 5G: PNF PnP e2e automation | SDC: C SO: C SDNC: C CCSDK: C | SDNC: NETCONF/TLS support in controller committed from Ericsson Additional development (SDC, SO, CCSDK) for PNF configuration UC is coordinated with CDS / e2e automation. See separate row for details. PNF configuration testing: Ericsson SO: (not a separate initiative uses E2E automation) assign/config building block | AT&T, Ericsson | NetConf is in development with high corporate commitment | |||||||||||||||||||||||||||||||||
| 2 |
| Y |
| Y |
Code is delivered | 5G: FM Meta PM Dictionary | SDC, VNFRqmt, VES Specification (Done) | 5G - FM Meta Data / 5G - PM Dictionary | 5G: Bulk PM 5G: PNF OB | SDC: C | SDC: Commit | AT&T, Ericsson, Nokia | FMPM Dictionary is in development with high corporate commitment | ||||||||||||||||||||||||||||||||||
| 2 | Y |
| Y |
Use case is feature complete and code committed. Code delivered for DCAE and Policy. For SDN-C, code delivered for 2 items. SDNC-431,433 moved to El Alto. SDNC-431 code complete but not merged. For OOF code committed, and needs to be merged. <please provide the gerrit links for followup>
| 5G: OOF & PCI | SDC, APP-C, DCAE, OOF, Policy, VNFRqmt | 5G - OOF and PCI (Casablanca carry-over items) | 5G: PNF OB Control Loop U/C | SDN-C: C DCAE: C OOF: C Policy: C | SDNC: TechMahindra with help from AT&T DCAE: Committed based on Wipro contribution OOF: Commit Policy: Committed based on Wipro contribution | AT&T, Wipro, Tech Mahindra | OOF/PCI Enhancements is in development with high corporate commitment Dublin Release Requirements I added policy because my understanding from Dublin Release Requirements there are additions for 5G - OOF and PCI | |||||||||||||||||||||||||||||||||||
| 2 |
Confirmed by Dublin Release Requirements that testing resources have been identified | Y |
| Y |
Code is delivered | 5G: PNF Plug and Play & PNF Re-registration | Benjamin Cheung | SDC, Portal, VID, SO, A&AI, SDN-C, DCAE | 5G - PNF Plug and Play (Casablanca carry-over items) | BBS | SDC: C Port: C VID: C SO: C A&AI: C SDN-C: C DCAE: C AAF: C | Portal: Commit (AT&T) VID: Commit SO: Committed based on the contributions from Nokia (confirmed) A&AI: Commit CCSDK/SDN-C : Committed to Tosca ingest changes DCAE: Committed based on the contributions from Nokia AAF: Commit | AAI: schema / model changes. (Jan 30 James Forsyth has ok'ed A&AI commitment) PORTAL: Targets only the top menu integration required for 5G use case functions from VID and SDC/AAI VID: A&AI schema alignment (agreed) | AT&T, Huawei, Ericsson, Nokia | PNF PNP Enhancements is in development with high corporate commitment | ||||||||||||||||||||||||||||||||
| 2 |
| Y |
| Y |
Code is delivered, Modeling work in progress. | 5G: Network Slicing | Borislav Glozman | SDC, Modeling Sub-committee | 5G - Slicing | SDC: C Model: TO | SDC: Commit Model: Commit | AT&T, Amdocs, Ericsson | Network Slicing has only modeling work that is being done in R4. | ||||||||||||||||||||||||||||||||||
| 2 |
| Y | Y |
Code delivered and into integration stage. | 5G: PNF Software Upgrade | Ulas Kozat | SDN-C | 5G - PNF SW Upgrade (Casablanca carry-over items) | SDN-C: C | SDN-C: Commit based on contributions from Huawei | Huawei | ||||||||||||||||||||||||||||||||||||
| 0 |
| Y |
| Y |
Most of the code has been merged or is pending for review. SO enhancements and APEX policy rule for BBS has been submitted, minor fixes will be done in the next 1-3 days and proceed with testing. | BBS | David Perez Caparros | DCAE, ExternalAPI, Modeling, SDNC, SO | BBS Broadband Service Use Case (Dublin) | PRH - 5G Use Case | AAI: DCAE: C ExtAPI: C SDC: TO SO (using 5G use case PNF discovery and re-registration): TO Policy: TO CLAMP: TO SDNC: C Modeling: design | DCAE: Committed based on contribution from Huawei, TechM and Nokia ExternalAPI: Committed SO: 5G PNF Committed based on the contributions from Nokia /Huawei SDNC: Committed based on contributions from BBS team Modeling: contributions from Swisscom/Huawei/Nokia | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability | Nokia, Swisscom, Huawei, |
...
| Priority | M1 Scorecard | TSC M1 Approval | M3 Scorecard | M3 TSC Approval | M4 Scorecard | TSC M4 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, what are gaps/ project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 |
| Y |
| Y |
| 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 |
| Y | Y |
Pending code review and integration <please provide gerrits awaiting review> | Continuation of HPA (Dublin) | Alexander Vul | VNFSDK, SDC, SO, VF-C, OOF, AAI, Policy, Multi-Cloud | Continuation of HPA (Dublin) | SDC - Jira bugs open, OL001 compatibility requirements addressed. | AAI: TO SO: Code Hardening, Expansion of use-case support, testing | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability | Intel ARM(???) | Development t resources from ARM are required to test HPA support on ARM hardware | ||||||||||||||||||||||
| 2 |
| Y |
| Y |
| Scaling Use Case (Dublin) | Scott Blandford | Main focus on DCAE/CLAMP & Policy | Scaling Use Case (Dublin) | DCAE: TO | CLAMP: Committed (Based on TechM resource commitment) Policy: Committed (Based on TechM Resource Commitment) | ||||||||||||||||||||||||
| 0 |
| Y | Y |
Code delivered in SDC, SO and MultiCloud. Pending Integration. | 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 | Testing confirmed by INTEL | |||||||||||||||||||||||
| 3 |
POC for Dublin under Multi-Cloud umbrella | Y |
| Y |
Day-2 Configuration and Visualization package is pending. <unclear - is it IN - if so provide gerrits> | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | Demo | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | Demo (C) | Only demo repository | Day-2 Configuration and Visualization package is pending. Planning to complete this by RC0. | VMware, Intel | Testing confirmed by INTEL | ||||||||||||||||||||||
| 2 |
SO (AT&T) and VID (Nokia) Testing confirmed by CM Team (AT&T) | Y |
| Y |
VID functionality completed; SO blocked by SDC issue in deploying workflow into SO <no additional code changes | Change Management Dublin Extensions - Flexible designer/orchestrator | SO, VID | Change Management Dublin Extensions | SO (C), VID (C) | SO: Committed (AT&T) VID: pending final decision from Nokia (stretch goal) | AT&T Nokia | ||||||||||||||||||||||||
2 |
Testing confirmed by Orange and AT&T | Y | Y |
Functionality completed; Working on code coverage; code is yet to be merged;The portion of code in APPC has been merged. | Change Management Dublin Extensions - Traffic Migration | APPC, OOF | Change Management Dublin Extensions | APPC (C), OOF (C), A&AI (TO) | APPC: Committed (Orange) OOF: Committed (Orange) | Orange | |||||||||||||||||||||||||
| 2 |
Testing confirmed by AT&T | Y |
| Y |
Feature completed; working on code coverage | Change Management Dublin Extensions - Schedule Optimization | OOF | Change Management Dublin Extensions | OOF (C), Policy (TO) | OOF: Committed (AT&T) | AT&T | ||||||||||||||||||||||||
| 3 |
Testing confirmed by AT&T | Y |
| Y |
| 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 | AT&T commits to finding the required resources | AT&T, Nokia | ||||||||||||||||||||||||
| 3 |
SO Only Testing confirmed by SO Team | Y |
| Y |
| Modularity | SO, SDC, VFC, APPC, SDNC | 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 CDS project will provide Resource assignment functionality | ||||||||||||||||||||||||||
| 3 |
ETSI Alignment SOOL003 plug-in to SO Ericsson confirmed the integration testing resource for the ETSI SOL003-plugin support | Y |
| Y |
Code delivered in SO and A&AI; working on VNFM Simulator for integration testing | ETSI Alignment SO plugin to support SOL003 to connect to an external VNFM | SO, SDC, AAI, | 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 Ericsson AAI: Not Committed | SDC: no resources .AAI: no resources (detailed impact to be discussed) Action Byuong | |||||||||||||||||||||||||
| 4 |
Architecture did not approve | N | OSAM/PNF | ??? | ??? | ||||||||||||||||||||||||||||||
| 4 |
| N | 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 |
| N | Alloted Network Function | ??? | ??? | ||||||||||||||||||||||||||||||
| 3 |
Prabhu Balan – (prabhu.balan1@vodafone.com) from Vodafone. Sean Joseph (sjoseph1@iconectiv.com) from iconnectiv. | Y |
| Y |
| Phase 1 - VSP Compliance Check | SDC CLI/VNFSDK | VSP Compliance Check within SDC (Dublin) | SDC: Committed based on contribution from VF, Huawei and iconectiv | Vodafone, iconectiv, huawei |
...