Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Overview

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.


Status

ComponentService Registration for heats(OpenStack Deployment)Service Registration for OOM(Kubernetes Deployment)Service Access via SDKService Access via Internal API GatewayCommentsContact

aaf






aaiWIPWIPN/AWIP
appc




clamp




cli




dcaegen2WIPWIP


DMaaPWIPWIP

Message router REST end point is already registered and can be accessed by other services.
External API




ESRDoneDone
Done
HolmesDoneDoneDoneN/AHolmes uses MSB JAVA SDK to register service because it's spun up by DCAE rather than OOM.Guangrong Fu
kube2msbN/AN/AN/AN/A

Kube2msb is used to automatically register services to MSB in kubernetes deployment.

logging Enhancements




mso




multicloudDoneDoneN/ADone
oomN/ADoneN/AN/AAutomatically service registration via kub2msb
policyWIPWIP


portal




sdc




sdnc




uuiDoneDone


vfcDoneDoneN/ADone
vid




vnfsdk





JIRA

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

  • No labels