---
description: First steps on a Slinky instant cluster, logging in, checking the cluster, submitting batch and interactive Slurm jobs.
revision_date: 03.11.2026
---

# Quickstart

## Log in

SSH to the cluster's public IP. This lands you in the Slurm login pod as `ubuntu`, with the Slurm CLI ready to use:

```bash
ssh ubuntu@<cluster-ip>
```

The login pod has no `sudo`, and anything installed outside `/home` is lost when the pod restarts, so keep your files under `/home`. For admin work (`sudo`, `kubectl`, adding users), SSH to the login node itself on port `2222`:

```bash
ssh -p 2222 ubuntu@<cluster-ip>
```

!!! warning "Wait for the cluster to be ready"
    While the cluster is still being validated, the login message shows `*** <cluster> IS NOT READY YET: ... ***`. The line is gone once both [validation](https://docs.verda.com/clusters/cluster-basics/validation/) phases have finished, which can be a few minutes after the console shows the cluster as running. Wait for that before starting work.

Additional users are provisioned with [`slinky-user-add`](https://docs.verda.com/clusters/slinky/users/) and log in on port `22` the same way, as themselves, so their jobs run under their own identity. `srun id` shows which identity a shell submits as.

!!! info
    Clusters deployed before October 2026 use the opposite layout: port `22` is the login node and port `2222` is the login pod (off by default). See [How users log in](https://docs.verda.com/clusters/slinky/users/#how-users-log-in).

## Check the cluster

```bash
sinfo
```

Worker nodes appear as `slinky-0`, `slinky-1`, ... in the `all` partition and should be `idle` (or `mix`/`alloc` when busy).

## Run your first job

Each worker has 8 GPUs, so a 16-GPU job spans two nodes:

```bash
srun --gpus=16 nvidia-smi -L
```

!!! warning
    Steps only see the GPUs they request. With no `--gpus` (or `--gres=gpu:N`), `nvidia-smi` reports `No devices found.` inside the step. See [Job environment](https://docs.verda.com/clusters/slinky/job-environment/#gpus).

## Batch jobs

Write the script under `/home` (it is shared with the workers) and submit from there:

```bash
cat > /home/ubuntu/hello.sbatch <<'EOF'
#!/bin/bash
#SBATCH --job-name=hello
#SBATCH --nodes=2
#SBATCH --gres=gpu:8
#SBATCH --time=00:05:00
srun hostname
srun nvidia-smi -L
EOF

sbatch /home/ubuntu/hello.sbatch
```

Output lands in `slurm-<jobid>.out` next to where you submitted. Use `squeue` for active jobs, `sacct` for finished ones. The full command reference is in the [Slurm documentation](https://slurm.schedmd.com/man_index.html), which applies to Slinky unchanged.

## Interactive sessions

```bash
srun --nodes=1 --gres=gpu:1 --time=00:15:00 --pty bash
```

drops you into a shell on a worker with one GPU bound. For multi-node interactive work, hold an allocation with [`salloc`](https://slurm.schedmd.com/salloc.html) and run `srun` inside it.

## Where to put things

* **`/home`** is shared everywhere: job scripts, data and container images ([SIF files](https://docs.verda.com/clusters/slinky/containers/)). Run Python workloads in a container for now, not from a virtualenv on `/home`: see [Python environments](https://docs.verda.com/clusters/slinky/job-environment/#python-environments).
* **`/shared`** is a world-writable dataset area on the same shared filesystem: one stable path for team data, identical on the login pod and inside every job.
* **`/local`** inside a step is the worker's local NVMe: a per-node cache for datasets and checkpoints. It persists across jobs and node restarts, so a re-run landing on the same node finds its data already there.
* **`/tmp`** inside a step is also on the NVMe, but private to the job and deleted when the job ends. Copy results you want to keep to `/local` or `/home`.
* **Extra shared filesystems** attached to the cluster are mounted in the login pod and inside jobs too, at the same path as on the login node (`/<SFS_NAME>`). See [Shared filesystem for a cluster](https://docs.verda.com/storage/shared-filesystem/use-sfs-with-a-cluster/).

HPC-X and Lmod modules are not available inside jobs; use a container image with its own MPI/NCCL stack. See [Job environment](https://docs.verda.com/clusters/slinky/job-environment/).

## Next steps

* Add your team: [User management](https://docs.verda.com/clusters/slinky/users/)
* Run containers: [Containers (Pyxis, Apptainer)](https://docs.verda.com/clusters/slinky/containers/)
* Watch the queue and node health: [Observability](https://docs.verda.com/clusters/slinky/observability/)
* Worked examples: [Tutorials](https://docs.verda.com/clusters/slinky/tutorials/)
