...
Priority | M1 Scorecard | TSC M1 Approval | 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, what are gaps/ project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | M4 Status | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1-regression 3-enhancements |
| Y | 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 | 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 | 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 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 | 5G: PNF Pre-onboarding Onboarding | SDC, VNFSDK, VNFRqmt (Docs) | 5G - PNF Pre-Onboarding & Onboarding | BBS | SDC: C VNFSDK: C | SDC: Committed based on Nokia/Ericsson contribution VNFSDK: Committed | AT&T, Huawei, Ericsson, Nokia | PNF POB/OB U/C is now in development, requirements and architecture stage with high corporate commitment. | ||||||||||
2 |
| 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 | 5G: Config w/ NetConf | Oskar Malm | SDC, (VID), SO, SDNC, CCSDK, VNFRQTS | 5G - Configuration with NETCONF | 5G: PNF PnP e2e automation | SDC: C (VID) 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 | 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 |
Confirmed by Yang Xu that testing resources have been identified | Y - conditional Integration still has concerns about coverage | 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 | SDN-C: Commit 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 | 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 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 | 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. | ||||||||||
0 |
| #action (Chaker): Add a risk concerning dependenecy with 5G Use Cases: Dublin Risks | 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 | Non 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 | M4 Status | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
| Y | Improve our E2E Process Automation | SO |
https://wiki.onap.org/download/attachments/48529726/ONAP-E2E-Automation-v3.pptx?api=v2 | AAI AAF DMaaP Policy PNF use case (5G) | XL | Code: APPC (CDS) TO: | SDC: CCSDK: SO: OOM: Testsuite: Documentation: AAI: TO | AT&T | ||||||||||||||||||||||||||||||||||
1 |
Container optimization : on –going (eg SDNC) | Testing Strategy https://lists.onap.org/g/onap-tsc/message/4605 Project teams to document the change in image size from Casablanca to Dublin as part of the changes they are making | S3P - Footprint Optimization (Integration with Alpine) | OOM + ALL | SDC: N CCSDK, CLAMP: Committed Multi-VIM/loud: committed Policy: committed DCAE: Not committed | SDC: no resources DCAE: Resource constraint | ||||||||||||||||||||||||||||||||||||||
1 |
Component/memory optimization: Ongoing Assessment | Testing Strategy https://lists.onap.org/g/onap-tsc/message/4605 Project teams to document the change in image size from Casablanca to Dublin as part of the changes they are making | OOM + ALL | SDC: N CCSDK, CLAMP: Committed Multi-VIM/loud: committed Policy: committed DCAE: Not committed | SDC: no resources DCAE: Resource constraint | |||||||||||||||||||||||||||||||||||||||
1 |
Global optimization (e.g. shared DB) - stretch goal=shared PostgreSQL; shared MariaDB | Testing Strategy https://lists.onap.org/g/onap-tsc/message/4605 Project teams to document the change in image size from Casablanca to Dublin as part of the changes they are making | OOM + ALL | SDC: N CCSDK, CLAMP: Committed Multi-VIM/loud: committed Policy: committed DCAE: Not committed | SDC: no resources DCAE: Resource constraint | |||||||||||||||||||||||||||||||||||||||
1 |
Manual PH1 | Yes with limited scope: Manual PH1 | CI/CD | OOM + Integration (Infrastructure) |
| Integration Logging OOM + ALL (helm charts) | L | no except devops/scripts in oom/integration | OOM: Linux Foundation (C) Orange (C) Bell (C) Amdocs (C) Logging: Bell (C) Amdocs (C) Integration: | Amdocs Orange Linux Foundation Bell Huawei | ||||||||||||||||||||||||||||||||||
1 |
| Yes | Document as You Code | ALL | Tracked in JIRA - Label: Documentation | |||||||||||||||||||||||||||||||||||||||
1 |
| Yes with Conditions #Action - provide findings on the PTL call - reviewed at PTL mtg - checklist integrated. | Security by Design | Security Subcommittee | ALL | |||||||||||||||||||||||||||||||||||||||
1 |
| Yes #Action on TSC | Modeling M3 Checklist enhancement | Modeling Subcommittee | SO, SDC, VFC, APPC, VNFSDK | Proposed M3 Checklist modeling updates discussion | VFC: Committed | |||||||||||||||||||||||||||||||||||||
1 |
| #Action - Need to be discussed on the PTL Call Phasing approach: #0 conf change only #1 upgrade with no data schema change #2 upgrade with data schema change | S3P - Provide Upgrade Capabilities | OOM + ALL | Dublin Release Platform Maturity | In Dublin will establish plan & basis for platform release upgrade strategy to be implemented in following release. | ||||||||||||||||||||||||||||||||||||||
1 |
| Y | Move Helm Chart (OOM) at project level | OOM + ALL | During the PTL meeting on 12/17 -it was agreed that No enforcement to make it happen for all project in Dublin release, but expectation to to completed within El Alto release. This could potentially be a S3P items. 6 projects have been identified for trial: Logging, Policy, APPC, CLAMP, AAI and ONAP CLI | |||||||||||||||||||||||||||||||||||||||
1 |
| Y | oParent Integration to fix vulnerabilities | Security Subcommittee | Integration +ALL | Modeling: TO | AAI, DCAE, DMaaP, Holmes, Logging, Modeling, MSB, Multi-Cloud, ONAP CLI, UUI, Policy, Portal, SO, VFC, VNFSDK, AAF,CLAMP, MUSIC: Already Integrated ExtApi, VID: Committed SDC: Not Committed CCSDK/SDNC, OOM, APPC, OOM: No | CCSDK/SDNC, APPC: dependency on ODL OOF (HAS, OSDF): python, not Java SDC: No resource OOM: No java code | ||||||||||||||||||||||||||||||||||||
1 |
| Yes with Conditions Based on PTL call (2/18), procedures to be provided to PTLs Action: rename after review w/Integration team & preso on 2/18 | CSIT CIST running OOM | PTLs | Infrastructure capacity | |||||||||||||||||||||||||||||||||||||||
2 |
| #On the condition that we have testing env across multiple sites | S3P- Geo-Redundancy | OOM (introduction of CNI)/MUSIC capabilities leveraged by initial ONAP Components i.e. OOF, Portal, SDC | Platform Maturity Resiliency Requirements | |||||||||||||||||||||||||||||||||||||||
2 |
| Yes with Conditions: Need to confirm testing resource to Yang Xu and what they will be able to test by 2/18 otherwise this item will be descoped | SOL 004 (VNF Package Security) | Samuli Kuusela | SDC, VNFSDK | SDC:
| SDC: Partially committed (based on Ericsson contribution) | |||||||||||||||||||||||||||||||||||||
3 |
| Yes with Conditions: #action - Stephen/SECCOM to follow-up on integration testing by 2/18 otherwise this item will be descoped Followup on confirming testing resources - not complete | xNF communication security enhancements | AAF, DCAE, Controllers | Slide presented on PTL Call (1/14/2019) | DCAE - Committed based on Nokia's contribution
| ||||||||||||||||||||||||||||||||||||||
4 |
| No | S3P - Service Mesh (ISTIO) | Security & Architecture Subcommittees | ALL except MSB or performed at K8S level (OOM); Poc of ISTIO plug-in to AAF not resourced | 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 |
| No | S3P Manageability - Logging Capabilities | see yellow/red in in progress log, aaf cli, consul, contrib, dcae, dmaap, nbi, oof, sdnc, so, uui, vid, vnfsdk, vvp good aai, appc, clamp, esr, multicloud, policy, pomba, portal, sdc, vfc | Library: In progress portal/sdk and possible so library adjustment
Infrastructure: dmaap is adding containers, need to work with other teams in red
as part of overall
| Log OOM Portal SO AAI | OOM (c) LOG (c) Portal (c) SO (c) AAI (c) Multicloud(c) | LOG/POMBA OOM | Amdocs AT&T Bell Hauwei Intel | |||||||||||||||||||||||||||||||||||
3 |
No particular Integration Testing required. Portal/UUI Teams will provide the testing resources | Locale/Internationalization language support | Portal, UsecaseUI | Internationalization language support | Portal, UsecaseUI | L | Code: | UsecaseUI (C) | ||||||||||||||||||||||||||||||||||||
3 |
Development Stretch Goal for Dublin. No particular Integration Testing required. Portal container at RC0 will be the final version to be tested | Y | Angular 6 Upgrade of ONAP Portal and SDK | Portal |
| Portal | XL | Code: PORTAL TO: Policy, VID | PORTAL (C) |
...