...
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.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message. |
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 recommendedAT&T, China Mobile, Tech Mahindra, Orange, Deutsche Telekom. |
Scope
What is this release trying to address?
Validate the HEAT scripts of VNFs.
The feature scope of the ONAP platform is still in definition by the TSC/Use case committee.
The impact on HEAT templates for Feature alignment is not yet clear. Describe the problem being solved by this release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case)The scripts can be invoked to validate the HEAT templates for VNFs prior to onboarding.
Minimum Viable Product
Describe the MVP for this releasetest scripts for HEAT templates.
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
...
...
| VVP AND issuetype = Epic AND fixVersion = "Dublin Release" | | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
|
Stories
...
...
...
| VVP AND issuetype = Story AND fixVersion = "Dublin 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.Maintain HEAT validation scripts in alignment with eth ONAP Platform
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this 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.
...
| Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = sanbox and issuetype in (bugVVP AND issuetype = Bug AND status in (Open, "In Progress", REOPENED) |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
|
)
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).
| Risk identified | Mitigation Plan | Contingency Plan |
|---|
| To fill out | To fill out | To fill out |
Fill out the Resources Committed to the Release centralized page.
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates. The ONAP Dublin release schedule is maintained here.
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.
...
