VF-C R2 Beijing - S3P
- Yan Yang
This page will track our test plans for S3P functionality (if applicable). When successful, we will update the Release Planning wiki on our status: Beijing Release Platform Maturity
Platform Maturity Integration Testing
Area | Targeted Level for current Release | How, Evidences | Comments | Result |
|---|---|---|---|---|
Performance | 1 | Are developing server simulation to receive requests from VF-C to SVNFM Baseline performance criteria are being defined |
| Pass |
Stability | 1 | 72 hours components level random transactions are being tested in cmcc lab Depend on the previous simulator https://lf-onap.atlassian.net/browse/VFC-662 |
| pass Test 72 hours pass in cmcc lab |
Resiliency | 2 | VF-C have integrated with OOM and can implement automated failure detection and recovery by leveraging the k8s capabilities |
| pass have been tested in intel lab, core component can be recovered relying on OOM |
Security | 1 | CII Passing is 97% ; code coverage is already above 50%; there are still unresolved critial issues https://lf-onap.atlassian.net/browse/VFC-660 |
| pass have passed when M4 CII Passing is 97% ; code coverage is above 50%; |
Scalability | 1(*) | Part of stateless components can scale via k8s For stateful VF-C components need more work to support scalability, we plan to support all components scalability in Casablanca release. |
| pass Note: Currenty,only ztevnfmdriver gvnfmdriver can be scaled via OOM, we plan to support all components scalability in Casablanca release. |
Manageability | 1 | VF-C updated log configuration and added filebeat container to VF-C, So VF-C logs will be transferred to ELK stack |
| pass VF-C logs can be written into /var/log/onap/vfc component directory and transferred to ELK stack |
Usability | 1 | documentation is already in onap.readthedocs.io |
| pass |