3 ms·
Give us some details about your setup. Are you running JH on the cloud somewhere? Or is this running on a single box at VT? We’ve got JH running on a Kube clust
by julienchastang 7y ago
Give us some details about your setup. Are you running JH on the cloud somewhere? Or is this running on a single box at VT? We’ve got JH running on a Kube cluster with persistent storage on the NSF Jetstream cloud [1] (which you could qualify for free resources being from VT) . This set up should theoretically address the scalability concerns you are having. See the work Andrea Zonca and I have been doing [2, 3, 4, 5]. Contact me for additional details.
[1] https://jetstream-cloud.org/ https://jetstream-cloud.org/
[2] https://zonca.github.io/2018/09/kubernetes-jetstream-kubespray.html https://zonca.github.io/2018/09/kubernetes-jetstream-kubespr...
[3] https://zonca.github.io/2018/09/kubernetes-jetstream-kubespray-explore.html https://zonca.github.io/2018/09/kubernetes-jetstream-kubespr...
[4] https://zonca.github.io/2018/09/kubernetes-jetstream-kubespray-jupyterhub.html https://zonca.github.io/2018/09/kubernetes-jetstream-kubespr...
[5] https://github.com/Unidata/xsede-jetstream/blob/master/vms/jupyter/readme.md https://github.com/Unidata/xsede-jetstream/blob/master/vms/j...
- acbart 7y agoI'm not as up on the details as you'd probably want, but my understanding is that we're running it on a virtual server with a nice chunk of RAM and CPU locally at VT. I don't think we want to be at all reliant on external servers - this is FERPA protected data. Plus, the long term goal was to find a solution that other schools could adopt without being an R1.