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 deliverFrankfurt |
| 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 Nokia Ericsson Orange China Mobile |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
Minimum Viable Product
Provide guidance for developers of VNFs so they can be compatible with ONAP
Requirements
update requirements in alignment with ONAP platform features
Update VNF test case descriptions to enable conformance test development
Minimum Viable Product
updates VNF requirements and updated VNF test Case DescriptionsDescribe 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.
...
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 status = Open AND fixVersion = "Frankfurt Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = sanbox and issuetype in (story) VNFRQTS AND issuetype = Story AND status = Open AND fixVersion = "Frankfurt Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.Keep teh VNF REquirments in Alignment with ONAP platform capabilities and support extending the VNF certification test regime.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
| Deliverable Name | Deliverable Description | ||
|---|---|---|---|
| documentation | https://docs.onap.org/en/latest/guides/onap-provider/index.html | To fill out | To fill out |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the API this project is expecting from other projects. - NONE
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.
...
API this project is delivering to other projects. NONE
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
...
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Depends on teh documentation project toolchain - ie Sphinx, pythion, ReadTheDocs.
Testing and Integration Plans
...
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.
refer to VNFRQTS How to Contribute
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.
...
Please update any risk on the centralized wiki page - Frankfurt Risks
Resources
Fill out the Resources Committed to the Release centralized page.
Release 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 recommended to provide these agreements and dates in this section.
...
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
Refer Frankfurt release timeline
Documentation, Training
Please update the following centralized wiki: Frankfurt Documentation
...