...
| 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, intelIntel |
Scope
What is this release trying to address?
...
- 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:
...
...
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Hardware Platform Enablement In ONAPUse Case: VoLTE(approved)
Use Case: Residential Broadband vCPE (Approved)
Enterprise vCPE - stretch goal
...
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/VNF Scaling
...
IN
...
H
...
NS/VNF scaling
...
VNF LCM (GVNFM)
...
IN
...
H
...
VNF instantiate, termination through GVNFM
...
Open source VNF Integratio(GVNFM)
...
IN
...
H
...
Integration with the open source VNF(HPA)
...
Integration with other projects:
...
Functionality Name
...
In or Out
...
Priority
...
Stretch
...
A&AI -Image Manager Integration
...
In
...
M
...
Integration with A&AI- Image Manager
Epics
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Performance | 0 | 1 | Need to work with the benchmark benchmarking project and define the critera
|
| ||||||||||
| Stability | 0 | 1 | Need to do a 72 hours soak test for VF-C
|
| ||||||||||
| Resiliency | 1 | 2 | automated detection and recoveryNeed 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 | support ONAP standard loggingNeed to work with Logging team to identify the logging guidline.
|
| ||||||||||
| Usability | 1 | 1 | documentation is already in onap.readthedocs.io, will continue to improve
|
|
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| 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.
...