| Table of Contents | ||
|---|---|---|
|
Overview
...
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
...
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
Not applicable No new API Incoming Dependency for this release.
The previous dependencies i.e.AAI, SDC, (m)SO, Portal remain unchanged.
API Outgoing Dependencies
...
| Third Party | Description | Version |
|---|---|---|
| Docker | Docker container host | Latest one |
| MariaDB | SQL DB | 10.1.11 |
Testing and Integration Plans
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| None 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.