...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance | *N/A | *N/A |
| - 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
|
| Stability | *N/A | *N/A |
| - 0 – none
- 1 – 72 hours component level soak w/random transactions
- 2 – 72 hours platform level soak w/random transactions
- 3 – 6 months track record of reduced defect rate
|
| Resiliency | *N/A | *N/A |
| - 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
|
| Security | *N/A | *N/A |
| - 0 – none
- 1 – CII Passing badge + 50% Test Coverage
- 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
- 3 – CII Gold
|
| Scalability | *N/A | *N/A |
| - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
|
| Manageability | *N/A | *N/A |
| - 1 – single logging system across components; instantiation in < 1 hour
- 2 – ability to upgrade a single component; tracing across components; externalized configuration management
|
| Usability | 1 | 1 | docs updated as required | - 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
|
*N/A - as mentioned above, OOM will support other projects to achieve their S3P requirements
API Incoming Dependencies
...
As OOM is fully functional as is there are no significant risks to project.
Fill out the Resources Committed to the Release centralized page.
...
