Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: update status for 5g Bulk PM.

...

Functional RequirementsOwner

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 projectsIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotesM4 Status
HPA

VNFSDK (minor)
SDC (minor)
Policy
OOF (minor)
SO (minor)
AAI,
Multi-Cloud
VNFRQTS

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)
SDC (TO/C)
Policy (C)
OOF (C)
SO (C/TO)
AAI (C)
Multi-Cloud (C)


Policy: Committed based on Intel providing resources

OOF: Committed

VNFSDK: Committed

SDC: committed based on Intel contribution.

SO: committed

AAI: committed based on Intel resources.

Multi-Cloud: committed



Intel
China Mobile
AT&T
VMware
ARM


Status
colourGreen
titleOn Track

All code has been or will be submitted

Status
colourGreen
titleOn Track

Unresolved dependency on SDC - two bug fixes required.

Update: Oct 18: the bugs on SDC have been addressed

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, Amdocs


Status
colourGreen
titleM4 Ready

Details

Status
colourGreen
titleM4 Ready

Details

Change Management - traffic migrationSDNC, APPC, VNFSDKLink 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 resourcesAT&T, Orange, Intel

Status
colourGreen
titleM4 Ready

Details

Status
colourGreen
titleM4 Ready

Details

Change Management - 5G PNF software upgradeSO, A&AI, Ansible/EC - test only support; SDNC/CCSDK- dev to incorporate 5G PNFsLink to Slide

Orange: 1

ATT: 1

China Telecom: 2

China Mobile: 2

Verizon: 1

Vodafone: 2



SDN-C: Committed
AT&T, China Mobile, Huawei

Status
colourGreen
titleM4 Ready

Details

Status
colourGreen
titleM4 Ready

Details

Status
colourGreen
titleON TRACK

Ansible playbooks have been submitted. SDN-C NB related LCMs started to support PNF operations

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 OOFVID: SCode: OOF, VID

OOF: Committed

VID: Not committed

(this can still be delivered with OOF)


VID: requires additional resources

AT&T

Status
colourGreen
titleM4 Ready

Details

Status
colourGreen
titleM4 Ready

Details

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

Status
colourGreen
titleOn Track

All code has been or will be submitted

Scaling

Beijing Improvements

(High Priority)

 Scott BlandfordAPPC, 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

Status
colourGreen
titleOn Track

All code has been or will be submitted

(VID is having issues with test environment) 

Scaling

Controller_Topic_ID

(Medium Priority)

 Scott BlandfordSO

Code: SO

SO: Committed


 AT&T

Status
colourGreen
titleOn Track

All code has been or will be submitted

Scaling

Homing and Capacity Check

(Low Priority)

 Scott BlandfordMulti-VIM, OOF, SDNC, SO OOF: on Multicloud and PolicyOOF: SCode: OOF, SO, SDNC, Multi-VIM OOF: Partially CommittedOOF: Resource issue if R2 solution needs to be extended for new policy constraints. AT&T

Status
colourRed
titlePostponed
Pushed to Dublin

5G/PNF

Plug and Play

SDC, SO, SDN-C, A&AI, CDT, Modeling, VID, DCAE, DMaaP

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

Code : DCAE


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: No impact

AAI: No code change, only modeling changes

OOF: No impact

DCAE: committed

DMaaP: committed

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


DCAE: Committed based on Nokia's contribution on PRH

AT&T, Nokia,

Status
colourGreen
titleSUBMITTED

Code has been developed and submitted.

Status
colourGreen
titleON TRACK

SO Code Merge. Health Checks for PRH done in DCAE.

Status
colourRed
titlePENDING

E2E.Test cases need to be updated (for integration & testing) after1st run of whole flow. Sunny Day scenarios to be prepared (for testing).

5G/PNF

Software Version Reporting

 CCSDK, SDN-CLink to Slide



CCSDK: committed

SDN-C: committed


AT&T



Status
colourGreen
titleON TRACK

A&AI and SDC support has been developed.

Status
colourRed
titlePOSTPONED

Usage in the 5G Software Upgrade Use Case is pushed to Dublin

5G/PNF

Lifecycle Management Support

(Restart, Suspend of PNF)

SDN-C/SDN-R. Controller support for operations. SDNC (SDNR) dev to incorporate 5G PNFsLink to Slide



OOF: Supports Change Management Scheduling

SDN-C: Committed

Will address this via Change ManagementAT&T, China Mobile, Huawei

Status
colourRed
titleINVESTIGATING

SDN-C Interfaces need investigation. Want to make sure SDN-C is supporting Ansible.

5G/performance Analysis and Optimization

High Volume and RT Data Collection of PM

DCAE, DMaaP, SDN-R, 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: No 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



Status
colourGreen
titleON TRACK & CODE SUBMITTED

Code is developed & Submitted.

5G/performance Analysis and Optimization

Bulk PM

 DCAE, DMaaPLink to Slide
DCAE: on DMAAP-DRDCAE:L

code change: DMaaP

Code change: DCAE

DCAE:  DataFileCollector- Committed (based on Ericsson Contribution) with dependency risk

PMMapper - Partial Commit (Based on Ericsson contribution) + dependency risk Not a hard requirement


DCAE: Dependency on DMAAP-DR + PMMapper (Stretch goal)


AT&T, Ericsson



Status
colourGreen
titleON TRACK

DMaaP Data Router

Status
colourRedGreen
titlePENDINGOn Track

File collector available but with a few pending tasks
Update form Vimal on Oct 4: File collector on track.
Status
colourRed
titlePOSTPONED

PM Mapper postponed to Dublin at M3

5G/performance Analysis and Optimization

Optimization Framework Enhancements (Placement, Formulation, Solving)

 OOF

Link to Slide

OOF: Mcode change: OOFOOF: Committed to SON
AT&T, Nokia, Reliance Jio

Status
colourGreen
titleOn Track

All code has been submitted

5G/Network slicingWithdrawn 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.

SO: will be ready to test soon.

Integration: Not started yet.


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



MultiCloud: Ready to test

VFC: not started yet

UUI: not started yet

Edge Automation Through ONAP (EA)A&AI, Multi-Cloud, OOF, SO

Edge Scoping MVP for Casablanca - ONAP Enhancements

  1. Cloud-agnostic Placement/Networking & Homing Policies (Phase 1 - Casablanca MVP, Phase 2 - Stretch Goal)

Orange: 3

ATT: 3

China Telecom: 3

China Mobile: 3

Verizon: 2

Vodafone: 1

OOF: on MultiCloud & SO

Multi-Cloud: on A&AI



SO: XS

AAI: XS

OOF: M

Multi-Cloud: M-L

Code: OOF, Multi-Cloud, A&AI, SO

Test: Integration (vFW use case)

Casablanca MVP:

  • OOF: Committed
  • Multi-Cloud: Committed
  • A&AI: Committed
  • SO: Committed




M4 on target in relevant projects

Integration Test Plan in Progress: HPA & Cloud Agnostic Intent - R3 Test Plan (In Progress)

Edge Automation Through ONAP (EA)Multi-Cloud

Edge Scoping MVP for Casablanca - ONAP Enhancements

2. Edge Scoping MVP for Casablanca - ONAP Enhancements#ONAPEnhancements-AggregatedInfrastructureTelemetryStreams(AlignswithHPArequirements,CombiningeffortswithHPA)

Orange: 3

ATT: 3

China Telecom: 3

China Mobile: 3

Verizon: 2

Vodafone: 1


Multi-Cloud: M-LCode: Multi-Cloud

Casablanca MVP:

  • Multi-Cloud: Committed



M4 on target in relevant projects

Start Small MVP "Node metrics and HPA metrics from Grafana dash board"

No plan for integration testing.


...