| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance | 0 | 0 | 0 -- none1 – baseline performance criteria identified and measured2 & 3 – performance improvement plans created & implemented |
|
|
| Stability | 1 - project team 2 - Integration team
| Integration team did a 72 hour test in Beijing 1 - project team 2 - Integration team Assume Integration team will address Level 2 - 72 hour test in Casablanca0 – none1 – 72 hours component level soak w/random transactions2 – 72 hours platform level soak w/random transactions3 – 6 months track record of reduced defect rateDublin |
| *current (1/9/19) code coverage is 66% |
| Resiliency | 2 | 2 In Casablanca we will address Resiliency at the DB level since that was a constrain in Beijing. this will be possible with the move to Maria DB w/Galera | - 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? Partial
Level 1 definitions in Casablanca where changed. Unclear if we can meet Level 1 at this time based on Open Questions: How do we handle false positives and third party issues reported in NexusIQ;
- We will tackle Criticals first and then address mediums as time permit
How do we deal with contiguously? (maybe 3, it really depends on the labs capacity)
|
|
|
| Security | 1 | Minimum Expectation |
| Absolute Minimum expectation:- CII badging passing level
- Continuously retaining no critical or high known vulnerabilities > 60 days
when we are on a 6 month release cycle
Addressing ALL communication has dependency on other projects, such as DMaaP, and dependency alignment does not fit schedule. - 0 – none
- 1 – CII Passing badge + 50% Test Coverage
- 2 – CII Silver badge; internal communication encrypted; old
- All communication shall be able to be encrypted and have common role-based access control and authorization for all calls3 – CII Gold.
|
| Scalability | 1 | 1 | - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
| maybe 2 |
| depends on how to setup the lab for geo-redundancy |
| Manageability | 1 | 1 TBD
Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear 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
|
| Usability | 1 | 1 TBD
Recommendation for Casablanca is Level 2; however, we cannot meeting Level 2
All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines; - There was an issue with ODL & API version - need to investigate further
Swagger 2.0 - We dependent on what ODL Oxygen for API documentation and they dictate version of Swagger used, currently looked like v1.2
E2E tutorial ???
|
| - 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
|