...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
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 componets |
| 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.
...
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(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 |
API Outgoing Dependencies
...