...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverFrunkfurt |
| 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. | ATT, China Mobile, Intel, VMware, Wind River |
Scope
What is this release trying to address?
...
vFW/vDNS
vCPE
TSC must have :
- Document current upgrade component strategy
- SECCOM Perform Software Composition Analysis - Vulnerability tables
- SECCOM Password removal from OOM HELM charts
- SECCOM HTTPS communication vs. HTTP
Minimum Viable Product
Enhanced MultiCloud Plugin for StarlingX
...
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 this project is delivering to other projects.
...
| 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
...