Page History

• Level 0: no performance testing done
• Level 1:
• 0 -- none
1 –
• baseline performance criteria identified and
measured2 & 3 – performance improvement plans created & implemented
• measured  (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
• Level 2: performance improvement plan created 
• Level 3: performance improvement plan implemented for 1 release (improvement measured for equivalent functionality & equivalent hardware)

1+ (Dublin recommendation 2 - may not reach 80% code coverage due to number of repository in DCAE; will be phased and target some component )

• Level 0
–
• : none beyond release requirements
• Level 1
–
• : 72
hours
• hour component-level soak
w/
• test (random test transactions with 80% code coverage; steady load)
• 2 – 72 hours platform level soak w/random transactions
3 – 6 months track record
• Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load)
• Level 3: track record over 6 months of reduced defect rate

• • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)

1

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear and cannot be committed to.

+ (Dublin recommendation 2 - cannot be committed for following reason)

• Resource constraint
• CADI library not available for Python 

• Process of AAF certificate distribution in K8S

• between ONAP components

• and

• external (xNF) to be defined
  
  DCAE team will integrate with Buscontroller integration for dynamic topic provisioning and AAF based role setting

• as STRETCH GOAL

• Level 0: None
• Level 1: CII Passing badge
  • Including no critical and high known vulnerabilities > 60 days old
• Level 2: CII Silver badge, plus:
  • All internal/external system communications shall be able to be encrypted.
  • All internal/external service calls shall have common
• 0 – none
• 1 – CII Passing badge + 50% Test Coverage
2 – CII Silver badge; internal communication encrypted;
• • role-based access control and authorization
for all calls3 –
• • using CADI framework.
• Level 3: CII Gold badge 

1

Mutli-site support   **Dependency on OOM Team (Stretch Goal, not currently committed for Casablanca)

0 –
• Level 0: no ability to scale
• Level 1
–
• : supports single site horizontal
scaling
• 2 – geographic scaling
3 – scaling
• scale out and scale in, independent of other components
• Level 2: supports geographic scaling, independent of other components
• Level 3: support scaling (interoperability) across multiple ONAP instances

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear (independent upgrade) and cannot be committed to.

• • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management

1

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear (related to tutorial documentation) and cannot be committed to.

(STRETCH GOAL- based on resource availability)

• Level 1:
• All ONAP components will use a single logging system.
• Instantiation of a simple ONAP system should be accomplished in <1 hour with a minimal footprint
• Level 2:
  • A component can be independently upgraded without impacting operation interacting components
  • Component configuration to be externalized in a common fashion across ONAP projects
  • All application logging to adhere to ONAP Application Logging Specification v1.2
  • Implement guidelines for a minimal container footprint
• Level 3
  • Transaction tracing across components

2 (STRETCH GOAL- based on resource availability)

• • Level 1:
    • User guide created
    • Deployment documentation
    • API documentation
    • Adherence to coding guidelines
  • Level 2:
    • API Documentation
      • All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines
      • All existing APIs must be documented in Swagger 2.0
  • Level 3
    • Consistent UI across ONAP projects
    • Usability testing conducted
    • API Documentation
      • All new API’s, all external APIs, and all existing API’s that are modified must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines
  • Level 4
    • API Documentation
      • All API’s for a given project must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation