The page is intended to summarize all the requirements for Dublin Release.
These requirements have been prioritized by the TSC to realistically fit within the Dublin Release Timeline.
This is not yet the Dublin Release scope. Release Scope will be finalized during the M1 Release Planning.
Projects intended to participate within Dublin release are posted in wiki.
New projects proposal are posted here. These projects need to be reviewed and approved by TSC.
Some of the Use Cases, Functional and non functional requirements are carried over from previous releases as they required multiple releases to be implemented.
The Requirements extracted from SP lists of priorities for Dublin are covered either by the Use Case, the functional requirements, the non functional requirement or within a project scope of work.
- Use Cases
- Functional Requirements
- Non Functional Requirements
TSC Prioritization (Ranking)
- RANK #0 – Special GO - fully covered by involved companies
- RANK #1 – GO “Must Have”
- RANK #2 - GO “Continuity of previous releases”
- RANK #3 – GO if PTLs are OK since the impacted applications are less “stretched” i.e. CLAMP, Policy, DCAE etc.
- RANK #4 – NO GO – Mostly new requirements/features/projects
Use Cases
M1 Scorecard:
- Green: Use Case will be fully implemented and tested
- Yellow: Use Case will be partially implemented. It is possible to identify capabilities for this use case that can be tested (phasing approach).
- Red: Use Case can not be partially delivered, min. requirements can not be met in order to define a testing strategy.
| 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 | HPA Testing confirmed by INTEL | Y | vFW | Policy/(APPC) HPA | vFirewall Use Case Upgrade | XS | All: Test Only except Policy APPC(TO) | Policy: Committed | Policy: Committed | AT&T | ||||
| 1 | HPA HPA Testing confirmed by INTEL | Y | vDNS | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
| 1 | Not part of Dublin scope - no regression test | NA | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||||
| 1 | Not part of Dublin scope - no regression test | NA | Integration Team | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||||
| 1 | HPA Testing confirmed by INTEL | Y | vCPE (Heat) | Integration Team | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
| 2 | Davide/Lin to review and provide final feedback | Y (conditional) | 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 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 provided by Chinamobile, Vodafone, Huawei, ZTE, WindRiver, VMWare, Intel, Lenovo, ChinaTelecom, Fujitsu | ||||
| 2 | 5G Use Case (Dublin) | 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 | 5G Use Case (Dublin) | 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 | 5G Use Case (Dublin) | 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 | 5G Use Case (Dublin) | 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 | 5G Use Case (Dublin) | Y (Conditional) | 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 | SDC: C SDN-C: C DCAE: C OOF: C Policy: C | SDC: NEED REVIEW 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 | 5G Use Case (Dublin) | Y (Conditional) | 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: Reviewing 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: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability (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: No enhancements dev | AT&T, Huawei, Ericsson, Nokia | PNF PNP Enhancements is in development with high corporate commitment | ||
| 2 | 5G Use Case (Dublin) | 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 | 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, |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
Functional Requirements
M1 Scorecard:
- Green: The functional requirement will be fully implemented and tested
- Yellow: The functional requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
- Red: The functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
| 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 | #action - Need to confirm testing resource to Yang Xu and what they will be able to test Bin/Yang to sync-up | 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 | HPA Testing confirmed by INTEL | 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 | 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 | Testing confirmed by INTEL | 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 | POC for Dublin under Multi-Cloud umbrella Testing confirmed by INTEL | #action for Srini/Marco/Yang - identify another repo than demo | 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, Intel | |||||||
| 2 | SO Only Testing confirmed by CM Team (AT&T) | #action - Ajay/Seshu/Ryan to meet and provide low level requirements | 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 AT&T | 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 | 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 | 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 | Move to POC | 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 | Move to POC | 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 | SO Only Testing confirmed by SO Team | 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 | ETSI Alignment SO plugint 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 | ||||||||
| 3 | ETSI Alignment. SOL005 plug-in to SO | (yellow or red?) | ETSI Alignment SO plugint to support SOL005 to connect to an external NFVO | SO, SDC, AA, External API, VFC (underdiscussion) | SO: SOL005 under dicusion with Verizon | |||||||||
| 4 | Architecture did not approve | 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 | Need to confirm testing resource | 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 |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
Non-Functional Requirements
M1 Scorecard:
- Green: The non-functional requirement will be fully implemented and tested
- Yellow: The non-functional requirement will be partially implemented. It is possible to identify capabilities for this non-functional requirement can be tested (phasing approach).
- Red: The non-functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
| 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 | Not committed: Ability to instantiate the entire service with API (VID) | Improve our E2E Process Automation | SO | TSC-53 - Getting issue details... STATUS 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 |
| Need to confirm testing resource to Yang Xu and what they will be able to test #Action-clarifications will be provided on PTL Call concerning Manageability/Footprint optimization 1) have we the resources (dev/test) 2) what are the impacts on the other requirements + backward compatibility & migration path from Casablanca Architecture to Dublin Architecture #action to split per item | 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 | phase 1 manual magic word "run-helm-deploy" in queue at LF, Orange and Log team Move to POC | split per item | CI/CD | OOM + Integration (Infrastructure) | TSC-25 - Getting issue details... STATUS
| 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 | Document as You Code | ALL | Tracked in JIRA - Label: Documentation | |||||||||||
| 1 | #Action - provide findings on the PTL call | Security by Design | Security Subcommittee | ALL | ||||||||||
| 1 | #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 | 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 | 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 | CIST running OOM | PTLs | Need to assess | Infrastructure capacity | ||||||||||
| 2 | See Dublin Release Platform Maturity | #Action - Need to be discussed on the PTL Call | S3P- Geo-Redundancy | OOM/MUSIC Integration to ONAP Components | Dublin Release Platform Maturity | |||||||||
| 2 | Need to confirm testing resource to Yang Xu and what they will be able to test by 2/4 otherwise this item will be descoped | SOL 004 (VNF Package Security) | Samuli Kuusela | SDC, VNFSDK | SDC: | SDC: Partially committed (based on Ericsson contribution) | ||||||||
| 3 | #action - Stephen/SECCOM to follow-up on testing | 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 | Library: In progress portal/sdk and possible so library adjustment PORTAL-348 - Getting issue details... STATUS Infrastructure: dmaap is adding containers, need to work with other teams in red DMAAP-853 - Getting issue details... STATUS as part of overall LOG-487 - Getting issue details... STATUS | 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 | Need to confirm testing resource to Yang Xu and what they will be able to test - to be concluded on 2/4 | 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-330 - Getting issue details... STATUS | Portal | XL | Code: PORTAL TO: Policy, VID | PORTAL (C) |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.