...
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.
Functionality Name | In or Out | Priority | Stretch |
NS LCM | IN | H | NS instance creation, NS instance termination |
VNF LCM(GVNFM) | IN | H | VNF deployment, termination according to the VNF information model |
VNF FCAPS | IN | M | Collection fcaps data from the EMS |
Resource Granting | IN | H | Grant the resources requested from VNFMs |
VNFM Integration | IN | H | Integration with specific VNFMs of vendors to deploy commercial VNFs |
VNF Integration(GVNFM) | IN | H | Integration with the VNF |
Interface provided | IN | H | Provide restful interfaces to Policy/SO/VID/portal |
NS LCM | IN | M | NS instance healing |
VIM Integration | IN | H | Integration with multi VIMs via Multi-VIM. |
NS LCM | OUT | M | NS instance scaling |
Resource Granting | OUT | M | Intelligent monitoring, allocation and reservation resources based on the requirement of VNFs |
A&AI Integration | In | M | Integration with A&AI |
SDC Integration | In | M | Integration with SDC |
...
Epics&Stories(draft)
NS Package Management
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description |
NS LCM | NS lifecycle management |
VNF Fcaps | Collect fcaps data from the EMS |
NS Resource Management | NS Visualize resources and instantiations resources management |
VNFM Drivers | VNFM drivers, including specific VNFM drivers |
VNF LCM(GVNFM) | VNF lifecycle management |
VNF Resource Management?GVNFM? | VNF Virtual Resource Management |
VNF Init Configuration(GVNFM) | VNF Init Configuration and Management |
Sub-Components
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
...
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) |
Catalog API (SDC) | API to read the NS and VNF Catalog | |||
Parser API | 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 |
API Outgoing Dependencies
API this release is delivering to other releases.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
NSLCM API Definition | Network services lifecycle management APIs | Link toward the detailed API description | ||
VNFM Driver API Definition | VNFM Driver component southbound APIs | |||
VNF LCM API Definition | provide 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 |
WSO2 | Workflow execution engine | |
ARIA | TOSCA Parser | |
Parser | Openstack Parser ??? |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.