Service

When we first committed to offer Jetstream2 support at 2i2c, Jetstream2, Magnum, OpenStack, ClusterAPI were all new concepts that we hadn’t used at 2i2c before. And although the initial exercise of reading about each of them independently was confusing, learning how they actually glued together was the key.

These describe the major service improvements that we rolled out in Q1 2025. See this blog post describing our product enhancement goals in Q1 2025 for the targets we intended to hit this quarter.

Building upon our previous work developing per-user storage quotas for our AWS infrastructure, we are pleased to announce that this feature is now available for GCP-hosted hubs! To provide this feature on this vendor, we have updated our infrastructure provisioning system to create persistent disks, and enable automatic backups of the disk for disaster recovery purposes.

Project Pythia and the “Jupyter notebook obsolescence” problem # Project Pythia provides educational resources for essential software tools that enable open, reproducible and scalable geoscience, such as the Pangeo stack of packages (Xarray, Dask, Jupyter).

Last December I had an opportunity to discuss the current and future state of the open publishing ecosystem at a workshop hosted by HHMI1. While 2i2c doesn’t primarily focus on “publishing” workflows, we do support communities on a journey that often leads to publishing, and we make choices about technology in our community hub platform that can support different kinds of publishing outcomes.

2i2c are pleased to announce the development and deployment of automated backups of home directories on GCP-hosted hubs! We have developed the gcp-filestore-backups project that regularly creates backups of JupyterHub home directories for disaster recovery purposes.

When sharing a storage disk between users, as is usually the case in a JupyterHub deployment, it is important to put in guardrails so that one user cannot eat up the whole storage capacity from the rest of the users.

We are excited to announce that all 2i2c hubs now run JupyterHub 5.0! This is an upgrade that brings some exciting new features and improvements. Some of the highlights include:

2i2c is pleased to announce the frx-challenges project, a new open source tool to help communities host data challenges on shared infrastructure: 2i2c-org/frx-challenges This project aims to make it easier for administrators to provide a service that enables users to submit code and data that are evaluated on secure infrastructure with access to private data and resources.

On most research oriented JupyterHub installations, users would like to customize their server (the environment, resources available, etc) after logging in. In Kubernetes based JupyterHub environments, a profile list provides this functionality.