-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create a remote spawner with load-balancing capability #137
Comments
From a securing things point of view it would be good if:
https://hub.docker.com/r/jupyterhub/singleuser/ |
Related discussion from riot (from early February)
|
The spawners select the command to spawn from the Jupyterhub configuration which we have modified to get Jupyterhub to run our UI Server: cylc-uiserver/jupyterhub_config.py Line 36 in 831a528
The spawners load this command from the config directly (rather than having it passed through from the hub): For multi-user setups I think we will advise running the Hub under a special "cylc" user account with a limited subset of Note1: Currently the hub is launched with the Note2: We will want to make the "base" config we provide in this repository overridable in some way as there are some settings in there that sites (and possibly users) may wish to fiddle (e.g. there will be a config for setting the scan interval). |
Running jupyterhub with sudo-spawner isn't especially difficult. But you do have to ensure sudospawner-singleuser becomes:
and jupyterhub_config.py is:
and the sudoers changes is as advised in https://jupyterhub.readthedocs.io/en/stable/reference/config-sudo.html |
[discussed at CylcCon2020]
We want the Cylc Hub to be able to start UI Servers on any one of a group of hosts.
There is already [at least one] JupyterHub spawner which is able to start servers on remote hosts, the remote spawner.
We would like to add basic load-balancing to this. Cylc has load-balancing built-in, see the
cylc.flow.host_select
module.The idea is to try and build a new JupyterHub spawner which handles load balancing to work out where to start the server, then uses the configured spawner (e.g. the remote spawner) to actually start the server.
This would give sites a lot of flexibility with which spawners they install.
As, depending on the nature of the installation this spawner may be running as a privileged user the code should be kept to a minimum.
The text was updated successfully, but these errors were encountered: