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:
    • Hardware Platform Awareness (HPA) Requirements
    • HEAT/TOSCA Information Model updates
  • 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 

...

The VNF Requirements developed by this project are applicable to the VNFs identified in the TSC E2E use cases.  

• a  VNF Provider (developer) using VNF Requirements in designing, testing, and certifying a VNF for use on ONAP
• a Service Provider using VNF Requirements as prototype text for RFPs to acquire VNFs to run in an ONAP context see VNFRQTS-16
• VNF Validation Project uses VNF Test Descriptions developed by this project to implement VNF testing for validation purposes. 

...

• A VNF Guidelines document summarizing VNF provider oriented deliverables and providing informative, forward lookiging guidance. 
• A set of Integrated VNF Requirements for use as prototype RFP text.
• VNF Test Descriptions for use by VNF Validation project, traceable from the VNF Requirments
• VNF Use Case - VNF Provider Guidelines for VNF Scale Out Use Case

...

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

Platform Maturity

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.

...

Other ONAP projects that this VNF Requirements project depends on:

• SDN-C          (for API requirements on VNFs)  
• APPC            (for VNF configuration  requirements) 
• VF-C             (for  VNF life cycle managment and configuration)
• Service Design & Creation               (for VNF onboarding)  
• DCAE            (for VNF reporting requirements)
• Authentication and authorization Framework (for VNF Security Requirements)
• Modeling        (for Tosca Data Modeling for VNF)
• Multi-VIM/ MultiCloud (for network cloud infrastructure requirements) 

...

...

Third Party Products Dependencies

...

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...

...

...