...
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 |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
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 |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
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 |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | CLAMP-102 |
---|
|
| - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
|
Manageability | 1 | 1 (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 | 1 (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 | - 1 – user guide; deployment documentation; API documentation
- 2 – API documentation; usability testing; tutorial documentation;
All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines; All existing APIs must be documented in Swagger 2.0 - 3 - UI consistency; usability testing; API Documentation
(changed and external APIs follow policy) 4 - API Documentation (all follow policy)
|
...
Risk identified | Mitigation Plan | Contingency Plan |
---|
new policy api(and contents) for guard policies creation not defined yet |
|
|
"vf_module_id" usage for scale out use case not yet completely confirmed | implement textbox to manually enter target parameter(for policy api call) | use the textbox to enter the value of whatever vf_module id's we need to make the CL works |
Resources
Link toward the Resources Committed to the Release centralized page.
Release Milestone
...