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 5 Current »

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 GatewayWebsocket SupportAuth PluginCommentsContact

aaf






WIP
aaiWIPDoneN/AWIP


appc






clampDoneDoneWIPWIPWIP

cli






dcaegen2WIPWIPWIPWIPWIP

DMaaPWIPWIP



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






ESRDoneDoneN/ADone


HolmesDoneDoneDoneN/A

Holmes 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






msoDoneDone




multicloudDoneDoneN/ADone


musicWIPWIP





oomN/ADoneN/AN/A

Automatically service registration via kub2msb
policyDoneDoneDone
WIP
/wiki/spaces/DW/pages/16272213
portal






sdc






sdnc






uuiDoneDone




vfcDoneDoneN/ADone


vid






vnfsdk







JIRA

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

  • No labels