DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.

Overview

Scope

What is this release trying to address?

• 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 

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

The TSC identified the following Use cases for Release A:

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. 

Minimum Viable Product

• 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

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Epics

Stories

Longer term roadmap

Amsterdam- deliver overview VNF Guidelines  & prototype RFP text requirements.

Beijing - Update Amsterdam deliverable for new ONAP features, Test Descriptions for VNF Package Testing, VNF Scaling Use case, tooling improvements

Casablanca - Extend tracability of VNF testing ( VNF Requirments Database),additional VNF provider use cases, Update Bejing deliverable for new ONAP features

Dublin - Design time VNF testing description, additional VNF provider use cases, Update Casablancadeliverable for new ONAP features

El Alto - Run time VNF testing description, update Dublin deliverable for new ONAP features

Frankfurt - Update El Alto deliverable for new ONAP features

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Sub-Components

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

Architecture

High level architecture diagram

The VNF Requirements Project is not delivering ONAP platform code, rather it delivers documentation targeted to VNF providers to enable thme to develop VNFS  which can be more easily onboarded and operated by an Operator using an ONAP platform.

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.

API Incoming Dependencies

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) 

The VNF Requirments does not produce code interfaciong with platform APIs. The VNF Requirments do consoliate requirements from ONAP platform compontents that impact the design and development of VNFs.  These ONAP platform components in the table below generate APIs that impact VNFs and so these are generally reflected in the VNF Requirements. 

API Outgoing Dependencies

The VNF Requirements do not provide code with APIs, but the VNF Requirements are used as inputs  by a number of other ONAP projects.

Third Party Products Dependencies

The VNF Requirements is documentation rather than code so there is no dependency on 3rd party products other than the documentation and development tool chains provided through the Linux Foundation. 

Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

Gaps

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.

Known Defects and Issues

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

Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

Documentation, Training

• VNF Guidelines  
  • component lead - Wenyao Guan (China Mobile) 
  • Forward looking guidance
• VNF Requirements
  • component lead - Herb Patten (AT&T)
  • VNF Conformance requirements
• VNF  Use Cases
  • component lead - Scott Blandford
  • tutorial
• VNF Test Case Descriptions
  • component lead - Steven Wright
  • Description of how to test the VNF Requirements

Other Information

Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS. This vnfrqts project is a documentation project using the LF toolchain coordinated via the documentation project. 

Charter Compliance

The project team comply with the ONAP Charter.