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

Compare with Current View Page History

« Previous Version 52 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 Case

Use CaseOwner

Projects or functional requirements Impacted

for Casablanca

Notes
vFWAT&THPA
vDNSAT&THPA
VoLTE

China Mobile

HPA
vCPEKang XiHPA
CCVPN

DCAE, SO,...

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

Materials Lin Meng. Material Jianguo Zeng

OSAM

SO, Portal, External API, APPC, DCAE

HPA

**NOTE: Based on Arch review, no projects should be code impacted

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


Functional Requirements

Functional RequirementsOwner

Projects Impacted

for Casablanca

Links

Priority

(from SP perspective)

HPAVNFSDK (minor), SDC (minor), Policy, OOF (minor), SO (minor)

Orange: 2

ATT: 2

China Telecom: 2

China Mobile: 1

Verizon: 2

Vodafone: 2

Change ManagementSDC, SO, VID, SDNC, APPC, VNFSDK

Orange: 1

ATT: 1

China Telecom: 2

China Mobile: 2

Verizon: 1

Vodafone: 2

Scaling

Orange: 1

ATT: 1

China Telecom: 1

China Mobile: 1

Verizon: 3

Vodafone: 1

5G/PNFSDC, SO, DCAE, SDN-C, App-C, A&AI, CDT, Modeling

Orange: 2

ATT: 1

China Telecom: 3

China Mobile: 1

Verizon: 1

Vodafone: 2

5G/performance Analysis and OptimizationDCAE

Orange: 2

ATT: 2

China Telecom: 1

China Mobile: 3

Verizon: 3

Vodafone: 3

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

SO,VID,SDNC,OOF,VFC,

UUI,MultiCloud, DCAE,

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

EA/Cloud Infrastructure for Distributed Edge Clouds (5G etc.)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

Abbreviations: 

  • Edge Automation through ONAP - EA

Non Functional Requirements

Non Functional RequirementsOwnerSub-categoryProject Impacted for Casablanca
S3P
  • Performance
  • Stability
  • Resiliency
  • Security (see below)
  • Scalability
  • Manageability
  • Usability

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

Materials.

Security

Note: This does not cover what is in S3P.  However based on that it is expected to use CADI to get certificates to enable secure communication

Pluggable authentication and Authorization (Use of CADI and ?): All projects

Secure communication to xNFs (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)
- VES security? 

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

Materials

Upgrade (from Beijing to Casablanca)

Architecture Alignment

  • API improvement
  • Real time streaming
  • K8S Support (for VNFs)
Materials.
HEAT support ?

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.

Internationalization language supportTao Shen
  • User Experience

Design language/internationalization component in Portal and provide service apis to partnering apps like Policy, VID, SDC, AAI

Note: This will need to go through the whole process (Architecture review,...) to understand what the sdk will be providing and dependencies on other ONAP project (Portal, SDC,...)

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)

Database as a service
  • Database

Music team planning to provide DB as a service. All applications having local DB can switch to this.

Note: no owner.

Service audit - POMBA
  • Audit

POMBA - off Logging project

Note: this is either a project or a sub-project but not a non-functional requirements.



  • No labels