TunePlane is designed to work on one GPU server and on a centrally governed multi-node cluster,
without a different product for each. What changes between them is which of the pieces below you
actually need.
Always
For a team
Which psycopg the console uses. The shipped image compiles psycopg[c] against the base
image’s libpq, so TLS to a managed Postgres validates against the certificates the image trusts
and a libpq security fix arrives with the next image rebuild. psycopg[binary] — the same C code
with its own libpq and its own OpenSSL bundled inside the wheel — is what a development checkout
gets, because it needs no compiler. Installing the wheel yourself, pick one:
tuneplane-server[c] (needs libpq-dev and a compiler) or tuneplane-server[binary]. With
neither, psycopg falls back to a pure-Python binding: slower, never broken.
A deployment with more than one console replica and no Redis has background roles disabled — storage
accounting, diagnosis, the daily report and the watchdog simply do not run. The
scheduled tasks page says so in a banner, but it is easy to miss. Per executor
local
agent
kuberay
slurm
One machine. Docker or Podman, and NVIDIA container runtime for real GPU passthrough. Nothing
else. This is the right starting point even for a team — moving to another executor later is a
setting, not a migration.
Several bare-metal machines, each running tuneplane-node. Requires the storage root mounted at the
same path on the console and every node, and a shared bearer token both sides hold. A missing
token refuses startup rather than running unauthenticated.
A Kubernetes cluster with the KubeRay operator, a GPU device plugin, and an RWX PVC for the
storage root. An RWO claim does not fail outright — it gives each pod its own volume, so
checkpoint shards split across nodes and the run cannot be resumed.
slurmrestd reachable over REST, with a JWT. The control plane never falls back to sbatch or
SSH. Container images must be available as SIF or SQSH through
TUNEPLANE_RUNTIME_REGISTRY_FILE, and the container runtime profile must be chosen explicitly.
Network
The second row is the one people miss. A console that users can reach is not automatically a console
that a worker node can reach.
Optional, and what you lose without each
