Enhancements since 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.Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MSB-140 - MSB JAVA SDK supports HTTPS service registration
HTTPS service registration is supported by REST API, kube2msb and MSB Java SDK now.Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MSB-152 - 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.Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MSB-156
...
- 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
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MSB-140
- Scalability and Resiliency
- Reach out to help ONAP projects to integrate with MSB Microservices Bus Tutorial.pdf
- Create a wiki page to track the integration progress: MSB Integration Status
- Deploy multiple API Gateway and discovery instances inside MSBDeploy multiple API Gateway and discovery instances inside MSB.
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MSB-117
- Performance and stability
- Plan to define Define performance metrics and set up a baseline
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MSB-116
- Plan to define Define performance metrics and set up a baseline
- Manageability
- Plan to integrate with logging enhancement project to provide central Integrate with logging enhancement project to provide central Logging
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MSB-145 - Provide a portal to manage the registered services
- Integrate swagger UIs with MSB portal, the user can browse the REST API definition of all registered services
- Plan to integrate with logging enhancement project to provide central Integrate with logging enhancement project to provide central Logging
...