How Slurm HRES Plugins Integrate Quantum Processors into Supercomputing Scheduling: Why Traditional Resource Models Fail to Adapt to QPUs
A NVIDIA Technical Blog post details how the Hierarchical Resources (HRES) plugin in Slurm 26.11 models quantum processing units (QPUs) as cluster-level schedulable resources, addressing structural flaws in existing scheduling models such as generic resource binding to single nodes and license-based schemes causing compute node idling. It also outlines the implementation paths for two community plugins, QRMI and QDMI.
Quantum processors are being installed in supercomputing centers worldwide, running alongside high-performance computing systems. For scientists in fields such as chemistry, weather modeling, and engineering simulation, the QPU is simply another accelerator—like CPUs and GPUs—that they wish to request, reserve, and execute using familiar methods. However, prior to Slurm 26.11, the scheduler lacked a native way to model QPUs as schedulable resources. Integration solutions at each site were repeatedly customized, users faced different interfaces depending on the site, administrators struggled to maintain proprietary code that was difficult to upgrade, and QPU vendors had to rebuild integrations for every customer.
The root of the problem lies in the structural mismatch between the physical attributes of QPUs and Slurm's existing resource models. QPUs are typically cluster-wide accelerators and do not belong to any single compute node. Slurm's Generic Resource (GRES) mechanism, used for GPUs, binds devices to specific nodes—if that node fails, the QPU becomes unreachable until an administrator reconfigures the cluster. Another common approach combines licenses with SPANK plugins: while licenses represent cluster-wide resources, SPANK only intervenes after a node has been allocated, meaning a job can hold compute nodes idle while waiting for the QPU. Furthermore, multiple SPANK plugins for different QPUs compete for the same command-line options, and many rely on Slurm's internal APIs, creating a risk of breakage with every upgrade. Crucially, Slurm itself cannot detect whether a QPU is undergoing calibration or is offline, leading it to launch jobs that cannot utilize the device.