The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Jira Legacy | ||||||||
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
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.
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:multicloud
Architecture
High level architecture diagram
...
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 |
|---|---|---|
| Lack committed resource for MultiClod Azure component | Call for contributor from community | request waiver or de-scope this component from Guilin Honolulu Release |
Resources
Fill out the Resources Committed to the Release centralized page.Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:multicloud
Release Milestone
The milestones are defined at the Release LevelPlanning: Honolulu and all the supporting project agreed to comply with these dates.
...
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
Please refer to Honolulu Documentation
Other Information
Vendor Neutral
...