...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Dublin |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, China Mobile, Tech Mahindra, Orange, Deutsche Telekom. |
...
Validate the HEAT scripts of VNFs.
The feature scope of the ONAP platform is still in definition by the TSC/Use
...
Describe the use case this release is targeted for (better if reference to customer use case)case committee.
The impact on HEAT templates for Feature alignment is not yet clear.
Use Cases
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
Jira Legacy server System Jira
| server | System Jira |
|---|
...
...
jqlQuery project =
| jqlQuery | project = |
|---|
...
VVP AND issuetype = Epic AND fixVersion = "Dublin Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
| VVP AND issuetype = Epic AND fixVersion = "Dublin Release" | |
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
Stories
Jira Legacy server System Jira
| server | System Jira |
|---|
...
...
jqlQuery project =
| jqlQuery | project = |
|---|
...
VVP AND issuetype = Story AND fixVersion = "Dublin Release" serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
| VVP AND issuetype = Story AND fixVersion = "Dublin Release" | |
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
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.
...
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.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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).
| 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
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.
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.
...