...
| 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) | HPA Enhancements (For Casablanca Release) | Orange: 2 ATT: 2 China Telecom: 2 China Mobile: 1 Verizon: 2 Vodafone: 2 | VNFSDK: none SDC: VNFSDK, VNFD model Policy: SDC OOF: SO, Policy, AAI AAI: Multi-CLoud | VNFSDK (C) | Policy: Committed based on Intel providing resources OOF: Committed VNFSDK: Committed SDC: committed based on Intel contribution. SO: committed AAI: TBD Multi-Cloud: committed | 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 SO : Committed (with support from ATT resources) | 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. SO:Committed | AT&T | ||
5G/PNF Plug and Play | SDC, SO, SDN-C, A&AI, CDT, Modeling, VID | 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: No impact | Code: VID Test Only: SDC | VID: Not Committed APPC: Not Committed AAI: Not Committed OOF: Partially Committed SDNC: 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 SO: Committed (with resurces from Nokia) | AT&T, Nokia, | ||
5G/PNF Software Version Reporting | CCSDK, SDN-C | Link to Slide | CCSDK: committed SDN-C: committed | AT&T | |||||||
5G/PNF Lifecycle Management Support | CLAMP, SDN-C | Link to Slide | AT&T | ||||||||
5G/performance Analysis and Optimization High Volume and RT Data Collection of PM | DCAE, | Link to Slide | Orange: 2 ATT: 2 China Telecom: 1 China Mobile: 3 Verizon: 3 Vodafone: 3 | DCAE: on DMAAP-DR, OOM | OOF: M DCAE: XL | code change: OOF Code : DCAE | CCSDK: committed SDN-C: committed OOF: Partially committed DCAE: Partially Committed | OOF: Limited resources DCAE: Due to dependency (see notes) + and Edge deployment support for R3, DDS-VES and new analytic platform (flink) not committed due to resource constraint | AT&T, Nokia, Ericsson | DCAE will introduces 3 new services for this FR. HV-VES - Committed by Nokia DataFileCollector- Committed by Ericsson(w/dependency on Dmaap-DR) PM-Mapper - Stretch goal (also w/dependency on Dmaap-DR | |
5G/performance Analysis and Optimization Bulk PM | Oscar Malm | DCAE, DMaaP | Link to Slide | code change: DMaaP Code change: DCAE | AT&T, Nokia, Ericsson | ||||||
5G/performance Analysis and Optimization Optimization Framework Enhancements (Placement, Formulation, Solving) | OOF | Link to Slide | OOF: M | code change: OOF | OOF: Committed to SON | AT&T, Nokia, Reliance Jio ( ? ) | |||||
| 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 | MVP (Plan B, Phase 1) : SO, Integration Stretch goal (Plan B, Phase 2) : SO,VID,SDNC,OOF,VFC, UUI,MultiCloud. | 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 | MVP (Plan B, Phase 1) : SO: committed Integration: committed Stretch goal (Plan B, Phase 2) : SO: not committed VID: Not Committed SDNC: Not committed OOF: Committed MultiCloud:Committed VF-C :Committed UUI: committed | SDNC: Limited resources | To align MVP, propose alternative action plan B: break this requirement into 3 phases. Phase 1 is to centralize the representation of cloud regions; Phase 2 is to apply consistent ID across all related ONAP projects. Phase 3 is to correlate and align dcaeLocation to AAI's cloud region. This phase requires further discussion, hence not listed here. | ||
| 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 specifics on DCAE impact and depends on OOM multisite solution will be supported. |
...