| Area | Actual level | Targeted level for current release | How, Evidences | Comments |
|---|
| Performance | 0 | 0 (given CLAMP is design time there is no point to adhere to L2 requirement) | Run performance basic test, depends on performance criteria availability for level 1 - not able to commit to more than what was done on Beijing | - 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
|
| Stability | 1 | 1 | Participate to Stability runs Level 1 | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | CLAMP-100 |
|---|
|
| - 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 | 1 | 1 | | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | CLAMP-83 |
|---|
|
| - 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 | - Reach CII passing badge, increasing test coverage as remaining item
- AAF CADI integration
- Infrastructure setup for js test coverage
| - 0 – none
- 1 – CII Passing badge + 50% Test Coverage, including no critical and high known vulnerabilities>60 days old
- 2 – CII Silver badge; internal/external communication encrypted; role-based access control and authorization for all calls based on CADI
- 3 – CII Gold
|
| Scalability | 1 | 1 | Level 1 single site horizontal scaling | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | CLAMP-102 |
|---|
|
| - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
|
| Manageability | 1 2 | (1 if not enough resource1 (2, if CLAMP can get more resource from the community) |
| - 1 – single logging system across components; instantiation in < 1 hour
2 – ability to upgrade a single component; tracing across components; externalized configuration management
; All application logging to adhere to
ONAP Application Logging Specification v1.2 3 - Transaction tracing across components
|
| Usability | 1 | 21 (1 if not enough resource)2, if CLAMP can get more resource from the community) | CLAMP is not anticipating new API at this point, so we are technically compliant with API CVS at this point | |