slac-lcls/jhub2

LCLS Jupyterhub deployment

jhub2's Issues

Stopping a server is not terminating the users jupyter-labhub process

Using Jupyterlab the users jupyter-labhub process (on a psana machine) is not terminate. The kernels are.
The hub uses (via ssh) a SIGTERM to kill the users processes but the jupyter-labhub doesn't exist as it get stuck
in closing sockets.
Not sure if this also happens for classical notebooks.

Resolve psana name before ssh to server

Currently the ssh spawner use the psana load balanced name. Part of the ssh command is to print the hostname
ti find the proper server name. If something goes wrong we don't know which host the spawner tried.
A possible alternative would be that the spawner is resolving psana to a hostname before the ssh. If something goes wrong the spawner can print which host was tried.

Allow easier way to set JUPYTERLAB_DIR or conda env

Hi,

it would be nice if there was an easy way to set JUPYTERLAB_DIR or the conda environment the jupyterlab will start in. This would allow installation of labextensions such as the git extension or ipywidgets for interactive plotting.

The current implenentation makes sure not to run a .bashrc before starting the jupyterlab which makes it difficult to make changes to the environment (still possible, but much more ugly than it could be).
A nicer way could be to try to source a .jhubrc if it exists at https://github.com/slac-lcls/jhub2/blob/master/sshspawner.py#L64.

Thanks,
Felix