...
1, vFW
2, vDNS
3, vCPE
4, VoLTE
5, CCVPN
Minimum Viable Product
Describe the MVP for this release.
...
4, Security enhancement: secured communication
Stretch Goal
1, Use OOF selected flavor for HEAT based VNF orchestration
2, Security enhancement: RBAC enablement
23, Kubernetes plugin
34, azure plugin
45, StarlingX plugin
56, Cloud Region decommission
67, Deploy MultiCloud service to edge cloud with AAI in centralized ONAP
78, HEAT orchestration enhancement
89, SRIOV-NIC support
10, HPA telemetry data collection and persistence
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 Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox MULTICLOUD and issuetype in (epic) and resolution=Unresolved serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox MULTICLOUD and issuetype in (story) and resolution=Unresolved serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
| Deliverable Name | Deliverable Description | |
|---|---|---|
| Source Code | Source code for all Multi-VIM/Cloud components | |
| Executables | Executables in zip package for Maven Artifacts | Maven Artifacts for all Multi-VIM/Cloud components |
| Docker Images | Docker images for all Multi-VIM/Cloud components | |
| Documentations | Developer and user documentations for all Multi-VIM/Cloud components | |
| Release Note | Release Note cover all Multi-VIM/Cloud components |
...
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.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| eventListener/v5 | VES collector event publish APIs | N/A since It is ready now | N/A since It is ready now | https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/1359970816242677/ves.html?version=1&modificationDate=1503378662000&api=v2 |
API Outgoing Dependencies
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| 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
...