NewsLayer.com
NewsLayer PulseLIVEBTC$82,951+0.85%ETH$2,510+1.42%SOL$110.35+1.82%XRP$1.4+1.52%DOGE$0.0861+2.10%ADA$0.2525+7.19%Total Cap$2.93T+0.89%Layer Index46 Neutral

Multi-Institutional Consortium Expands QRMI to Standardize Quantum-HPC Integration Across Major Workload Managers

A multi-institutional consortium comprising IBM Quantum, Pasqal, Alice & Bob, CINECA, Lawrence Livermore National Laboratory (LLNL), Oak Ridge National Laboratory (ORNL), and the STFC Hartree Centre has detailed the expansion of the…

Quantum Computing Report

Publisher

Oct 10, 2026 at 7:19 PM UTC · 3 min read

Multi-Institutional Consortium Expands QRMI to Standardize Quantum-HPC Integration Across Major Workload Managers
NewsLayer editorial artwork

A multi-institutional consortium comprising IBM Quantum, Pasqal, Alice & Bob, CINECA, Lawrence Livermore National Laboratory (LLNL), Oak Ridge National Laboratory (ORNL), and the STFC Hartree Centre has detailed the expansion of the open-source Quantum Resource Management Interface (QRMI).

Detailed in a research paper (arXiv:2607.19591), QRMI establishes a vendor-agnostic middleware layer that exposes quantum processing units (QPUs) as first-class schedulable resources alongside classical CPUs and GPUs. Building on IBM’s reference architecture for quantum-centric supercomputing, the updated framework extends QPU co-scheduling beyond Slurm to encompass six primary HPC workload managers and orchestrators: Slurm, PBS Professional, IBM Spectrum LSF, Open Cluster Scheduler (Grid Engine), Kubernetes, and the Flux Framework.

[ Summary of QRMI Workload Manager Integrations ]
Workload ManagerIntegration MechanismResource Abstraction & Availability Handling
• Slurm• SPANK Plugin framework• Uses Generic Resources (GRES) and Dynamic Licenses to align QPU availability with node execution.
• PBS Professional• Server & execution hooks• Uses custom resources and server_dyn_res scripts to check QPU readiness during scheduling.
• IBM Spectrum LSF• jobstarter and postexec hooks• Maps QPUs via External Load Information Managers (ELIM) running periodic status checks.
• Open Cluster Scheduler• Queue prolog/epilog & Load Sensors• Employs custom string and numeric complexes with Load Sensors (e.g., Warden) for slot tracking.
• Kubernetes• Custom Operator & CRDs• Uses QuantumResource and QuantumResourceClaim CRDs with job suspension until claims bind.
• Flux Framework• Fluxion graph-based scheduler• Models QPUs as native nodes in the resource graph and uses Fluence sidecars to monitor queue depth.

Integrating heterogeneous QPU hardware into classical HPC data centers presents abstraction and scheduling challenges due to vendor-specific APIs, dynamic calibration windows, and queue latency. QRMI decouples application logic and batch schedulers from hardware APIs through a unified middleware layer. The integration enforces a standardized three-step job lifecycle across all supported schedulers: