Login Sign up

Wednesday Oct. 14, 2020, 4:45 p.m.–Oct. 14, 2020, 5 p.m. in Enterprise Jupyter Infrastructure

IBM Quantum Experience Notebooks. Serving JupyterHub at scale for the Quantum Computing Community

Juan Cruz-Benito

Audience level:
Intermediate

Brief Summary

Since IBM put online the first cloud accessible quantum computer in 2016, there has been a surge of interest in accessing these systems. Among the different tools that IBM Quantum Experience provides to the quantum computing community, the cloud-based Jupyter Notebooks are a core part. This talk introduces how we enable ~240,000 users to use these notebooks via a JupyterHub deployed in Kubernetes.

Outline

How can we enable a complete online experience for IBM’s Quantum Experience (https://quantum-computing.ibm.com/) users to access all of our quantum devices and software libraries effortlessly? That question fired a research and engineering process at the core of the IBM Quantum cloud software team to provision, and integrate with our software, a JupyterHub deployment on Kubernetes available for ~240000 enrolled users. In this talk, we discuss how we have integrated JupyterHub with our already existing IBM Quantum Experience platform and how we are leveraging the power of the JupyterHub to provide the best experience to the users. Among other aspects, during the presentation, we cover how we have solved, and we're still addressing issues related to custom authentication with our platform, performance, look & feel, permanent storage per user, user environment tailoring, provision of pre-installed software like Qiskit (https://qiskit.org/) and other quantum-related software and tutorials, automation of the selection of custom hardware resources for different users, how we deal with malicious users, or how we handle ~800 concurrent user servers during our last May 4th challenge (https://www.ibm.com/blogs/research/2020/05/quantum-challenge-results/). To conclude the presentation, we will share some final reflections of our experience and plans we have to continue developing our platform and contributing to the Jupyter ecosystem.