Versions Compared

Old Version 26

changes.mady.by.user Steven wright

Saved on

compared with

New Version 27

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 

...

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

Gaps identifiedImpact
VNF Requirments Requirements linkage to testing

VNF Requirements are current provided for RFP purposes, but the linkage to testing and validation of those requirments is not yet in place

This release provides initial generic test plan descriptions for testing of VNFs based on the VNF Package. It does not provide test descriptions for design time or run time functional testing of VNFs.

The testing linkage is also costrained by the scope of the VNF Information model in the VNF Package and the relationships identified between that information model and the VNF requirements.

Hardware / infrastructure requirementsThe Amsterdam release requirments had a placeholder (Chapter 6) for VNF requirements associated with the hardwrae executuion environment. Additional requirments are expected in this area from the Multi-VIM project, and perhaps the PNF related features.
HEAT/TOSCA requirementsThe Amsterdam release requirments has text on HEAT and TOSCA requirmenst but not numbered requirments text. This is expected to be improved as part of the Beijing release work.

Known Defects and Issues

Provide a link toward the list of all known project bugs.

...