Versions Compared

Old Version 14

changes.mady.by.user Steven Wright

Saved on

compared with

New Version 15

changes.mady.by.user Steven Wright

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project NameVNFRQTS
Target Release NameBeijing
Project Lifecycle StateEither Incubation , Core, Mature . Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, China Mobile, Orange, Bell Canada, Amdocs, VMWare, Huawei, ZTE, Intel

...

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

PerformanceNAVNFRQTS is primarily a documentation project and does not deliver ONAP platform code
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
StabilityNAVNFRQTS is primarily a documentation project and does not deliver ONAP platform code
  • 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
ResiliencyNAVNFRQTS is primarily a documentation project and does not deliver ONAP platform code
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
SecurityNAVNFRQTS is primarily a documentation project and does not deliver ONAP platform code
  • 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
ScalabilityNAVNFRQTS is primarily a documentation project and does not deliver ONAP platform code
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
ManageabilityNAVNFRQTS is primarily a documentation project and does not deliver ONAP platform code
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability1

VNF Guidelines

VNF Requirments

http://docs.onap.org/en/latest/guides/onap-user/vnfprovider.html
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation


API Incoming Dependencies

...