Skip to main content
Make sure you’ve read Prerequisites first. This page covers installing RDT on your control node. If your control node has no internet access, see Offline Installation instead; if you’d rather run RDT from a container image, see Running RDT in a Container. RDT is distributed as the regatta-rdt RPM, one of the utility packages in Regatta’s tools suite. It’s installed like any other RegattaDB RPM package, from the local .rpm file included in your RegattaDB software package (see Prepare for Deployment for how these packages are delivered):
During installation you’ll be prompted to accept the Regatta EULA (or set ACCEPT_EULA=1 for unattended installs; see EULA Acceptance). By default, the RPM creates and installs for a regatta deployment user/group; to use a different one, set REGATTA_USER/REGATTA_GROUP (see Deployment User for the naming rules). Once installed, the RPM automatically installs RDT itself for the deployment user via pip install --user, bundling the self-contained Regatta Python driver (pyregatta) so no separate driver installation is needed.

​
Manual install (skip or retry the automatic step)

To skip the automatic install and only unpack the files, set AUTO_INSTALL=0 in the install command:
If the automatic install is skipped, or fails (for example on a node without network access), the install log is written to /var/log/regatta/rdt/install.log. You can then install (or reinstall) manually, as the deployment user:
Any extra arguments are forwarded to pip (e.g. --user, --break-system-packages). Because RDT is installed with --user, the rdt command lands in ~/.local/bin. If it’s not on your PATH, add it as follows:

​
Uninstalling

Removing the RPM uninstalls RDT automatically for the deployment user:
Set AUTO_INSTALL=0 in the remove command to skip this. You can also uninstall manually at any time, as that user:
Note that uninstalling only removes RDT itself, not the bundled pyregatta driver; it may be shared with other Regatta tools installed for the same user.

​
Installing from source

Installing from source requires the pyregatta driver to be available separately (it’s only bundled automatically by the RPM install path above).

​
Verifying the install

​
Next steps

Continue to Configuration Overview to create your first RegattaDB configuration.