...
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Frankfurt |
| Project Lifecycle State | Incubation |
| Participating Company | China Mobile ,ZTE, Huawei, Nokia ,VMware, Boco, Jio, raisecom, Intel, verizon |
Scope
What is this release trying to address?
The VF-C
...
Frankfurt release has following primary objectives:
1. Improving platform maturity : Mariadb-Galera DB Consolidation ,security (i.e., S3P items)
2. Supporting use cases identified by ONAP and integration: vCPE
3. Supporting Functional Requirements identified:
ETSI Alignment ： migrate VF-C catalog to modeling etsicatalog
E2E Network Slicing: (supporting NSSMF,Stretch goal depend on the commit resource )
4. VF-C enhancement and new features:
Python upgrade from python2 to python3
JDK upgrade evaluate and migrate (Depend on the commit resource)
VF-C integrate with CLI to improve VF-C Usability
Improve GVNFM Driver as SOL003 adapter
Provide python-based Dmaap library
Supporting LCM Operation rollback(Stretch goal)
Add VF-C related use case vCPE on daily CI chains
5. Document current upgrade component strategy(TSC must have) Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-1576
6. SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must have) - plan to solve the most of the security issues, but also depends on the commit resource Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-1574
7. SECCOM Password removal from OOM HELM charts(TSC must have) Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-1575
8. SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-1577
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Use Case: Residential Broadband vCPE (Approved)
Requirements
Describe the use case this release is targeted for (better if reference to customer requirements).
ETSI Alignment Support
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
E2E Network Slicing Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-146 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-158
Minimum Viable Product
...
VF-C will include the necessary sub-components supporting the primary objectives: meeting platform maturity goals and supporting the use cases.
LCM(instantiate/terminate/heal/scaling) for NS and Vendor VNFs
FCAPS for vendor VNFs
LCM(instantiate/terminate) for open source VNFs
Minimum VF-C components supporting above functionalities:
NSLCM/GVNFM/Workflow/Vimproxy/EMS driver/vendor VNFM driver
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.
Epics
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox VFC and issuetype in (epic) and fixVersion = "Frankfurt Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Stories
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox VFC and issuetype in (story) and fixVersion = "Frankfurt Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) 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 components |
| 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.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
Architecture
High level architecture diagram
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the ONAP Architecture 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
Please fill out the centralized wiki page: Frankfurt Release Platform Maturity v1
API Incoming Dependencies
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.
...
| 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
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 | Link toward the detailed API description | ||||
VNFM Driver API Definition | VNFM Driver component northbound APIs | |||||
| VNF LCM API Definition | provide VNF lifecycle management APIs | Catalog API | NS/VNF package 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, ...).
...
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
Gaps
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
Please refer to Frankfurt Defect Status
Risks
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).
Please update any risk on the centralized wiki page - Frankfurt Risks
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.
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
...
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
Documentation, Training
Please update the following centralized wiki: Frankfurt Documentation
...
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
...