| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance | 1 | 1 |
| - Level 0: no performance testing done
- Level 1: baseline performance criteria identified and 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)
|
| Stability | 2 | 2
|
| - Level 0: none beyond release requirements
- Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
- 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
|
| Resiliency | 2 | 2 |
| - 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
|
| Security | 1 | 1+ (Most DCAE components are complaint; will address remaining in Frankfurt based on resource availability) |
| - 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 role-based access control and authorization using CADI framework.
- Level 3: CII Gold badge
|
| Scalability | 1 | 1
|
| - Level 0: no ability to scale
- Level 1: supports single site horizontal 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
|
| Manageability | 1 | 1+ (except Logging where some DCAE components are not complaintExcept logging, all other requirements are met) |
| - 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
|
| Usability | 1 | 1+
|
| - Level 1:
- User guide created
- Deployment documentation
- API documentation
- Adherence to coding guidelines
- Level 2:
- Level 3
- Consistent UI across ONAP projects
- Usability testing conducted
- API Documentation
- Level 4
|
