← 🗂️ Scheduling & Orchestration
Core
Slurm for AI Clusters
Slurm is the scheduler most large training clusters still run, because it was built for exactly this shape of work: long jobs that need many nodes at once, launched with one command, placed with knowledge of the network. A candidate for a training-infrastructure role is expected to read an sbatch script, know how GPUs are requested and enforced, and explain why a job is stuck in the queue. This page covers the model, the commands that matter, the GPU-specific configuration, and the failure modes a platform engineer meets.
a free account unlocks the core curriculum tier · no card
RELATED CONCEPTS
LESSONS THAT TEACH THIS
PRACTICE THIS IN REAL QUESTIONS
Kubernetes, Slurm & GPU SchedulingExplain how a Slurm job actually gets its GPUs: GRES, partitions, cgroups, and the sbatch that lands 8 GPUs on one node.→Kubernetes, Slurm & GPU SchedulingSlurm or Kubernetes for a 2,000-GPU training cluster? Make the case, and tell me what you lose either way.→AI Infrastructure System DesignDesign a training cluster for 10,000 GPUs: pods, fabric, storage, failure domains and the scheduler. Justify every number.→AI Infrastructure System DesignDesign a training cluster for a one-trillion-parameter MoE. Size it, choose the parallel layout, and map it onto the fabric.→Kubernetes, Slurm & GPU SchedulingWalk me through what happens when a pod asks Kubernetes for four GPUs, from the manifest to the container seeing them.→AI Infrastructure System DesignWalk me through an inference platform for a hosted LLM. What are the pieces, and what does each one do?→
