Page Comparison

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

Pass

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

• 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

• 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%;

• 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.

• 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

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