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

MSB is designed as an extendable, pluggable architecture, so an auth plugin can be added to MSB api gateway to provide centralized auth.

aaiDoneDoneN/ADone


appc






clampDoneDoneWIPWIPWIP

cli






dcaegen2WIPWIPWIPWIPWIP

DMaaPDoneDone



Message router REST endpoint is already registered and can be accessed by other services.
External APIWIPWIP



External APIs should be registered to MSB External API gateway so they can be accessed by external systems.

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
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.
sdc






sdnc






uuiDoneDone



UUI should be registered to MSB External API gateway so they can be accessed outside of ONAP.
vfcDoneDoneN/ADone


vid






vnfsdk







JIRA

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

  • No labels