deploy-slurm-cluster

A procedure for installing and checking Slurm, a system that schedules jobs across computing servers, on a GPU cluster using DeepOps.

In plain words
What is it for?
Use it to prepare hosts, install NVIDIA drivers and Slurm, configure shared storage and health checks, and verify that cluster jobs can run.
Why use it?
It turns several GPU servers into a managed cluster and checks the setup before and after installation. This helps catch access, driver, and configuration problems before workloads run.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/nvidia/deepops/deploy-slurm-cluster
Any agent
npx skills add NVIDIA/deepops --skill deploy-slurm-cluster
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/deepops

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 625 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.00625
Opus 5 $0.00021 $0.00313
Sonnet 5 $0.00008 $0.00125
Haiku 4.5 $0.00004 $0.00063

Measured 2d ago against content hash 254f68140b5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deploy-slurm-cluster scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/deploy-slurm-cluster/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploy a Slurm GPU cluster

Preconditions

  • Ubuntu 22.04/24.04 or RHEL/Rocky 8/9 hosts you may fully manage (driver installs may reboot them; no active users or workloads).
  • SSH access from the provisioning machine to every host as a sudo-capable user.
  • Run everything from the repository root.

Procedure

  1. Prepare the environment and verify it:

    git submodule update --init --recursive
    ./scripts/setup.sh
    cp -r config.example config
    
  2. Edit config/inventory: put the controller under [slurm-master] and compute nodes under [slurm-node] (a single machine can be both). Set the connection user in [all:vars] if not root.

  3. Preflight — must pass before deploying:

    python3 scripts/validation/deepops_doctor.py --remote --json
    

    Fix anything in failures (each check's detail says how) and rerun.

  4. Deploy:

    ansible-playbook -l slurm-cluster playbooks/slurm-cluster.yml
    

    This installs NVIDIA drivers, builds and configures Slurm, and sets up munge, NFS, and node health checks. Expect roughly 30–60 minutes on a first run.

  5. Validate on a cluster node — the success signal is this, not the play recap:

    python3 scripts/validation/validate_slurm.py --json
    

    Require "ok": true with gpu_job_ok: true and nodes_unavailable: 0.

Failure branches

  • Playbook fails on a transient error (mirror timeout, apt lock, network blip): rerun the same playbook; it is idempotent. A converged rerun ends with changed=0.
  • nvidia-smi works in the validator's srun job but "fails" over SSH: that is the login GPU-hide behavior, not an error (see AGENTS.md gotchas).
  • gpu_job_ok: false with driver errors: follow skills/diagnose-driver-install/.
  • Node shows down or drained in node_states: check scontrol show node <name> for the reason; after fixing, resume with scontrol update nodename=<name> state=resume.
  • Wrong or stale host facts after reprovisioning a node: rerun with --flush-cache.

Read the full file on GitHub · 73 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 73 lines · 42 tokens per session scan A 254f68140b5f

Subscribe to this mod's changes

deploy-slurm-cluster is a skill published in the GitHub repository NVIDIA/deepops (1,471 stars, last pushed today), licensed BSD-3-Clause. It adds 42 tokens to every session and 625 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.