VNFRQTS Istanbul Release Planning
- Trevor Lovett
The content of this template is expected to be fill out for M1 Release Planning Milestone.
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Istanbul |
Project Lifecycle State | Incubation |
Participating Company | AT&T, Nokia, Ericsson |
Scope
What is this release trying to address?
Provide guidance for developers of VNFs so they can be compatible with ONAP
Requirements
n/a
Minimum Viable Product
Update VNF Requirements to reflect any new, updated, or removed functionality in the Istanbul release
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
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description |
|---|---|
documentation | VNF Requirements for Network Function providers |
Sub-Components
vnfrqts/epics
vnfrqts/requirements
vnfrqts/guidelines
vnfrqts/testcases
vnfrqts/usecases
Architecture
High level architecture diagram
N/A - Documentation only project
Platform Maturity
API Incoming Dependencies
N/A - Documentation only project
API Outgoing Dependencies
N/A - Documentation only project
Third Party Products Dependencies
See requirements.txt
TESTING AND INTEGRATION PLANS
N/A - Documentation only project
refer to VNFRQTS How to Contribute
GAPS
None known at this time
KNOWN DEFECTS AND ISSUES
None
RISKS
Please update any risk on the centralized wiki page - Istanbul Risks
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.
DOCUMENTATION, TRAINING
Please update the following centralized wiki: Istanbul Documentation
refer to VNFRQTS How to Contribute
Note
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.
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.
Charter Compliance
The project team comply with the ONAP Charter.