...
Platform Maturity Integration Testing
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments | Result |
---|
Performance | 0 | 1 | Are developing server simulation to receive requests from VF-C to SVNFM Baseline performance criteria are being defined Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VFC-663 |
---|
|
VF-C Maturity Test Report | - 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
| Pass VF-C Maturity Test Report |
Stability | 0 | 1 | 72 hours components level random transactions are being tested in cmcc lab Depend on the previous simulator Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VFC-662 |
---|
|
VF-C Maturity Test Report | - 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
| pass Test 72 hours pass in cmcc lab VF-C Maturity Test Report |
Resiliency | 1 | 2 | VF-C have integrated with OOM and can implement automated failure detection and recovery by leveraging the k8s capabilities Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VFC-661 |
---|
|
| - 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 | CII Passing is 97% ; code coverage is already above 50%; there are still unresolved critial issues Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VFC-660 |
---|
|
| - 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
| pass |
Scalability | 0 |
1(*)0 | Part of stateless components can scale via k8s For stateful VF-C components need more work to support scalability Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VFC-659 |
---|
|
| - 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
| pass |
Manageability | 0 | 1 | VF-C updated log configuration and added filebeat container to VF-C, So VF-C logs will be transferred to ELK stack Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VFC-639 |
---|
| . | - 1 – single logging system across components; instantiation in < 1 hour
- 2 – ability to upgrade a single component; tracing across components; externalized configuration management
| pass VF-C logs can be written into /var/log/onap/vfc component directory and transferred to ELK stack |
Usability | 1 | 1 | documentation is already in onap.readthedocs.io Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VFC-664 |
---|
|
| - 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
| pass |