Enhancement from R1
- Provides HTTPS endpoint at MSB API gateway
Now the client can either send an HTTP request to 80(VM)/30081(k8s) or an HTTPS request to 443(VM)/30443(k8s) of MSB Internal API gateway to access the services.
- MSB-140Getting issue details... STATUS - MSB JAVA SDK supports HTTPS service registration
HTTPS service registration is supported by REST API, kube2msb and MSB Java SDK now.
- MSB-152Getting issue details... STATUS - Support websocket service
MSB API gateway can proxy websocket service now.
Service registration is the same as normal REST service.
Client sends a websocket request to API gateway, API gateway handles the service discovery and load balacing, then the client gets the push notification.
- MSB-156Getting issue details... STATUS
S3P Updates
- Security
- CII Badge
- SONAR code coverage. Reach or surpass the 50% goal on all repos.
- Nexus IQ scans:
- All critical license issues are cleared
- Most of the critical security issues are cleared. The left one is Remote Code Execution (RCE) introduced by the jackson-bind, which is an indirect dependency of some fundamental 3-party libraries such as dropwizard, Hibernate and swagger. We are still looking for possible solution or mitigation.
- Provides HTTPS endpoint at MSB API gateway to provide encrypted communication
- MSB-140Getting issue details... STATUS
- Scalability and Resiliency
- Reach out to help ONAP projects to integrate with MSB
- Create a wiki page to track the integration progress: MSB Integration Status
- Deploy multiple API Gateway and discovery instances inside MSB.
- MSB-117Getting issue details... STATUS
- Performance and stability
- Manageability
Information/Data Model Alignment
N/A, MSB doesn't use Information/Data Model produced by Modelling subcommittee.
API Updates
No API change in this release.