...
| 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, 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,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 | 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 : 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. | 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, Policy | 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 Policy: Committed based on wipro contribution | 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 | - Benjamin Cheung I added policy because my understanding from N.K. Shankaranarayanan there are additions for 5G - OOF and PCI | |||||||
| 0 | BBS | David Perez Caparros | DCAE, ExternalAPI, Modeling, SDNC, SO | BBS Broadband Service Use Case (Dublin) | PRH - 5G Use Case | AAI: TO (to be confirmed) DCAE: C ExtAPI: C SDC: TO SO (using 5G use case PNF discovery and re-registration): TO (to be confirmed) Policy: TO CLAMP: TO SDNC: C Modeling: design | DCAE: Committed based on contribution from Huawei, TechM and Nokia ExternalAPI: Committed SO: 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, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | M4 Status | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 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 | S3P - Footprint Optimization | OOM + ALL | https://wiki.onap.org/download/attachments/45293323/Dublin-Footprint-Optimizations.pdf?version=1&modificationDate=1544543600000&api=v2 | SDC: N CCSDK, CLAMP: Committed Multi-VIM/loud: committed Policy: committed | SDC: no resources | |||||||||||||||||||
| 1 | CI/CD | Infrastructure |
| Integration Logging OOM | L | no | OOM: Bell (C) Amdocs (C) Logging: Bell (C) Amdocs (C) Integration: | |||||||||||||||||
| 1 | Document as You Code | ALL | Tracked in JIRA - Label: Documentation | |||||||||||||||||||||
| 1 | Security by Design | Security Subcommittee | ALL | |||||||||||||||||||||
| 1 | Modeling M3 Checklist enhancement | Modeling Subcommittee | SO, SDC, VFC, APPC, VNFSDK | Proposed M3 Checklist modeling updates discussion | VFC: Committed | |||||||||||||||||||
| 1 | S3P - Provide Upgrade Capabilities | OOM + ALL | Dublin Release Platform Maturity | CLAMP: Committed | ||||||||||||||||||||
| 1 | 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. 4 projects have been identified for trial: Logging, Policy, APPC and Clamp | |||||||||||||||||||||
| 1 | oParent Integration to fix vulenaribilities | Security Subcommitee | Integration +ALL | AAI: Already Integrated | ||||||||||||||||||||
| 1 | CIST running OOM | PTLs | Need to assess | Infrastructure capacity | ||||||||||||||||||||
| 2 | S3P- Geo-Redundancy | OOM/MUSIC Integration to ONAP Components | Dublin Release Platform Maturity | |||||||||||||||||||||
| 2 | SOL 004 (VNF Package Security) | Samuli Kuusela | SDC, VNFSDK(?) | SDC: Partially committed (based on Ericsson contribution) | ||||||||||||||||||||
| 3 | PNF/xNF communication security enhancements | AAF, DCAE, Controllers | Slide presented on PTL Call (1/14/2019) | DCAE - Committed based on Nokia's contribution | ||||||||||||||||||||
| 4 | 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 | 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 | ??? | |||||||||||||||||||||
| 3 | Locale/Internationalization language support | Portal, UsecaseUI | Internationalization language support | Portal, UsecaseUI | L | Code: | UsecaseUI (C) | |||||||||||||||||
| 3 | Angular 6 Upgrade of ONAP Portal and SDK | Portal |
| Portal | XL | Code: PORTAL TO: Policy, VID | PORTAL (C) |
...