Overview

Scope

What is this release trying to address?

MSB(Microservices Bus) provides key infrastructure functionalities to support ONAP Microservice Architecture(OMSA), which includes:

• Provides RESTFul API for service registration/discovery
• Provides JAVA SDK for service registration and access
• Provides a transparent service registration proxy with OOM-Kube2MSB
• Provides a transparent service communication proxy which handles service discovery, load balancing, routing, failure handling, and visibility by Internal API Gateway(Current implementation) and Mesh sidecar(WIP)
• Provides an External API Gateway to expose ONAP services to the outside world
  
  

Note: The current name MSB(Microservices Bus) can't  well explain the project anymore, we're considering to change to a new name which can better reflect the scope and functionalities of this project.

Use Cases

MSB is an infrastructure project, it means that MSB supports every ONAP use case with no difference.

Minimum Viable Product

• Meet the planned Beijing platform maturity(S3P) requirements
• Reach out to help other projects integrate with MSB 

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Epics

Stories

Longer term roadmap

• Investigate service mesh(Istio) and integrate Istio into OMSA when it's production ready.
• Work together with Microservice subcommittee and other projects such as OOM/AAF/Logging to achieve OMSA(ONAP Microservice Architecture) to support carrier-grade ONAP platform.

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

Architecture

High level architecture diagram

This diagram shows how MSB project fits in the ONAP Architecture in a very high-level view.

If we take a closer look at ONAP Microservice Architecture, we get this diagram. The yellow blocks are currently in this project.

Please note that this diagram is a functional view of OMSA, which is not mapped to specific projects. So some of the blocks are currently implemented in this project, some of the blocks are implemented in other projects such as OOM and DMaaP, and other blocks may not exist yet, which need to be implemented or integrate with opensource projects to provide these functionalities. MSB will work with the related projects to provide all the OMSA functionalities to support a reliable, resilient and scalable ONAP Microservice Infrastructure.

MSB will provide service mesh as a transparent service communication layer which handles service discovery, load balancing, routing, failure handling, and visibility. 

Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

• API Incoming Dependencies

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

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 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.

• 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, ...).

• 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.

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.

• Known Defects and Issues

Provide a link toward the list of all known project bugs.

• Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

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 recommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

• Documentation, Training

• Reach out to each project to help them to integrate with MSB, including tutorial, demonstration and code example.
• Provide introduction, guideline and API documentation in ONAP wiki.
• Populate release documentation content to http://onap.readthedocs.io includes items such as:
  • Installation instructions
  • Configuration instructions
  • Developer guide
  • End User guide
  • Admin guide
  • ...

Other Information

• Vendor Neutral

All proprietary trademarks, logos, product names, etc. have been removed to comply with this rule and be agnostic of any proprietary symbols. If there is any new findings, the team promises to remove them ASAP.

• Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.