...
| 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 | Beijing |
| Project Lifecycle State | Incubation |
| Participating Company | China Mobile, ZTE, Huawei, Raisecom. |
Scope
What is this release trying to address?
Describe the problem being solved by this release.
...
- Support NS/VNF scaling
- Provide Monitor GUI for VM alarm and performance
- Integration with Image Management Project
- 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: VoLTE(approved)
- Enterprise CPE(stretch goal)
Minimum Viable Product
Describe the MVP for this release.
...
Integration specification for OOM/Logging/IM
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 |
LCM | In | H | VoLTE Use Case Instantiation, Termination, Scaling |
VNF Monitor | In | H | VNF Alarm and Performance |
VM Monitor | In | H | VM Alarm and Performance |
| Topology | In | H | The visualization of the topological relation among various instances(TBD) |
Integration with other projects:
Functionality Name | In or Out | Priority | Stretch |
A&AI -IM Image mangement Integration | In | M | Integration with A&AI- IMImage Management |
Logging Integration | In | M | Integration with Logging |
Epics
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Stories
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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...) of this release.
Deliverable Name | Deliverable Description |
Service LCM Portal | Providing GUI of service life cycle management |
VNF Monitor Portal | Providing GUI for VNFs alarm and performance |
VM Monitor Portal | Providing GUI for VMs alarm and performance |
Sub-Components
List all sub-components part of this 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 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 | 1Awaiting guidance from Benchmark subcommittee | Need to work with the benchmarking project and define the critera
|
| |||||||||||
| Stability | 0 | 1We | assume that integration team will Need to do a 72 hours soak test for VF-C
|
| |||||||||||
| Resiliency | 1 | 2automated detection and recovery | 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 | 01(*) | *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 logging. | 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
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.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
| Portal Platform API | API for integration of portal applications | |||
Catalog API (SDC) | API to read the NS and VNF Catalog | |||
SO API(Modeling) | API for NS instantiation and termination | |||
Micro-services bus API | API for registration and use of micro-services bus | |||
DMaaP API | API for VNFs/VMs fcaps data subscription | |||
A&AI API | API for gettring inventory and image management | |||
| VF-C API | API for NS instantiation and termination |
API Outgoing Dependencies
None
Third Party Products Dependencies
None.
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 Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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.
...