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

Compare with Current View Page History

Version 1 Next »

This documents the strawman proposal (presented at ONAP Session September 27, 2017) for how to handle requirements that would be of interest to the ONAP operators as they implement ONAP into production.

Inputs

Notes from the Tuesday September 26th discussion at ONAP meeting

R2 Proposed Non-Functional Requirements

Draft Architecture Principles

General Approach

  • For each category of carrier-grade requirements, multiple levels of requirements will be established
  • The TSC & Architecture Committee, in cooperation with the project teams, will establish guidelines for requirement levels that must be met by each project.  The required level may be influenced by: MVP project status, desired project maturity level, release inclusion

Performance

  • Level 0: no performance testing done
  • Level 1: baseline performance measured
  • Level 2: performance improvement plan created & implemented in 1 release
  • Level 3: performance improvement plan implemented over 2 releases

Stability

  • Level 0: none beyond release requirements
  • Level 1: x% code coverage; 72 hour soak test
  • Level 2: y% code coverage; 30-day soak test
  • Level 3: track record over 6 months of reduced defect rate

Availability

  • Level 0: no redundancy
  • Level 1: manual failure detection & recovery time of 30 minutes tested
  • Level 2: warm or cold standby with automated failure detection of 5 minutes & recovery time of 15 minutes
  • Level 3:
    • support n-way active-active configurations with failover detection & rerouting < 100ms
    • Additionally for stateful components: support data replication technique with maximum loss of 100ms of data
    • Measure of failed requests should be <15 out of 1 million requests

  • These levels may drive need for common tooling & approaches to consistently implement this

Security

  • Level 0: None
  • Level 1: CII Passing badge
  • 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 role-based access control and authorization.
  • Level 3: CII Gold badge 

Scalability

  • Level 0: no ability to scale
  • Level 1: supports single site horizontal scale out and scale in
  • Level 2: supports geographic scaling


Manageability

  • Level 1: All ONAP components will use a single logging system.


Usability/Operations (applies to entire ONAP Project)

  • Instantiation of a simple ONAP system should be accomplished in <1 hour



  • No labels