...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverFrankfurt |
| 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. | China Mobile ,ZTE, Huawei, Nokia ,VMware, Boco, Jio, raisecom, Intel, verizon |
Scope
What is this release trying to address?
Describe the problem being solved by this releaseThe VF-C Dublin release has following primary objectives:
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
...
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| Source Code | Source code for all VF-C components | ||
| Maven Artifacts | Maven Artifacts for all VF-C components | ||
| Docker Containers | Docker container associated with VF-C components | ||
| Documentation | VF-C detailed documentation |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||||
|---|---|---|---|---|---|---|---|---|---|
Catalog API (SDC) | API to read the NS and VNF Catalog | ||||||||
Parser API(Modeling) | API for parsering TOSCA file | ||||||||
Micro-services bus API | API for registration and use of micro-services bus | ||||||||
Multi-vim API | API to allocate resource to VIM | ||||||||
DCAE VES collector SB API | API to push vnf fcaps data to VES collector | ||||||||
A&AI API | API to store inventory | ||||||||
| OOF API | API to chose VIM which is used to deploy VNF | To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
API Outgoing Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||||
|---|---|---|---|---|---|---|---|---|
NSLCM API Definition | Network services lifecycle management APIs | To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description | ||
VNFM Driver API Definition | VNFM Driver component northbound APIs | |||||||
| VNF LCM API Definition | provide VNF lifecycle management APIs | |||||||
| Catalog API | NS/VNF package management APIs |
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version | ||
|---|---|---|---|---|
| To fill out | To fill out | To fill outactiviti workflow engine |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...