| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|
| Performance | 0 | 1 or 2  - Stretch goal | | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | APPC-1310 |
|---|
|
|
|
| Stability | 1 - project team 2 - Integration team
| 1 - project team but we may not reach 80% code coverage 2 - Integration team Assume Integration team will address Level 2 - 72 hour test in Dublin |
| *current (1/1113/19) code coverage is 67.5%9% - Level 0: none beyond release requirements
- Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
|
| Resiliency | 2 | 2
|
|
|
| Security | 1 | Minimum Expectation |
| Absolute Minimum expectation:- CII badging passing level
- Continuously retaining no critical or high known vulnerabilities > 60 days old
- All communication shall be able to be encrypted and have common role-based access control and authorization.
|
| Scalability | 1 | 1 |
|
|
| Manageability | 1 | 1, 2(partial)
|
| - 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.2Implement guidelines for a minimal container footprint
|
| Usability | 1 | 1
|
| 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
TBD - Swagger 2.0 - We dependent on what ODL Fluroine for API documentation and they dictate version of Swagger used, currently looked like |