...
Table of Contents | ||
---|---|---|
|
Overview
Project Name | Enter the name of the project |
---|---|
Target Release Name | Beijing |
Project Lifecycle State | Incubation |
Participating Company | China Mobile ,ZTE, Huawei, Nokia ,VMware, Boco, Jio, raisecom |
, Intel |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Functionality enhancement to existing use cases?NS/VNF scaling?EPA feature support? indirect mode
Maturity enhancement to existing functionalities?including VF-C dummy case for developer, interface align ETSI
...
.
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, enhance stability,performance,security etc.
2. Functionality enhancement to existing use cases: scaling, HPA
3. Maturity enhancement to existing functionalities: interface align ETSI, indirect mode support
...
Features and Functionality for this Release:
- NS/VNF scaling
- EPA feature support
- Indirect mode
- VF-C dummy case for developer?such as vFW/vLB
- Add integration with OOM/Logging/A&AI-IM
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Use Case: Residential Broadband vCPE (Approved)
Enterprise vCPE - stretch goal
Minimum Viable Product
Describe the MVP for this release.
LCM(instantiate/terminate/heal/scaling) for NS
LCM(instantiate/terminate/heal/scaling) and FCAPS for VNFs vendor VNFs
LCM(instantiate/terminate) for open source VNFs
Integration specification for OOM/ 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 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
...
NS LCM
...
IN
...
M
...
NS instance healing
...
NS LCM
...
OUT
...
M
...
NS instance scaling
...
Resource Granting
...
OUT
...
M
...
Intelligent monitoring, allocation and reservation resources based on the requirement of VNFs
...
Interface provided
...
IN
...
H
...
Provide restful interfaces to Policy/SO/VID/portal
Integration with other projects(VF-C will consume the interfaces these projects provided ):
...
Functionality Name
...
In or Out
...
Priority
...
Stretch
...
VIM Integration
...
IN
...
H
...
.
...
A&AI Integration
...
In
...
M
...
Integration with A&AI
...
SDC Integration
...
In
...
...
Integration with SDC
...
Epics
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 |
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.
...
Indicate where your project fit within the ONAP Archiecture 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
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Performance | 0 | 1 | Need to work with the benchmarking project and define the critera
|
| ||||||||||
Stability | 0 | 1 | Need to do a 72 hours soak test for VF-C
|
| ||||||||||
Resiliency | 1 | 2 | Need to work with OOM team to learn more about the mechanism they can provide.
|
| ||||||||||
Security | 0 | 1 | increase test coverage to 50% and need help with CII badging
|
| ||||||||||
Scalability | 0 | 1(*) | *NOTE - due to lack of resources, VF-C may not achieve level 1 for all components in this release. and It is "Low" priority per Jason's slides from TSC 1/4/2018.
|
| ||||||||||
Manageability | 0 | 1 | Need to work with Logging team to identify the logging guidline.
|
| ||||||||||
Usability | 1 | 1 | documentation is already in onap.readthedocs.io, will continue to improve
|
|
API Incoming Dependencies
...
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 | |||
A&AI Image Manager API | API to get/store image |
API Outgoing Dependencies
API this project is delivering to other projects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
NSLCM API Definition | Network services lifecycle management APIs, including scaling API | Link toward the detailed API description | ||
VNFM Driver API Definition | VNFM Driver component northbound APIs, including scaling API | |||
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 |
---|
activiti workflow engine | workflow execution engine |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
Gaps identified | Impact |
---|---|
To fill out | To fill out |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
Risk identified | Mitigation Plan | Contingency Plan |
---|
Risk Description | |||
---|---|---|---|
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.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
It is not expected to have a detailed project plan.
Date | Project | Deliverable |
---|---|---|
To fill out | To fill out | To fill out |
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...