...
| 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?
...
| Deliverable Name | Deliverable Description |
|---|---|
| VID application | Executable, Docker |
| MariaDB | SQL database
scheme |
| Release documentation | ONAP WIKI pages |
...
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
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | CM | Change management | TBD | TBDTBD | |
|---|---|---|---|---|---|---|---|---|---|
| NB Interface | REST API | TBD | TBD | Link toward the detailed API description |
...
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
...
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.
- 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 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan | |||
|---|---|---|---|---|---|
| None at this time | N/A | N/A | To fill out | To fill out | To fill out |
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.
...