-
Notifications
You must be signed in to change notification settings - Fork 64
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
Configurator for environment customization #312
Comments
Mention that docker image names can be changed from the Configurator now Ref 2i2c-org/infrastructure#312
Hey @yuvipanda - what's the status of this one? It seems like it much progress has been made in the configurator but not sure if these boxes should be checked or not :-) |
@yuvipanda quick question coming to my mind when I looked into this issue. |
Great question, @damianavila!
Does this help, @damianavila? |
Yes, this helps... so if the configurator always takes precedence, you will only expose a subset of options preventing them to get more resources than it should take, right? I am thinking about how to prevent them from self-assigned more CPU and RAM than they should be self-provisioning... looking quickly into the configurator repo I see some schemas that should restrict what the admins can customize, am I right? Where that schema lives inside the pilot-hub repo? I see some schema here: https://github.com/2i2c-org/pilot-hubs/blob/master/hub-templates/base-hub/values.yaml#L126, is that the one I am should be looking at? |
@damianavila it was confusing for me too, so I opened #350 to try document that. It's brought up useful questions on what should be where. |
I believe that the configurator has been updated a few times since the last time this issue was updated - where are we now on functionality of the configurator? Can we update the tasks above to reflect the steps needed to finish this off? |
I have updated the items completed accordingly to these docs: https://pilot.2i2c.org/en/latest/admin/howto/configurator.html |
Yeah - I think we should treat the tasks in this issue as a kind of "beta release" of the configurator - they should capture major functionality that needs to be there but not necessarily everything we'd want the configurator to do |
We have this deployed, and further work on self-serve of JupyterHub config will now be tracked in https://2i2c.productboard.com/feature-board/7803674-product-ideas/features/25998745/detail |
Mention that docker image names can be changed from the Configurator now Ref 2i2c-org/infrastructure#312
Description
There are a bunch of config changes that can be made by hub admins without risk of bringing their own hub down in an unrecoverable way. Currently, they need to be made via PR to this repo, involving time from 2i2c engineers. This slows down hub admins, and takes up 2i2c engineer time.
We should make these 'self serve' instead, where admins can use a familiar GUI to make changes themselves. This GUI should be devoid of footguns, where admins can accidentally delete everything and lock themselves out.
To begin with, the configuration GUI should allow admins to:
Inspired in part by tljh-repo2docker (via @jptio)
Benefit
As a hub administrator, I want to change some settings without involving 2i2c engineers so that it can happen more quickly and without hassle.
Implementation
We can iterate in the https://github.com/yuvipanda/jupyterhub-configurator repository. Here's a preview of how it looks currently:
I want to have something minimal deployed functionally before end of march, and hopefully we can have a complete deployment before start of next NA academic semester.
Tasks to complete
The text was updated successfully, but these errors were encountered: