You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01

Are developing server simulation to receive requests from VF-C to SVNFM

Baseline performance criteria are being defined

VFC-663 - Getting issue details... STATUS

VF-C Maturity Test Report

  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01

72 hours components level random transactions are being tested in cmcc lab

Depend on the previous simulator

VFC-662 - Getting issue details... STATUS

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
Resiliency12

VF-C have integrated with OOM and can implement automated failure detection and recovery by leveraging the k8s capabilities

VFC-661 - Getting issue details... STATUS

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01

 CII Passing is 97% ;

code coverage is already above 50%;

there are still unresolved critial issues

VFC-660 - Getting issue details... STATUS


  • 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
Scalability01(*)

Part of stateless components can scale via k8s

For stateful VF-C components need more work to support scalability

VFC-659 - Getting issue details... STATUS

  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability01

VF-C updated log configuration and added filebeat container to VF-C, So VF-C logs will be transferred to ELK stack

VFC-639 - Getting issue details... STATUS .

  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11

documentation is already in onap.readthedocs.io

VFC-664 - Getting issue details... STATUS

  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation
  • No labels