...
| 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 | Enter the name of the release you are targeting to deliverAmsterdam |
| Project Lifecycle State | PlanningIncubation |
| Participating Company | China Mobile, AT&T, ZTE, Huawei |
Scope
What is this release trying to address?
Providing full Graphical User Interface (GUI) of VoLTE use case for operators and end-users.
...
- Service life cycle management for NS
- Monitoring system alarms
- Showing system performance
Use Cases
Minimum Viable Product
- Portal of service LCM for NS
- Portal of system alarms
- Portal of system performance
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 |
Monitor | IN | H | Monitoring system alarms |
Performance | IN | H | Showing system performance |
...
Epics
...
...
Epics
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Stories
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Longer
...
term roadmap
...
- Improve
...
Nested NSs.
...
- operations of VoLTE use case
- Improve operations of vCPE use case
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description |
NS LCM Portal | Providing GUI of NS lifecycle life cycle management |
VNF Fcaps | Collect fcaps data from the EMS |
NS Resource Management | NS Visualize resources and instantiations resources management |
VNFM Drivers | VNFM drivers, including specific VNFM drivers |
VNF LCM(GVNFM) | VNF lifecycle management |
VNF Resource Management?GVNFM? | VNF Virtual Resource Management |
VNF Init Configuration(GVNFM) | VNF Init Configuration and Management |
Alarms Portal | Providing GUI of system alarms |
Performance Portal | Providing GUI of system performance |
Sub-Components
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
List the other ONAP projects your depends on.
...
- Portal Platform
- DCAE
- SO
Use case Portal
VID
Multi-VIM
A&AI
SDC
Modeling
MSB
OOM
- VF-C
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.
...
Anyone reading this section should have a good understanding of all the interacting modules.
The color coding is as following:
- Green color of FBs (NFVO, G-VNFM/S-VNFM and EM) and interfaces (IFA013/SOL005, IFA007/SOL003, IFA008/SOL002, IFA006/OpenStack) implies full compliancy with ETSI NFV Release-2 specifications.
- Blue color of interface (3GPP Itf-N – northbound of EM) implies full compliancy with 3GPP SA5 specifications
- Yellow color of FBs (AA&I, MSO, DCAE and Policy) and interfaces (ECOMP message bus) implies un-changed ONAP message bus (same as used by APP-C)
- White color of interfaces implies that this particular interface is typically not standardized and remains proprietary
- Pink color of FB (ONAP Adaptor) shows the actual scope of the VF-C open source development effort
API Incoming Dependencies
List the API this release is expecting from other releases.
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 Portal Platform API (SDC) | API for integration of portal applications | ||||||
SO to read the NS and VNF CatalogParser API | API for parsering TOSCA fileNS instantiation and termination | ||||||
Micro-services bus API | API for registration and use of micro-services busMulti-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 inventoryalarms and performance data | |||
| VF-C API | API for NS instantiation and termination |
API Outgoing Dependencies
API this release is delivering to other releases.
...
API Name
...
API Description
...
API Definition Date
...
API Delivery date
...
API Definition link (i.e.swagger)
None.
...
NSLCM API Definition
...
Network services lifecycle management APIs
...
Link toward the detailed API description
...
VNFM Driver API Definition
...
VNFM Driver component southbound APIs
...
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
None.
...
WSO2
...
Workflow execution engine
...
ARIA
...
TOSCA Parser
...
Parser
...
Openstack Parser ???
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
Provide a link toward the list of all known project bugs.
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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).
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
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
- 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
- ...
| 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.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.