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

Compare with Current View Page History

« Previous Version 9 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.

Use Case

Use CaseOwner

Projects Impacted

for Casablanca

vFW

vDNS

VoLTE



vCPEKang Xi
CCVPNChina Mobile


Functional Requirements

Functional RequirementsOwner

Projects Impacted

for Casablanca

HPA
Change Management
Scaling
5G/PNF




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
Security

Truning ON AAF in Portal and start using role management for partners - Policy, SDC, VID, AAI requires SDK upgrade

AAF certificate management integration (both for FE HTTPs and BE rest API calls) on All applications

Upgrade (from Beijing to Casablanca)

Architecture Alignment

  • API improvement
  • Real time streaming
  • K8S Support (for VNFs)

HEAT support ?


Internationalization language support
  • User Experience
Design language/internationalization component in Portal and provide service apis to partnering apps like Policy, VID, SDC, AAI
Testing
  • Enable JavaScript Unit tests
  • CSIT tests
Most UI projects with javascript
Database as a service
  • Database
Music team planning to provide DB as a service. All applications having local DB can switch to this.



  • No labels