Skip to article frontmatterSkip to article content

Implement per-user home directory quotas for AWS-hosted hubs

Sub-issues
  • #4647 - [EPIC] [DevelopmentSeed partnership] Integrate jupyterhub-home-nfs helm chart into 2i2c infrastructure

  • #5002 - [EPIC] [devseed] Set up automated backups using EBS snapshots for our home directory Volumes in AWS

  • #5004 - [EPIC] [devseed] Set up alerting for an EBS volume getting close to full on AWS, and a runbook on how to resize it when needed

  • #5066 - [EPIC] Deploy jupyterhub-home-nfs to nmfs-openscapes

  • #5067 - Deploy jupyterhub-home-nfs to CryoCloud

  • #5285 - Set resource requests and limits on jupyterhub-nfs-home nfs-server pod

  • #5367 - Debug and Verify that EBS disk size alerts go through to Slack channel

  • #5403 - Enable alerting for all hubs we’ve rolled out jupyterhub-home-nfs to

  • #5424 - Enable automatic homedirs backups for all hubs we’ve rolled out jupyterhub-home-nfs to

  • #4869 - Write a blog post talking about the new home directory per-user quota functionality

  • #365 - [2025-01-29] Social media campaign – Enforcing per-user storage quotas with jupyterhub-home-nfs (2i2c-org/2i2c-org.github.io)

Participate in the issue: github.com/2i2c-org/infrastructure/issues/5010

This issue tracks rolling out ‘per user home directory quotas’ as an initiative within the product & services team.

Team


Status: Done

Back to: All Initiatives