IBM has spent years laying the groundwork for a future where quantum and classical high-performance computing (HPC) systems work together to tackle problems neither computational paradigm can solve alone. Now, that future is becoming reality.<\/p>\n
Last year, at the Supercomputing 2024 conference in Atlanta, GA, we presented\u00a0our vision for quantum-centric supercomputing<\/a>\u00a0(QCSC), a computational paradigm that we believe will enable the first demonstrations of quantum advantage by the end of 2026. That vision included plans for integrating quantum resources with popular HPC resource management systems like Slurm, as well as proposals for three potential architectures to enable hybrid quantum-classical workflows at scale.\u00a0<\/p>\n Since then, we\u2019ve been working with our partners at research organizations like Rensselaer Polytechnic Institute (RPI), STFC Hartree Centre, Cleveland Clinic, Oak Ridge National Laboratory, and the quantum startup Pasqal to bring these plans to life\u2014building open-source tools that real-world HPC users and data center admins can start exploring today.<\/p>\n Explore the quantum spank plugins for Slurm on GitHub<\/a> These tools have already been put to the test in the real world through our collaboration with the team behind the AiMOS supercomputer at RPI\u2019s Future of Computing Institute<\/a>. Our partnership with RPI has been essential over the past year as we\u2019ve worked through multiple iterations of our quantum plugins for Slurm and quantum resource management interface.<\/p>\n The RPI team has allowed us to test multiple deployments with an active user base of students and postdocs, helped us explore different strategies for access management and resource allocation, and made invaluable contributions to\u00a0the arXiv paper<\/a>\u00a0describing our efforts.\u00a0Now, thanks to the integration of AiMOS with the Future of Computing Institute\u2019s on-prem IBM Quantum System One, RPI is home to the first QCSC environment ever deployed within the walls of a university.<\/p>\n “This is a major step toward the unification of classical and quantum computing workflows,\u201d said Christopher Carothers, Ph.D., chief scientist of RPI\u2019s Future of Computing Institute. \u201cIt was made possible in part by the collaborative efforts of students, faculty and other members of RPI\u2019s research community.\u201d<\/p>\n Our work on this project has taught us important lessons, brought us useful insights, and inspired strategic course corrections that are helping to shape the future of quantum-centric supercomputing. Below, we take a quick look at what we\u2019ve accomplished, and how our vision of quantum-centric supercomputing architectures has evolved since we first shared it last year.<\/p>\n Introducing quantum plugins for Slurm workload manager\u00a0<\/p>\n Last year, we offered a glimpse<\/a>\u00a0at how users might one day leverage workload management systems like\u00a0Slurm<\/a>\u00a0to implement hybrid quantum-classical workflows on a quantum-centric supercomputing architecture. In the months since, we\u2019ve worked with RPI, STFC Hartree Centre, and Pasqal to realize that vision with\u00a0a set\u00a0of open-source quantum plugins for Slurm. Workload managers like Slurm play a vital role in HPC workflows, taking care of resource management and job scheduling, so it\u2019s important that we provide plugins that allow them to incorporate quantum resources seamlessly.<\/p>\n We\u2019re focusing our initial efforts on Slurm because it is the most popular HPC workload manager in the world, and certainly the most popular among HPC users who also work with IBM quantum computers. For most of the research community, HPC is done through Slurm, and we\u2019re adopting that usage pattern to get as many researchers and developers exploring hybrid quantum + HPC workloads as we can. Over time, we hope to support similar initiatives for other resource managers so we can bring quantum to even more of the HPC community.<\/p>\n With the help of our partners, we\u2019ve built a set of quantum plugins for Slurm using the \u201cSlurm Plug-in Architecture for Node and job Kontrol\u201d or spank architecture. Integration to resource managers decouples quantum computational resource control and allocation from user code and creates a clear split of responsibilities between HPC data center administrators, HPC users, and HPC application code. Slurm\u2019s plugins architecture gives HPC datacenter administrators the ability to add new capabilities to the resource manager without interruption, simply by adding compiled files to the existing environment.<\/p>\n This approach allows us to give full operational control to administrators while maintaining maximum flexibility for users. The result is a familiar user experience for all personas in data centers. Administrators can track and control allocation of resources; researchers and developers use Qiskit in program code and allocate resources during job submission alongside classical CPU, memory and GPUs. To learn more about our quantum plugins for Slurm\u2014including details on the plugins\u2019 structure, flow, and general architecture\u2014be sure to read our detailed overview on the project GitHub repo, here<\/a>.<\/p>\n Developing a vendor-agnostic Quantum Resource Management Interface (QRMI)\u00a0<\/p>\n HPC users and data center admins can use our open-source quantum spank plugins to submit jobs incorporating quantum compute resources. However, the plugin itself doesn\u2019t directly manage the complexities of controlling the quantum resources, which can vary a great deal depending on hardware vendors and the specifics of individual hardware backends.<\/p>\n That\u2019s why, alongside our quantum plugins for Slurm, we\u2019ve also developed\u00a0QRMI, the quantum resource management interface.\u00a0QRMI essentially functions as a thin middleware layer that abstracts away the complexities of controlling the quantum resources of specific hardware backends. Rather than requiring the spank plugin to manage those complexities directly, QRMI exposes a set of simple APIs that allows the plugin to easily acquire or release hardware, run tasks, and monitor the state of quantum computational resources.<\/p>\n QRMI is written in the high-performance Rust programming language with APIs available in Rust, Python, and C to ensure you can easily integrate it into the computational environment of your choice. These three programming languages give us a foundation that allows us to integrate control over quantum resources to nearly any infrastructure system and framework you can imagine, whether that\u2019s resource managers, workflow orchestration tools, the monitoring stack, or something else.<\/p>\n Explore the QRMI project GitHub repository\u00a0here<\/a>\u00a0to learn more about how to install and use our QRMI implementation, and to see examples of the three APIs that are currently available.<\/p>\n Collaborating with RPI to refine our vision for QCSC architectures<\/p>\n In our Supercomputing 2024 blog last fall<\/a>,\u00a0we laid out three potential architectures for quantum-centric supercomputing:<\/p>\n Architecture 1:\u00a0Separates classical from quantum jobs. In the context of IBM quantum computers, quantum jobs are executions of the Qiskit primitives. Since then, we\u2019ve had the opportunity to test these architectures across multiple deployments with the team behind RPI\u2019s Future of Computing Institute, which is home to both the AiMOS supercomputer and an IBM Quantum System One. Led by Professor of Computer Science Christopher D. Carothers, the RPI team has been instrumental in helping us determine how to optimize system partitioning and access policies, administer storage and data flow between quantum and classical resources, manage dependencies, and optimize the user experience.\u00a0These developments will enable quantum-centric supercomputing researchers at RPI and other collaborating institutions to seamlessly transition to an integrated classical-quantum environment that will optimize computational workflows for key applications, such as electronic structure problems, energy-matter interactions, and more.<\/p>\n As our work developing QRMI and the spank plugins for Slurm in collaboration with RPI has progressed over the past year, we\u2019ve settled on architecture 2,\u00a0the hybrid model, as our strategy of choice. One of the benefits of this approach is that once your quantum-classical job starts running, it blocks off all resources required for the job\u2019s entire duration. We\u2019ve already begun to see the benefits of this strategy in research collaborations with\u00a0STFC Hartree Centre<\/a>, whose work with IBM under the Hartree National Centre for Digital Innovation Program<\/a> (HNCDI) highlights the potential for hybrid quantum + HPC workloads powered by our hybrid model QCSC architecture to enable near-term demonstrations of quantum advantage. HNCDI were recently recognized with an IEEE Distinguished Synergy Award<\/a> for their work driving quantum computing towards adoption.<\/p>\n To learn more about why we settled on the hybrid architecture described above, and to get a technical deep dive on our spank plugins and QRMI,\u00a0read our overview paper on arXiv<\/a>. Please note that, much like the contents of our\u00a0quantum plugins for Slurm<\/a>\u00a0and\u00a0QRMI<\/a>\u00a0GitHub repositories, this paper is very much still a work in progress. This is a collaborative effort involving multiple research organizations, so we invite you to check back in the weeks and months ahead to see how it evolves, and we hope you\u2019ll consider joining our collaboration to help shape the future of quantum-centric supercomputing.<\/p>\n Head to the GitHub repos linked above to start exploring the QCSC software tools that are available today and see how you can contribute.<\/p>\n","protected":false},"excerpt":{"rendered":"IBM has spent years laying the groundwork for a future where quantum and classical high-performance computing (HPC) systems…\n","protected":false},"author":2,"featured_media":145205,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[64,63,257,105],"class_list":{"0":"post-145204","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-computing","8":"tag-au","9":"tag-australia","10":"tag-computing","11":"tag-technology"},"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/posts\/145204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/comments?post=145204"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/posts\/145204\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/media\/145205"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/media?parent=145204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/categories?post=145204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/au\/wp-json\/wp\/v2\/tags?post=145204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Explore the Quantum Resource Management Interface on GitHub<\/a><\/p>\n
\nArchitecture 2:\u00a0A hybrid model where we treat quantum resources like any other resource, and we treat all jobs in the integrated system as hybrid jobs\u2014differentiating and allocating based on the type of resource required by each job.
\nArchitecture 3:\u00a0A mixed model that attempts to leverage the benefits of both architecture 1 and architecture 2, while mitigating their drawbacks through more complex configuration and development.\u00a0<\/p>\n