One of the most important goals for MSB Beijing release is to reach out every project and help the integration process with MSB. The purpose of this document is to keep track of the status of the integration process.
|Component||Service Registration for heats(OpenStack Deployment)||Service Registration for OOM(Kubernetes Deployment)||Service Access via SDK||Service Access via Internal API Gateway||Websocket Support||Auth Plugin||Comments||Contact|
MSB is designed as an extendable, pluggable architecture, so an auth plugin can be added to MSB api gateway to provide centralized auth.
|DMaaP||Done||Done||Message router REST endpoint is already registered and can be accessed by other services.|
External APIs should be registered to MSB External API gateway so they can be accessed by external systems.
|Holmes||Done||Done||Done||N/A||Holmes uses MSB JAVA SDK to register service because it's spun up by DCAE rather than OOM.||Guangrong Fu|
Kube2msb is used to automatically register services to MSB in kubernetes deployment.
|oom||N/A||Done||N/A||N/A||Automatically service registration via kub2msb|
|policy||Done||Done||Done||WIP||Integration of the Policy Platform with OOM and MSB|
|portal||Portal UI should be registered to MSB External API gateway so they can be accessed outside of ONAP.|
|uui||Done||Done||UUI should be registered to MSB External API gateway so they can be accessed outside of ONAP.|