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 | 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 |
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 | 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 | 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) Policy: Partially committed - TechM resources but scope must be worked out by M2 | 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 | Multi-Cloud, Demo | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | MultiVIM/Cloud: partially committed based on VMware's contribution | VMware | |||||||||
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: Partially committed SO: Partially committed based on ATT resources APPC: C SDNC: N AAI: Partially committed VID: Committed based on Nokia resources Policy: Not committed - per Ajay no need for this release | SDC: not enough resources, stretch goal 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 OOF:
| Orange, AT&T | |||||
3 | Model Driven Control Loop Design (Close Loop sub-committee) | DCAE, CLAMP, Policy | Model driven Control Loop Design This project has been split so that a portion of it can be accomplished in Dublin. The model driven portion of the project is represented on this line and has been committed to with a unrequired stretch goal for DCAE | DCAE: Partial Committed CLAMP: Committed Policy: Committed | DCAE: One requirement cannot be committed due to resource constraint, and it is a needed requirement | AT&T, Nokia | ||||||||
3 | Self Serve Control Loop (Closed Loop Subcommittee) | Scott Blandford | DCAE, Policy, SDC | Model driven Control Loop Design This is the descoped portion of the above project. This is not committed but we may try to get it done if resources emerge over the next couple weeks. | DCAE: Partial Commitment Policy: Partial Commitment SDC: Partial Commitment | DCAE Resource constraints Policy: Resource Constraints SDC: Resource Contrstraints | AT&T | |||||||
3 | 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 | 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 | OOF: Policy Tosca model API and ONAP CLI integration | Intel | |||||||||
4 | Alloted Network Function | ??? | ??? | |||||||||||
4 | VSP Compliance Check | SDC | VSP Compliance Check within SDC (Dublin) | 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 | Improve our E2E Process Automation | SO | - TSC-53Getting 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 | 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. 6 projects have been identified for trial: Logging, Policy, APPC, CLAMP, AAI and ONAP CLI | |||||||||||
1 | oParent Integration to fix vulenaribilities | Security Subcommitee | Integration +ALL | AAI, DCAE, DMaaP, Holmes, Logging, MSB, Multi-Cloud, ONAP CLI, UUI, Policy, Portal, SO, VFC, VNFSDK, AAF,CLAMP, MUSIC: Already Integrated ExtApi: Committed SDC, Modeling, OOM:? CCSDK/SDNC, OOM, APPC, VID: No | CCSDK/SDNC, APPC: dependency on ODL OOF (HAS, OSDF): python, not Java VID: No Resource? | |||||||||
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 | 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) |
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.