Versions Compared

Old Version 96

changes.mady.by.user Shankaranarayanan Puzhavakath Narayanan

Saved on

compared with

New Version 97

changes.mady.by.user Stephen Terrill

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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











Security

Stephen Terrill




Note: This does not cover what is in S3P.  However based on 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: Wait until there is multi-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 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? HTTPS security for VES (DCAE) (with certificates, slowly deprecating username/pasword)

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

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


Materials

CADI/AAF Integration:


Test coverage (js):

(1) js Sonar plug-ins activation

(2) min. 3 additional containers per application

=> Jenkins enhancements

(3) Maven build to be updated

Test coverage (js):

All: M/L






Upgrade (from Beijing to Casablanca)
Helen Chen




All: XL




Architecture Alignment

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

View file
nameONAP Casablanca Architecture Readout v2.pptx
height250









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.









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)









...