...
The VF-C Beijing release has two primary objectives: 1. improving platform maturity ; 2. supporting use cases.
- System maturity enhancement: integration with Logging/A&AI-Image Manager
2. Functionality enhancement to existing use cases, : NS/VNF scaling, HPA feature support, indirect mode support
3. Maturity enhancement to existing functionalities, including VF-C dummy case for developer,: interface align ETSISystem maturity enhancement, add ? integration with Logging/A&AI-IMOpensource VNF
Features and Functionality for this Release:
- NS/VNF scaling
- HPA feature support
- Multi-cloud Indirect mode
- VF-C dummy case for developer, such as vFW/vLBAdd integration with OOM/integration with opensource VNF
- Integration with Logging/A&AI-IMImage Manager
- HPA support- stretch goal
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
...
LCM(instantiate/terminate/heal/scaling) and FCAPS for VNFs VNFs which included in VoLTE use case
LCM(instantiate/terminate) for opensource VNFs
Integration specification for Logging/A&AI-IMImage Manager
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.
Functionality Name | In or Out | Priority | Stretch | |
NS Scaling | IN | H | NS scaling | |
VNF Scaling | IN | H | VNF Scaling | |
VNF LCM (GVNFM) | IN | H | VNF deploymentinstantiate, termination through GVNFM | |
VNF Integration(GVNFM) | IN | H | Integration with the VNF | |
HPA support (GVNFM)- stretch goal | INM | L | GVNFM HPA feature support |
...
Functionality Name | In or Out | Priority | Stretch |
| Logging Integration | In | M | Integration with Logging |
A&AI - IMLogging Image Manager Integration | In | M | Integration with LoggingA&AI- Image Manager |
Epics
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Deliverable Name | Deliverable DescriptionNS/VNF Scaling API | NS/VNF Scaling API to So/Policy/UUI |
Optimized NS/LCM API | Provide the Optimized NS/LCM API/UUI | |
Indirect mode proxy | Provide Indirect mode proxy function | |
HPA feature parse | Provide HPA feature parse function | |
GVNFM with improvement function | Provide GVNFM which can used to support vFW/vLB use case | |
| 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 |
New deliverables in this release: NS/VNF Scaling API?Optimized NS/LCM API? Multi-cloud Indirect mode proxy? GVNFM with improvement function.
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
TBD
Architecture
High level architecture diagram
...
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 | |||||
| A&AI Image Manager API | API to get/store image | OOF API (TBD) | API to get vnf placement |
API Outgoing Dependencies
...
| Risk identified | Mitigation Plan | Contingency Plan | To fill out | To fill out | To fill outRisk Description | |
|---|---|---|---|---|---|---|
| HPA support | Move to the next release | Move to the next release | EPA modeling haven't been definded yet | |||
| Logging integration | Continue the current form of logging or writting log in accordance with the clear part of loging requirement | Continue the current form of logging or writting log in accordance with the clear part of loging requirement | Currently there is no explicit requirement about how to log |
Resources
Fill out the Resources Committed to the Release centralized page.
...