...
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.
| Area | Actual level | Targeted level for current release | How, Evidences | Comments |
|---|
| Performance | 0 | 0 | Run performance basic test, depends on performance criteria availability for level 1 - not able to commit to more than what was done on Amsterdam | - 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
|
| Stability | 0 | 1 (assumption is that 72 hour soak test will be done by Integration team testing); not separate testing will be done at component level | 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 | 0 | 1 | Reach CII passing badge, increasing test coverage as remaining item | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CLAMP-101 |
|---|
|
| - 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 | 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 |
Using | Already using EELF common framework for logging | - 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 | Documentation only for this release - Stretch to have automated API docs (Swagger) | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CLAMP-32 |
|---|
|
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | CLAMP-31 |
|---|
|
| - 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
|
API Incoming Dependencies - To Be Reviewed for Beijing
...
