Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

To fill out
API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)High level description of 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 NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description
Service Registration
1/1/2018release API Freeze dateMicroservice Bus API Documentation
Service Discovery
1/1/2018release API Freeze dateMicroservice Bus API Documentation
JAVA SDK
1/1/2018release API Freeze dateMicroservice 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, ...).

NameDescriptionVersion
To fill outTo fill outTo fill out

...

ConsulConsul is a distributed, highly-available, and multi-datacenter aware tool for service discovery, configuration, and orchestration. 0.9.3
OpenRestyOpenResty® 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
RedisRedis 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.

  1. Unit test: the goal is 50% coverage for Amsterdam Release.
  2. Functional test: Leverage the robot framework infrastructure to provide the functional test.
  3. Integration test: Support integration team to provide the end to end integration test.
  4. 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.

...