DRAFT PROPOSAL FOR COMMENTS
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Amsterdam Release |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Huawei & VMWare |
...
| Deliverable Name | Deliverable Description |
|---|---|
| Message Router | Source Code / Executable / Docker Image |
| Data Router | Source Code / Executable / Docker Image |
Sub-Components
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
ONAP Dependencies
List the other ONAP projects your depends on.Micro Services Bus
Architecture
High level architecture diagram
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
...
| MSB | Service registry |
API Outgoing Dependencies
API this release is delivering to other releases.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
| DCAE |
Third Party Products Dependencies
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, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version | To fill out | To fill out | To fill out|
|---|---|---|---|---|---|
| AJSC | microservice application sever | AJSC 5 | |||
| Ubuntu | OS | ||||
| Docker | VM container |
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
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.
...
- 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.
- SonarQube will be used to test coverage report.
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.
...