...
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level, the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Since Integration project does not deliver code, the following will refer to the overall ONAP platform maturity level as measured by the Integration team S3P testing activities during the prior release.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance |
N/A| Not Measured |
|
| - 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
|
| Stability |
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 | - 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| Not Measured |
|
| - 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| Not Measured |
|
| - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
|
| Manageability |
N/ANot Measured
|
|
| - 1 – single logging system across components; instantiation in < 1 hour
- 2 – ability to upgrade a single component; tracing across components; externalized configuration management
|
| Usability |
N/ANot Measured
|
|
| - 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
|
API Incoming Dependencies
...
