The content of this template is expected to be fill out for M1 Release Planning Milestone.
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
...
Describe the problem being solved by this release
1. Complete Instance storage function for supporting test environment auto deploy of NFV Testing Automatic Platform
2. Improving platform maturity (TSC Muse have)
3. Supporting use cases identified by ONAP and integration: vCPE
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Use Case: Residential Broadband vCPE (Approved)
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
...
Describe the MVP for this release.
VF-C will include the necessary sub-components supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
LCM(instantiate/terminate/heal/scaling) for NS and Vendor VNFs
FCAPS for vendor VNFs
LCM(instantiate/terminate) for open source VNFs
Minimum VF-C components supporting above functionalities:
NSLCM/GVNFM/Workflow/Vimproxy/EMS driver/vendor VNFM driver
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.
...
| Deliverable Name | Deliverable Description | ||
|---|---|---|---|
| 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 | To fill out | To fill out |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
...
Indicate where your project fit within the ONAP Architecture diagram.
Block and sequence diagrams showing relation within the project as well as relation with external components are expected.
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
Please fill out the centralized wiki page: Frankfurt Release Platform : https://wiki.onap.org/display/DW/Guilin+Release+Platform+Maturity
API Incoming Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||||
|---|---|---|---|---|---|---|---|---|---|
Parser API(Modeling) | API for parsering TOSCA file | Etsicatalog API Document | |||||||
Micro-services bus API | API for registration and use of micro-services bus | Microservice Bus API Documentation | |||||||
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 | AAI REST API Documentation | |||||||
| 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 |
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 out|
|---|---|---|---|---|---|
| Django | https://www.djangoproject.com/ | 2.1.10 | |||
| djangorestframework | https://www.django-rest-framework.org/ | 3.10.3 |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...