| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Amsterdam |
| Project Lifecycle State | Planning |
| Participating Company | Amdocs, AT&T |
Scope
What is this release trying to address?
...
VID will contribute to the following use cases:
Use Case: Residential Broadband vCPE (Approved)
VID will continue to support to the following use case:
Minimum Viable Product
- 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.
Epics
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 (epic) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
| Deliverable Name | Deliverable Description |
|---|---|
| VID application | Executable, Docker |
| MariaDB | SQL database scheme |
| Release documentation | ONAP WIKI pages |
Sub-Components
Components Name | Components Repository name | Maven Group ID | Components Description |
|---|---|---|---|
| asdcclient | vid/asdcclient | org.onap.vid.asdcclient | VID SDC Client library |
ONAP Dependencies
Portal - Our application is compiled with the Portal SDK and is accessed as a "tab" in the Portal web application. Any changes to this sdk may require re-compilation on our end.
...
API Incoming Dependencies
No incoming dependenciesnew API Incoming Dependency for this release.
The previous dependencies i.e.AAI, SDC, (m)SO, Portal remain unchanged.
API Outgoing Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | CM |
|---|---|---|---|---|---|
| NB Interface | REST API | TBD | TBD | TBDLink toward the detailed API description |
Third Party Products Dependencies
N/A.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, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Third Party | Description | Version |
|---|---|---|
| Docker | Docker container host | Latest one |
| MariaDB | SQL DB | 10.1.11 |
Testing and Integration Plans
Test plan of every epic will be posted soonProvide 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.
- 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 Release.
List identified release gaps (if any), and its impact.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan | ||
|---|---|---|---|---|
| To fill out | To fill out | To fill outNone at this time | N/A | N/A |
Resources
Fill out the Resources Committed to the Release centralized page.
Release 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 recommended to provide these agreements and dates in this section.
...
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.