The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
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
...
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
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| OpenStack Proxy endpoint | OpenStack APIs (align to newton release) with proxied endpoints exposed by each plugin (OpenStack, VIO) | Ready Since Amsterdam Release | Ready Since Amsterdam Release | |
| VFC orientied APIs | abstract APIs for VFC which is inherited from OPENO for each plugin (OpenStack, VIO) | Ready Since Amsterdam Release | Ready Since Amsterdam Release | https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html |
| OOF oriented APIs | Capacity check to filter out those underlying VIM/Cloud without adequate resources for VNF placement | Ready Since Beijing Release | Ready Since Beijing Release | https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html |
| VIM/Cloud LCM API | Registry API is used to discover infrastructure's resources, including HPA and register them into AAI | Ready Since Amsterdam Release | Ready Since Amsterdam Release | https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html |
| FCAPS configuration API | FCAPS configuration API is to provision VESagent with VES collector endpoint, metric to collect, event to report, etc. | Ready Since Beijing Release | Ready Since Beijing Release | |
| SO oriented APIs | Generic API for SO to adapt to various VIM/Cloud type with MultiCloud plugin | Ready Since Dublin Release | Ready Since Dublin Release | https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html |
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
Resources
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
...
The milestones are defined at the Release Planning: Honolulu Istanbul 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 Istanbul Documentation
Other Information
Vendor Neutral
...