...
The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverDublin |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended. | AT&T Ericsson, Nokia, China Mobile, Amdocs |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Use Cases
The Dublin release of VNFRQTS project will address the following items:
- bug fixes, maintenance and feature alignment of VNF Guidelines, VNF Requirements and VNF Test Descriptions consistent with the rest of the ONAP Dublin release.
- The VNF Provider Use cases for Autoscaling to be documented with associated VNF Requirements
- The VNF Test Descriptions appendix to be updated to reflect test implementations planned for Dublin by other projects ( VVP, VNFSDK, etc.)
- Toolchain improvements for the management of VNF Requirements
- Categorization of VNF Requirements to support ONAP VNF Badging & certification initiatives
Use Cases
The set of E-E use cases for ONAP Dublin release is discussed by the ONAP TSC Use case committee hereDescribe the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
The ONAp VNFRQTS Project will deliver the following documentation as its minimum viable product:
VNF Guidelines.
VNF Requirements.
VNF Test Descriptions.
VNF Provider Use CasesDescribe the MVP for this 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
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = sanbox and issuetype in (epic) VNFRQTS AND issuetype = Epic AND fixVersion = "Dublin Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
Jira server ONAP JIRA columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = sanbox and issuetype in (story) VNFRQTS AND issuetype = Story AND fixVersion = "Dublin Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | NA | VNFRQTS is documentation |
| |
| Stability | NA | VNFRQTS is documentation |
| |
| Resiliency | NA | VNFRQTS is documentation |
| |
| Security | NA | VNFRQTS is documentation |
| |
| Scalability | NA | VNFRQTS is documentation |
| |
| Manageability | NA | VNFRQTS is documentation |
| |
| Usability | 1 | 1 | https://docs.onap.org/en/casablanca/guides/onap-provider/index.html |
|
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
N/A to documentation
API API Outgoing Dependencies
API this project is delivering to other projects.
...
- N/A to documentation
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
...
N/A to documentation
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
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.
N/A to documentation
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.
...
Provide a link toward the list of all known project bugs.
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...
| title | Note |
|---|
...
- .
Other Information
Vendor Neutral
...