Skip to main content
Below is a command reference guide for the RDT. Every command also accepts the global options (--user, --key, --password, --ask-password, --verbose, --version). Each command also has a short alias, shown in parentheses next to its name below (aliases aren’t shown in --help output, but work the same as the full name). Run rdt <command>
--help at any time for the same information from the CLI itself.

config (alias: c)

Manage RegattaDB configuration files. See Creating & Managing Configs for a guided walkthrough.

config create (alias: cr)

config print (alias: p)

config edit (alias: e)

config list (alias: ls)

No options. Lists both packaged templates and saved configs.

config load (alias: l)

config remove (alias: rm)

distribute (alias: di)

Distributes Regatta RPMs to every node.

setup (alias: st)

Installs RPMs and configures nodes (see System Setup Overview).

start-services (alias: ss) / stop-services (alias: sps)

Starts or stops the System Manager and SNA as node-level services.

configure (alias: co)

Registers the nodes, devices, and modules with the System Manager.

start-cluster (alias: sc) / stop-cluster (alias: stop)

Starts or stops every configured module via the System Manager (MANAGE SYSTEM START/ MANAGE SYSTEM SHUTDOWN).

create-cluster (alias: ccl)

Runs the full pipeline in one command: distribute → setup → start-services → configure → start-cluster.

reset (alias: re)

Stops services, clears all RegattaDB data, and restarts services. Does not automatically reconfigure or restart the database afterward. See RegattaDB Lifecycle.

clean (alias: cl)

Removes Regatta’s installation, files, logs, and traces from every node (preserving RDT itself where it’s installed; see What Changes on Your Nodes).

collect (alias: coll)

Collects debug information from RegattaDB nodes.