Embed wrapspawner to allow selection of image

[gsemet]

Hello

How hard would it be to embed wrapspawner or similar in order to allow user selection of desired profile upon connection.
What I mean by "profile" is a predefined list of "image + cpu number + disk space + memory".

I imagine something like a dropbox where user can select for instance"small datascience notebook", "big memory datascience" or "Python training notebook", and so on, and it would launch the related image and cpu/memory request for kube.

[yuvipanda]

Thank you for opening this issue, @gsemet! I agree that it would be very useful to have!

I think adding something like jupyterhub/dockerspawner#219 to github.com/jupyterhub/kubespawner is a better fit! What do you think, @minrk?

[cam72cam]

I'd like to help out, even if that is just being a guinea pig on this ticket

[gsemet]

Isn’t it easier or better to integrate wrapperspawner in zero to jupyterhub or hack into kubespawner?

[gsemet]

@yuvipanda If I follow you proposal to hack into kubewrapper, I would like to propose the following change in kubewrapper:

• New option c.KubeSpawner.single_user_profile_list is added and take precedence over `singleuser_image_spec
• this option is a list of dictionnary of form:

{
    'display_name': 'Human Readable Profile Title',
    'image_spec': 'image/to_execute:label'
    'cpu_limit': cpu_limit,
    'cpu_guarantee': cpu_guarantee,
    'mem_limit': mem_limit,
    'mem_guarantee': mem_guarantee,
    'lifecycle_hooks': lifecycle_hooks,
    'volume_mounts': volume_mounts,
}

Note that lifecycle_hooks and volume_mounts can be superseeded in this configuration (I propose the following: if key is defined, no matter its value (None or set to a value), the setting is super seeded. If not set, the default value stays c.KubeSpawner.volume_mounts for example).

Or maybe we can be more agressive:

• the format is not defined (except the mandatory 'display_name'), and any KubeSpawner parameter can be superseeded in this data structure.

This would allow extension in the future, such as adding a logo (base64 or url or image id) to have a better looking profile selection (like the welcome panel in jupyterlab).

[minrk]

indeed, adding wrapperspawner support may be the best way to go.

[gsemet]

I have made a proposal in this PR: jupyterhub/kubespawner#137

[jgerardsimcock]

Has this functionality been merged into the z2jh deployment yet? If not and we want to implement this, what is the best way to approach this?

[minrk]

I think the kubespawner profiles are now in z2jh

[consideRatio]

Closed thanks to @gsemet's work on jupyterhub/kubespawner#137!