The page is intended to summarize all the requirements for Casablanca Release. These requirements will need to be prioritized to realistically fit within the Casablanca Release Timeline.
This is not yet the Casablanca Release scope. Release Scope will be finalized by M1 Release Planning.
Projects intended to participate within Casablanca 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 Amsterdam and Beijing Releases as they required multiple releases to be implemented.
The Requirements extracted from SP lists of priorities for Casablanca are covered either by the Use Case, the functional requirements, the non functional requirement or within a project scope of work.
Use Cases
| Use Case | Owner | Projects or functional requirements Impacted for Casablanca | Link(s) to High Level Design (HLD) /Low Level Design (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 |
|---|---|---|---|---|---|---|---|---|---|---|
| vFW | AT&T | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||
| vDNS | AT&T | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||
| VoLTE | China Mobile | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||
| vCPE | Kang Xi | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | |||||
| CCVPN | DCAE, SO,...? NOTE: No project should be code impacted by this use case. | Materials Lin Meng. Material Jianguo Zeng | All; Test Only | China Mobile, Vodafone | Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement | |||||
| OSAM/PNF | SO, Portal, External API, APPC, DCAE HPA **NOTE: Based on Arch review, no projects should be code impacted VNFRQTS (include PNFs) | OSAM Material | All: Test Only | ATT, Turk Telecom, Swisscom | OSAM uses the PNF capability similar to 5G use case. No new efforts were identified to support OSAM using PNF. Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement |
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
| Functional Requirements | Owner | Projects Impacted for Casablanca | Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Priority (from SP perspective) | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| HPA | VNFSDK (minor), SDC (minor), Policy, OOF (minor), SO (minor) VNFRQTS | HPA Enhancements (For Casablanca Release) | Orange: 2 ATT: 2 China Telecom: 2 China Mobile: 1 Verizon: 2 Vodafone: 2 | Policy: on SDC OOF: on AAI, Policy | |||||||
| Change Management | SDC, SO, VID, SDNC, APPC, VNFSDK, OOF, VF-C VNFRQTS | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | VID: on OOF, SO | Code: APPC, SO,SDN-C, OOF, VID,SDC | VID: Not committed APPC: Not committed SDC: committed based on Amdocs contribution | VID: requires additional design information APPC: Not enough details on requirements, plus limited resources | AT&T | |||
| Scaling | SO, APPC, VF-C, CLAMP, DCAE, Policy, OOM, VID, SDN-C, A&AI, Multi-VIM/Cloud, OOF VNFRQTS | Link to Slides | Orange: 1 ATT: 1 China Telecom: 1 China Mobile: 1 Verizon: 3 Vodafone: 1 | CLAMP: depend on Policy VID: on SO APPC: on SO Policy: on SO OOF: on MultiCloud, Policy | VID: XS CLAMP: M AAI: XS OOF: S | Code: SO, APPC, CLAMP, DCAE, Policy, OOM, VID, SDN-C, A&AI, Multi-VIM/Cloud, OOF Test Only: SDC | CLAMP: Committed with risks (see dependency) VID: Committed APPC: Partially Committed Policy: Committed with risks (TBD) AAI: Committed OOF: Partially committed | APPC: Only committing to requirement to retrieve configuration data from AAI; Support for Controller Type currently a stretch goal until requirement are more defined OOF: Limited resources | AT&T | ||
| 5G/PNF | SDC, SO, DCAE, SDN-C, App-C, A&AI, CDT, Modeling, VID, OOF VNFRQTS | Link to Slide | Orange: 2 ATT: 1 China Telecom: 3 China Mobile: 1 Verizon: 1 Vodafone: 2 | VID: on SO | VID: S AAI: XS? need clarification on what's expected OOF: need clarification on requirements for RAN VNF Homing | Code: VID Test Only: SDC | VID: Not Committed APPC: Not Committed AAI: Not Committed OOF: Partially Committed | VID: Additional information required APPC: Per review of slides, does not appear to be anything specific for APPC in Casablanca. Items mentioned are more longer term, roadmap items AAI: Expecting this to be modelling/schema updates only but unclear. Need additional information and analysis by AAI SMEs OOF: Additional information required on policies required for RAN VNF Homing | |||
| 5G/performance Analysis and Optimization | DCAE, OOF, SDN-R | Orange: 2 ATT: 2 China Telecom: 1 China Mobile: 3 Verizon: 3 Vodafone: 3 | |||||||||
| 5G/Network slicing | Withdrawn from Casablanca release by the requirement owner | Orange: 3 ATT: 3 China Telecom: 1 China Mobile: 2 Verizon: 2 Vodafone: 3 | |||||||||
Centralized Representation and Consistent ID of Cloud Regions | SO,VID,SDNC,OOF,VFC, UUI,MultiCloud, DCAE, DMaaP, Integration | Centralized Representation and Consistent Identification of Cloud Regions In ONAP | Orange: 1 ATT: 2 China Telecom: 2 China Mobile: 3 Verizon: 1 Vodafone: 1 | VID: on SO | VID: S | code : SO,VID,SDNC,OOF,VFC, UUI,MultiCloud, Integration Test: DCAE, DMaaP | VID: Committed OOF: Partially Committed | OOF: Limited resources | |||
| EA/Cloud Infrastructure for Distributed Edge Clouds (5G etc.) | Policy, Multi-Cloud, A&AI, ESR, OOF, SO, DCAE, OOM (minor) | Orange: 3 ATT: 3 China Telecom: 3 China Mobile: 3 Verizon: 2 Vodafone: 1 | OOF: on MultiCloud, AAI | AAI: XS? need clarification on what's expected OOF: M | code: OOF | AAI: Expecting this to be modelling/schema updates only but unclear. Need additional information and analysis by AAI SMEs |
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.
Abbreviations:
- Edge Automation through ONAP - EA
Non Functional Requirements
| Non Functional Requirements | Owner | Sub-category | Project Impacted for Casablanca | Link(s) to High Level Design (HLD) /Low Level Design (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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| S3P |
| Likely ALL depending upon TSC determination of new level requirements per category | Usability: New API’s adhere to Versioning strategy Manageability: Adherence to ONAP Logging Spec v1.2 | ||||||||
| Security | Note: This does not cover what is in S3P. However based on that it is expected to have a certificate or use CADI to get certificates to enable secure communication Pluggable authentication and Authorization (Use of CADI and ?):
Secure communication to xNFs (Security for 5G Use cases). DCAE, APPC, VFC? VNF requirements. (Secure Communication to Network Functions)
Vnf package security following SOL 004: SDC, VNF reqs, VNF SDC | CADI/AAF Integration:
| Test coverage (js): (1) js Sonar plug-ins activation (2) min. 3 additional containers per application => Jenkins enhancements (3) Maven build to be updated | Test coverage (js): All: M/L | |||||||
| Upgrade (from Beijing to Casablanca) | All: XL | ||||||||||
Architecture Alignment |
| ||||||||||
| HEAT support | HEAT-based ONAP deployment support should be dropped once OOM-based ONAP deployment's issues are fully identified and resolved. Recommendation from TSC: keep supporting HEAT in Casablanca for testing and integration purposes. However, HEAT won't be a gating item at Release Sign-Off. | ||||||||||
| Tao Shen |
|
Note: This will need to go through the whole process (Architecture review,...) to understand what the sdk will be providing and dependencies on other ONAP project (Portal, SDC,...) | |||||||||
| Testing | Helen Chen |
| Most UI projects with javascript. Recommendation from TSC: This is related to Code Coverage: recommendation is to keep 50% Code Coverage for Casablanca including JavaScript. (In Beijing Release code coverage was only covering Java and Python code) |
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.