Versions Compared

Old Version 19

changes.mady.by.user Steven wright

Saved on

compared with

New Version 20

changes.mady.by.user Steven wright

Saved on

Key

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

DRAFT PROPOSAL FOR COMMENTS

...

  • This project will deliver a unified set of VNF Guidelines and VNF Requirements.
    • The VNF Guidelines and VNF Requirements must be  versioned to enable evolution based on operational experience
    • The VNF Guidelines and VNF Requirements will support the ONAP Architecture Principles.
    • Update the  VNF Requirements as prototype RFP text for the ONAP/Beijing release including:
    • Update the  VNF Guidelines as  for the ONAP/Beijing release
  • Identify a list of features and functionality will be developed.
    • The VNF Guidelines and Requirements will support the Release 1 Use Cases.
      • Use cases focused on VNF Requirements may be developed in this project, and they will need to be aligned with the ETE Platform use cases.  
      • Document the VNF Provider Guidelines for VNF Scaleout Use Case for the ONAP/Beijing release
    • VNF Guidelines and Requirements  are to be refined beyond prototype text  (e.g. through EPIC statements, use cases)  to deliver test cases and test procedures for us in VNF onboarding & validation. VNF Requirement level use cases to be aligned with ETE platform use cases
      • Document the VNF Test Case Descriptions  for VNF Package testing for the ONAP/Beijing release
  • Identify what is in or out of scope. During the development phase, it helps reduce discussion.
    • VNF Guidelines may be forward looking, or include best practices in VNF design and VNF lifecycle processes.
    • VNF Requirements from ONAP APIs should be linked to the ONAP Release
    • VNF  Requirements may include: 
      • expected  operational characteristics ( e.g. security, resilience, upgradeability) 
      • conditional  requirements (e.g. When configured for deployment on High Availability Network Cloud Infrastructure, the VNF Shall …)
  • Tool chain improvements
    • Develop requirements structure/ metadata to support better linkage / tracking with other ONAP projects
    • Develop templates for VNFs to demonstrate VNF Requirements conformance 

...

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 Requirements

VNF Use Cases (new)

VNF RequirmentsTest Case Descriptions (new)

http://docs.onap.org/en/latest/guides/onap-user/vnfprovider.html

1

additional types of documentation to move towards level 2 with:

Use cases (tutorial/ usability)

Test Case Descriptions (testing)

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

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill outONAP supporting multiple onboarding formatswork with VNF SDK, VVP and SDC to minimize the risk.Document the desired direction in the forward looking VNF Guidelines

Resources

Fill out the Resources Committed to the Release centralized page.

...