We have it setup at work, as an alternative way to use our HPC resource compared to the traditional Linux shell + slurm usage. User goes with the web browser t

We have it setup at work, as an alternative way to use our HPC resource compared to the traditional Linux shell + slurm usage. User goes with the web browser to our jupyterhub URL, logs in with our usual credentials, selects a job type (amount of memory and max duration), and jupyterhub takes care of launching a jupyter kernel as a slurm batch job on a compute node in the cluster, and proxies http I/O via the jupyterhub node to the user web browser. In the jupyter notebook, users have access to the same cluster filesystems as if she would login traditionally via ssh.