| Table of Contents | ||
|---|---|---|
|
Overview
...
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
Note: MSB project has no incoming dependency.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | To fill out | High level description of the APIDate for which the |
|---|---|---|---|---|---|---|
API
...
API Outgoing Dependencies
API this project is delivering to other projects.
Note: MSB project estimate that there will be no API modification during Beijing release, we will continue to use the same APIs published in Amsterdam.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
| Service Registration | 1/1/2018 | release API Freeze date | Microservice Bus API Documentation | |
| Service Discovery | 1/1/2018 | release API Freeze date | Microservice Bus API Documentation | |
| JAVA SDK | 1/1/2018 | release API Freeze date | Microservice Bus API Documentation |
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 |
...
| Consul | Consul is a distributed, highly-available, and multi-datacenter aware tool for service discovery, configuration, and orchestration. | 0.9.3 |
| OpenResty | OpenResty® is a full-fledged web platform that integrates the standard Nginx core, LuaJIT, many carefully written Lua libraries, lots of high quality 3rd-party Nginx modules, and most of their external dependencies. It is designed to help developers easily build scalable web applications, web services, and dynamic web gateways. | 1.11.2.3 |
| Redis | Redis is an in-memory data structure store, used as a database, cache and message broker. | 3.2.8 |
Testing and Integration Plans
...
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 test: the goal is 50% coverage for Amsterdam Release.
- Functional test: Leverage the robot framework infrastructure to provide the functional test.
- Integration test: Support integration team to provide the end to end integration test.
- All the above should be automation tests run on the LF Jenkins Infrastructure.
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.
...
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
MSB project follows the ONAP Beijing release milestones.
Team Internal 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 to provide these agreements and dates in this section.
...