...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Beijing Release |
| Project Lifecycle State | Incubation Mature (Refer to ONAP Charter, section 3.3 Project Lifecycle for further information) |
| Participating Company | AT&T, Amdocs |
Scope
What is this release trying to address?
Describe the problem being solved by this release1. Platform maturity - enhance stability, performance, security etc. to strive for carrier-grade maturity.
2. New requirements:
a. Change management - support working without a scheduler component.
b. **TBD**
Use Cases
Describe VID will contribute to the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
Describe the MVP for this release.following use cases:
VID will continue to support to the following use case:
Use Case: Residential Broadband vCPE (Approved)
Minimum Viable Product
***OFIR
- Read only "ONAP global role" permission for VID users
- Specific role assignment for components instantiations
- Change management for selected work flows (Upgrade and Configuration)
- PNF support
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.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=vid and issuetype in (story) and fixVersion in ("Beijing release") serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Longer term roadmap
...
- Fully automated deployment of new VNFs without the need of manual intervention or configuration.
- Support workflows for change management by using the SDC as a provider of workflows capabilities
- Dashboarding scheduled and ongoing change management
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed agree 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.
...
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.
- Unit tests are run automatically as part of every code merge.
- Once the final Docker image is compiled, it will be installed onto a Docker host and will be checked to ensure no errors occur during start-up.
- Functional testing will occur to ensure that the use cases are functioning correctly.
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 Releaserelease.
List identified release gaps (if any), and its their impact.
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
...