Skip to content

StoragePolicy

Jump to bottom
Rob Nagler edited this page Nov 6, 2016 · 3 revisions

Disk Policy

Currently this policy only applies to JupyterHub. As of 10/7/2016, this is a proposal.

JupyterHub Storage

When login to JuypterHub, you "server" is a Docker container visible only to you. The container has three file systems:

  • / - The root file system is running off the local, shared 1TB SSD, which is not backed up or mirrored. It does not survive container restarts.

  • /home/vagrant/jupyter - The "root" directory for Jupyter file viewer. This is private to you, NFS mounted, mirrored, and backed up. NFS runs over a private 1gbps "backnet" to 7200RPM SATA.

  • /home/vagrant/tmp - Where you should store node-local temporary data. It is not backed up or mirrored. For now, it is on the root file system, but might move to a larger disk if we decide that makes sense.

This directory will not survive a system restart or a container update. You get direct access to the local SSD disk space on the blade, so IO is fast. If you generate useful files in this space, you need to copy them over to scratch.

  • /home/vagrant/scratch - where you should run jobs that require greater than 10GB of data. This is private to you, NFS mounted, mirrored, but not backed up. The pool is 8TB.
Clone this wiki locally