...
MSB is part of the underlying platform to support onap microservice communication.
MSB consists of these sub-components:
- Registry Service information storage, MSB uses Consul as the service registry.
- MSB Discovery Provides REST APIs for service discovery and registration.
- API Gateway Provide service request routing, load balancing and service governance. It can be deployed as external Gateway or Internal Gateway.
- MSB SDK A Java SDK for point to point communication.
...
- OOM deploy/start/stop ONAP components.
- Registrator watches the kubernetes event.
- Registrator reads the service definition from kubernetes deployment specs.
- Registrator sends service endpoints to MSB discovery when ONAP apps are deployed by OOM.
- Registrator registers service endpoint info to MSB. It also updates the service info to MSB when ONAP components are stopped/restarted/scaled by OOM
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.
...
- 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
...
- 0 – none
- 1 – 72 hours component level soak w/random transactions
- 2 – 72 hours platform level soak w/random transactions
- 3 – 6 months track record of reduced defect rate
...
- 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
...
- 0 – none
- 1 – CII Passing badge + 50% Test Coverage
- 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
- 3 – CII Gold
...
- 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
...
- 1 – single logging system across components; instantiation in < 1 hour
- 2 – ability to upgrade a single component; tracing across components; externalized configuration management
...
- 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
Frankfurt Release Platform Maturity
API 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.
...
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
---|---|---|---|---|---|
Service Registration | RESTFul API for service registration with MSB. | 2019/01/24 | no change in this release | no change in this releaseRelease Planning#DublinReleaseCalendar | Microservice Bus API Documentation |
Service Discovery | RESTFul API for service discovery with MSB. | 2019/01/24 | no change in this release | no change in this releaseRelease Planning#DublinReleaseCalendar | Microservice Bus API Documentation |
JAVA SDK | JAVA SDK for service registration, discovery and inter-services communication. | 2019/01/24 | no change in this release | no change in this releaseRelease Planning#DublinReleaseCalendar | Microservice Bus API Documentation |
...
Name | Description | Version |
---|---|---|
Consul | Consul is a distributed, highly-available, and multi-datacenter aware tool for service discovery, configuration, and orchestration. | 01..94.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 |
...
Risk identified | Mitigation Plan | Contingency Plan |
---|---|---|
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
The project team comply with the ONAP Charter.
Reply to TSC Must Have Questions
- Document current upgrade component strategy : MSB has no persistent data, all services are registered to MSB by kub2msb when ONAP components are spun up by oom. So there is no need for an upgrade.
- SECCOM Perform Software Composition Analysis - Vulnerability tables : the current status is the same as R5 MSB Security/Vulnerability - Full Content, we're analysing the solvable vulnerabilities and create tasks for them.
- SECCOM Password removal from OOM HELM charts: No password in HELM charts.
- SECCOM HTTPS communication vs. HTTP: Plain HTTP endpoints will be removed.
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key MSB-398