...
| 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: Partially OOF: Committed VNFSDK: Committed SDC: commited based on intel contribution. | Policy: Resources | 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.DMaaP, Integration (DCAE,DMaaP will only be impacted 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 OOF: M | code: OOF, DCAE | OOF: Committed Multi-Cloud: Committed SO/AAI: In progress DCAE: Not committed | 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 |
...