VF-C R2 Beijing - S3P

Performance

1

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

Baseline performance criteria are being defined

VFC-663: Support platform Maturity Requirements-Performance Level 1Closed

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

1

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

Depend on the previous simulator

VFC-662: Support platform Maturity Requirements-Stability Level 1Closed

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

2

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

VFC-661: Support platform Maturity Requirements-Resiliency Level 2Closed

• 0 – none

• 1 – manual failure and recovery (< 30 minutes)

• 2 – automated detection and recovery (single site)

• 3 – automated detection and recovery (geo redundancy)

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

VFC-660: Support platform Maturity Requirements-Security Level 1Closed

• 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

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.

VFC-659: Support platform Maturity Requirements-Scalability Level 1Closed

• 0 – no ability to scale

• 1 – single site horizontal scaling

• 2 – geographic scaling

• 3 – scaling across multiple ONAP instances

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

VFC-639: Support platform Maturity Requirements-Manageability Level 1Closed.

• 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

documentation is already in onap.readthedocs.io

VFC-664: Support platform Maturity Requirements- Usability Level 1Closed

• 1 – user guide; deployment documentation; API documentation

• 2 – UI consistency; usability testing; tutorial documentation

pass