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: OSAM uses the PNF capability similar to 5G use case. No new development efforts were identified to support OSAM using PNF VNFRQTS (include PNFs) | OSAM Material | All: Test Only | ATT, Turk Telecom, Swisscom | . 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 | Code: Policy, OOF, VNFSDK | Policy: Committed based on Intel providing resources OOF: Committed VNFSDK: Committed SDC: commited based on intel contribution. | Intel | ||||
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 SDC: on SO | Code: APPC, SO,SDN-C, OOF, VID,SDC | VID: Not committed APPC: Not committed SDC: committed based on Amdocs contribution SDN-C: committed OOF: Not Committed | VID: requires additional design information APPC: Not enough details on requirements, plus limited resources OOF: Resources to be worked out | AT&T | |||
Scaling | SO, APPC, VF-C, CLAMP, DCAE, Policy, OOM, VID, SDN-C, A&AI, Multi-VIM/Cloud, OOF VNFRQTS,SDC | 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 | CLAMP: Committed with risks (see dependency) VID: Committed APPC: Partially Committed Policy: Committed with risks (TBD) AAI: Committed OOF: Partially committed SDN-C: committed DCAE: Not 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; if R2 homing workflows need to be enhanced. SDC: waiting on controller type decision DCAE: From requirement, appears TO impact; need clarification as DCAE is noted as code impact. | 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 DCAE: on DMAAP-DR, OOM | VID: S AAI: XS? need clarification on what's expected OOF: need clarification on requirements for RAN VNF Homing DCAE: XL | Code: VID Test Only: SDC Code : DCAE | VID: Not Committed APPC: Not Committed AAI: Not Committed OOF: Partially Committed SDNC: committed DCAE: Partially Committed (New service committed based on Ericsson/Nokia) | 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 DCAE: No Edge deployment support for R3. DDS-VES and new analytic platform not committed | AT&T, Nokia, Ericsson | ||
5G/performance Analysis and Optimization | DCAE, OOF, | Orange: 2 ATT: 2 China Telecom: 1 China Mobile: 3 Verizon: 3 Vodafone: 3 | OOF: M | code change: OOF | CCSDK: committed SDN-C: committed OOF: Partially committed DCAE: Not Committed | OOF: Limited resources DCAE: Additional information required to assess impact | |||||
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, Integration. DCAE,DMaaP. (DCAE,DMaaP will only be concerned in case of distributed DACE mS deployment.) | 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 SO/OOF/VFC: MultiCloud | VID: S MultiCloud: S VFC:S | code : SO,VID,SDNC,OOF,VFC, UUI,MultiCloud, Integration Test: DCAE, DMaaP | VID: Not Committed OOF: Committed SDNC: Not committed DCAE: Not committed MultiCloud: Committed VF-C :Committed | SDNC: Limited resources DCAE: Not enough details on requirements. | |||
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 SO: S? OOF: M Multi-Cloud: M | Code: OOF, Multi-Cloud, SO, A&AI, DCAE | Casablanca MVP:
Stretch Goal:
| AAI: Expecting this to be modelling/schema updates only but unclear. Need additional information and analysis by AAI SMEs DCAE: Need clarification on DCAE impact |
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 | Portal: on AAF, MUSIC, OOM VID, Policy, SDC, AAI: on Portal | Portal: XL | Portal: Code | Portal: Not Committed APPC: Partial DCAE:Partial | APPC: Please refer to M1 Planning template for details DCAE: Refer to DCAE R3 M1 Release Planning#PlatformMaturity for details | Portal: IBM (only forAngularupgrade - shown interest, but not committed yet) | Portal: 1) Looking for resources who can help with adhering logging standards, API versioningandkubernetesdeploymentof Portal dockers. 2) Furthermore, Portal requires a security expert in addressing angular upgrade to address the Nexus-IQ reported vulnerability (the angular upgrade its self is XL t-shirt size task). | |
Security | Note: This does not cover what is in S3P. Howeverbasedon 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 toxNFs(Security for 5G Use cases). DCAE, APPC, VFC? VNF requirements. (Secure Communication to Network Functions)
Vnf package security following SOL 004: SDC, VNFreqs, VNF SDC | CADI/AAF Integration: | Portal: on AAF Test coverage (js): (1) js Sonar plug-ins activation (2) min. 3 additional containers per application => Jenkins enhancements (3) Maven build to be updated DMaaP on AAF DCAE on AAF, OOM,DMAAP OOF on AAF | Portal (CADI): M DCAE: XL Test coverage (js): All: M/L | Portal: Code | Portal: Not Committed APPC: Partial OOF: Partial DCAE: Not Committed | APPC: Please refer to M1 Planning template for details DCAE: Refer to DCAE R3 M1 Release Planning#PlatformMaturity for details OOF: Please see OOF Casablanca M1 Release Planning Template | Portal: Looking for resources who understand the AAF based certificate management to upgrade using CADI client in Portal. OOF: Need more clarity on AAF support for python projects in Casablanca | |||
Upgrade (from Beijing to Casablanca) | All: XL | APPC: Not Committed CLAMP: Not Committed DCAE: Not Committed | APPC, CLAMP, Portal, SDC: Lack of resources require additional information (does it include rollback, retrofit, no impact on run-time, etc)? | ||||||||
Architecture Alignment |
| DCAE on DMAAP (for DR) | DCAE:XL | APPC: Under assessment CLAMP: Under assessment DCAE:Partial Commit (New service committed based on Ericsson/Nokia) | DCAE: DDS-VES and new analytic platform (FLINK) not committedduetoresource. xNF-DCAE authentication not committed due to open issue listed under security. | ||||||
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. | Portal: on OOM | Portal: S | Portal: Code | Portal: Not Committed APPC: Will support Heat partially OOF: Support HEAT for testing | Portal: See Risk #4 | Portal: Switching CSIT jobs from using HEAT basedtoOOM based requires resources who can understand the current setup. | ||||
Internationalization language support | Tao Shen |
| Design language/internationalization component in Portal and provideserviceapistopartnering apps like Policy, VID, SDC, AAI Note: This will need to go through the whole process (Architecture review,...) to understand whatthesdk will be providing and dependenciesonother ONAP project (Portal, SDC,...) As per Lingli and Tao from chinamobile, this is reviewed and approved by Arch Team. | UsecaseUI: on Portal | Portal: L | Portal: Code | Portal: Partial APPC: Not Committed CLAMP: Not Committed | Portal: Limited resources | Portal: AT&T, ChinaMobile | Portal: Policy, VID, SDC, AAI can choose to use this Internationalization feature based on their capacity. Only UsecaseUI team is committed to develop and use this feature for now in Casablanca. | |
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) | Policy, VID, SDC, AAI: on Portal (for JavaScript coverage) | Portal: XL SDC:S VID:S | Code: portal, SDC, VID | Portal: Partial (no Javascript) APPC: Partial, Java code will maintain 50%, no commitment for Javascript CLAMP: Partial, Java code will maintain 50%, no commitment for Javascript DCAE:Partial (except javascript) SDC: maintain 50% coverage for java and python add 10% coverage for UI(java script)
VID: maintain 50% coverage for java add 10% coverage for UI (java script) | Portal: AT&T, IBM, TechM | Portal: UI projects may depend on Portal team for pairwise testing |
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.