DMS Overview

Lightbits' Data Mobility Service (DMS) is a standalone service running in a Docker container. It runs on dedicated resources outside a Lightbits cluster that manage and orchestrate the mobility of volumes and snapshots within the Lightbits cluster. The DMS is comprised of a few services deployed on a single server. The deployment is performed using Docker Compose.

The DMS solution does not include any Quality of Service (QoS) mechanisms by default. Running DMS - whether as a single instance or across multiple instances - can impact the overall performance of the Lightbits cluster. This potential impact should be carefully evaluated and taken into consideration when deciding to apply the DMS solution.

Services are grouped into three stacks:

  1. dms:

    • dms: A service that exposes the gRPC/REST API.
    • discovery-client: Lightbits discovery client that performs auto discovery and NVMe connect.
    • dmscli: Command line to interact with the DMS service.
  2. temporal:

    • postgres: A database for durable workflows and activities.
    • temporal-server: A workflow engine that orchestrates complex long-running tasks.
    • temporal-ui: A UI to visualize workflow state, progress, and status.
  3. observability: (optional)

    • node-exporter: Exports metrics from the DMS server.
    • prometheus: Collects and stores time series metrics from node-exporter, the DMS service, and workflow metrics.
    • grafana: Visualizes metrics recorded by Prometheus, via dedicated and customizable dashboards.

Lightbits recommends running Prometheus and Grafana services externally to the DMS server. However, optional support is provided to run them on the DMS server for ease of use, if such services are not already running elsewhere in the system.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
On This Page
DMS Overview