...
| 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: M SDC:XS Policy: M OOF: S SO: S AAi: S/M Multi-Cloud: M | VNFSDK (C) | Policy: Committed based on Intel providing resources OOF: Committed VNFSDK: Committed SDC: committed based on Intel contribution. SO: committed AAI: committed Multi-Cloud: committed | Intel | |||
| Change Management - Flexible designer/orchestrator | SDC, SO, VID | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | VID: on SO SDC: on SO | SDC:XL VID: M | Code: SO,VID,SDC | VID: Not committed (Note: VID part is "nice to have" - no dependency on VID from other projects) SDC: committed based on Amdocs contribution SO : Committed (with support from ATT resources) | VID: requires additional resources | AT&T | ||
| Change Management - traffic migration | SDNC, APPC, VNFSDK | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | Code: SDNC, APPC | SDN-C: committed APPC: Not committed Orange: Committed | APPC: Not enough details on requirements, plus limited resources | AT&T, Orange, Intel | ||||
| Change Management - 5G PNF software upgrade | APPC, SO, SDC, A&AI, Ansible/EM | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | SDC: Not committed | SDC: missing information on requirements and designe. | AT&T, China Mobile, Huawei | |||||
| Change Management - CM scheduler | OOF, VID VID - Nice to have - the functionality can still be delivered with OOF only (scheduler would need to be invoked through CLI) | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | VID on OOF | VID: S | Code: OOF, VID | OOF: Committed VID: Not committed | OOF: Risk on resources - being worked out VID: requires additional resources | AT&T | ||
Scaling Closed Loop Scaling (High Priority) | Policy, CLAMP, SO, DCAE | Link to Slides | Orange: 1 ATT: 1 China Telecom: 1 China Mobile: 1 Verizon: 3 Vodafone: 1 | CLAMP: on Policy Policy: on SO | CLAMP: M | Code: SO, CLAMP, Policy Test: DCAE | CLAMP: Committed with risks (dependency on Policy) Policy: Committed with risks (TBD) SO: Committed DCAE: Committed | AT&T | |||
Scaling Beijing Fixes (High Priority) | Scott Blandford | APPC, SDNC, SO, AAI, VID | VID: on SO APPC: on SO | VID: XS AAI: XS | Code: APPC, SDNC, SO, AAI | AAI: Committed APPC: Committed SDNC: Committed SO: Committed VID: Committed | AT&T | ||||
Scaling Controller_Topic_ID (Medium Priority) | Scott Blandford | APPC, Policy, SDC, SDNC, SO, VID | Undefined | APPC: Not Committed Policy: Not Committed SDC: Not Committed SDNC: Not Committed SO: Not Committed | Feature Design is not defined | AT&T | |||||
Scaling Homing and Capacity Check (Low Priority) | Scott Blandford | Multi-VIM, OOF, SDNC, SO | OOF: on Multicloud and Policy | OOF: S | Code: OOF, SO, SDNC, Multi-VIM | OOF: Partially Committed | OOF: Resource issue if R2 solution needs to be extended for new policy constraints. | 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: Committed based on Nokia's contribution SDNC: committed SO: Committed (with resources from Nokia) SDC: support based on current sdc capabilities from Beijing. APPC: Not CommittedNo impact AAI: Not Committed No code change, only modeling changes OOF: Partially CommittedNo impact | 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 PNF placement | 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 (native Kafka support) | OOF: M DCAE: L | code change: OOF Code : DCAE | CCSDK: committed SDN-C: committed OOF: Partially committedNo Impact DCAE: Committed (based on Nokia contribution) with dependency risk | OOF: Limited resources | AT&T, Nokia, | DCAE: Edge deployment support for R3, DDS-VES and new analytic platform (flink) not committed due to resource constraint | |
5G/performance Analysis and Optimization Bulk PM | DCAE, DMaaP | Link to Slide | DCAE: on DMAAP-DR | DCAE:L | code change: DMaaP Code change: DCAE | DCAE: Partial CommitData File Collection Committed DMaaP – (Dependency on DMAAP-DR + PMMapper (Stretch goal based on Ericsson contribution) – Not a hard requirement | DCAE: Dependency on DMAAP-DR + PMMapper (Stretch goal based on Ericsson contribution) | AT&T, Ericsson | DCAE:DataFileCollector- Committed (based on Ericsson Contribution) | ||
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, Plan B, Phase 1: Centralized Representation of Cloud Regions | SO, 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 | code : SO, Integration | SO: committed based on Intel's contribution Integration: committed | 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. Note on "Intel's contribution": This is the synergy effort with HPA, no further special changes needed here. hence this can be deemed as a dependency on HPA's impact on SO. | |||||
Centralized Representation and Consistent ID of Cloud Regions, Plan B, Phase 2: Consistent ID of Cloud Regions | 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/SDNC: on SO SO/OOF/VFC: MultiCloud | VID: XS MultiCloud: S VFC:S | code : SO,VID,SDNC,OOF,VFC, UUI,MultiCloud | SO: not committed VID: Not Committed SDNC: Not committed OOF: Committed MultiCloud:Committed VF-C :Committed UUI: committed | SDNC: Limited resources VID: requires additional resources | |||
| Edge Automation Through ONAP (EA) | A&AI, Multi-Cloud, OOF, SO | Orange: 3 ATT: 3 China Telecom: 3 China Mobile: 3 Verizon: 2 Vodafone: 1 | OOF: on MultiCloud Multi-Cloud: on A&AI | AAI: XS SO: XS OOF: M Multi-Cloud: L | Code: OOF, Multi-Cloud, SO, A&AI Test: Integration | Casablanca MVP:
Casablanca Stretch Goal:
|
...