You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 165 Next »

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 CaseOwner

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


All: Test OnlyN/A - part of regression testsN/A - part of regression tests

vDNSAT&THPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests

VoLTE

China Mobile

HPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests

vCPEKang XiHPA


All: Test OnlyN/A - part of regression testsN/A - part of regression tests

CCVPN

LIN MENG

jianguo zeng

DCAE, SO,...?

NOTE: No project should be code impacted by this use case.

Materials Lin Meng. Material Jianguo Zeng

All; Test Only

(DCAE?)



China Mobile, Vodafone

Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement

DCAE :  Based on proposal see no impact, however was noted by Xin Miao from Huawei that new collector will be required for this usecase; need to be confirmed by US owner.

OSAM/PNF

Sumithra Bhojan

Bora Eliacik

Ryan Hallahan

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

(star) 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 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 EngagementNotes
HPA
Alexander Vul

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 (C)
SDC (TO)
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: TBD

Multi-Cloud: committed



Intel
ARM
AT&T
Huawei


Change Management
Ajay Mahimkar

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: Committed

VID: requires additional design information

APPC: Not enough details on requirements, plus limited resources

OOF: Risk on resources -  being worked out

SO : Committed (with support from ATT resources)

AT&T
Scaling
Scott Blandford

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

Benjamin Cheung

Vimal Begwani

Shekar Sundaramurthy


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 PNF placement

SO: Committed (with resurces from Nokia)


AT&T, Nokia,

5G/PNF

Software Version Reporting

 Vimal Begwani

Shekar Sundaramurthy 

 CCSDK, SDN-CLink to Slide



CCSDK: committed

SDN-C: committed


AT&T

5G/PNF

Lifecycle Management Support

 Vimal Begwani

Shekar Sundaramurthy

 CLAMP, SDN-CLink to Slide





AT&T

5G/performance Analysis and Optimization

High Volume and RT Data Collection of PM

Benjamin Cheung

Vimal Begwani

Shekar Sundaramurthy


DCAE, SDN-R, CCSDK, SDNCLink 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

Vimal Begwani

Shekar Sundaramurthy



 DCAE, DMaaPLink to Slide


code change: DMaaP

Code change: DCAE



AT&T, Nokia, Ericsson

5G/performance Analysis and Optimization

Optimization Framework Enhancements (Placement, Formulation, Solving)

 Sarat Puthenpura

Vimal Begwani

Shekar Sundaramurthy

Benjamin Cheung 

 OOF

Link to Slide

OOF: Mcode change: OOFOOF: Committed to SON
AT&T, Nokia, Reliance Jio
5G/Network slicing

Vimal Begwani

Shekar Sundaramurthy

Benjamin Cheung

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

Bin Yang

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.)

ramki krishnan

Raghu Ranganathan

Vimal Begwani

Policy, Multi-Cloud, A&AI, ESR, OOF, SO, DCAE, OOM (minor)

Edge Scoping MVP for Casablanca - ONAP Enhancements

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:

  • OOF: Committed
  • Multi-Cloud: Committed
  • SO: Committed
  • AAI: In progress

Stretch Goal:

  • DCAE : Not committed

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.



(star) 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 RequirementsOwnerSub-categoryProject Impacted for CasablancaLink(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 projectsIf Partially or not Committed, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc)Company EngagementNotes
S3P
Jason Hunt
  • Performance
  • Stability
  • Resiliency
  • Security (see below)
  • Scalability
  • Manageability
  • Usability

Likely ALL depending upon TSC determination of new level requirements per category


Materials

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: XLPortal: Code

Portal: Not Committed

APPC: Partial

DCAE:Partial

Portal: See Risk #2

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

Stephen Terrill




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 ?):

  • JAVA projects to use CADI client and enforcement point
  • Non-JAVA projects:Waituntilthereismulti-language.
  • All projects either need to have certificates (for secure communication) (based on a common trust store of AAF).  The certificate distribution can be part of deployment mechanism and will be further detailed.

Secure communication toxNFs(Security for 5G Use cases). DCAE, APPC, VFC? VNF requirements. (Secure Communication to Network Functions)
- TLS and/or SSH for netconf (APP-C, SDN-C, CCSDK)
- HTTPS security for VES (DCAE) (with certificates, slowly deprecating username/pasword)

  • Description of how the xNFs will get their certificates (VNFreqs). 

Vnf package security following SOL 004: SDC, VNFreqs, VNF SDC


Materials

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

Risk #1

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



Portal: See Risk #3

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)
Helen Chen




All: XL

APPC: Not Committed

CLAMP: Not Committed

DCAE: Not Committed

APPC, CLAMP, Portal, SDC, DCAE: Lack of resources require additional information (does it include rollback, retrofit, no impact on run-time, etc)?




Architecture Alignment

Chris Donley
  • API improvement
  • Realtimestreaming
  • K8S Support (for VNFs)



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

Helen Chen

Brian Freeman


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 OOMPortal: SPortal: 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 supportTao Shen
  • User Experience

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 PortalPortal: LPortal: Code

Portal: Partial

APPC: Not Committed

CLAMP: Not Committed

Portal: Limited resourcesPortal: AT&T, ChinaMobilePortal: 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.
TestingHelen Chen
  • Enable JavaScript Unit tests
  • CSIT tests

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, APPC, CLAMP, DCAE: See Risk #1


Portal: AT&T, IBM, TechMPortal: UI projects may depend on Portal team for pairwise testing

(star) 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.



  • No labels