Epic brief: https://docs.google.com/document/d/1YB6vlcwF0mG61CawEaAEsrR4a_18-2xFKwGwe1Anw0I/edit?usp=sharing

RHODS provides several out-of-the-box notebook images that automatically include packages to make it easy for users to get started with common components. However, in many/most instances, users need a specific set of packages/libraries with specific versions depending on the projects. There are so many possible variations of these packages/libraries/versions that it’s not practical to provide out-of-the-box images to anticipate the various needs. Users do not want to have to rely on pip installs for all the packages/libraries on a regular basis because it’s time consuming, and it can be difficult to keep track of all the needed components. They are looking for a quick & easy way to start a notebook session with the components they need for a project. Oftentimes, there can be repeatable patterns for the necessary components rather than starting from scratch for every project.

Many times users need specific package/library versions for a project, and they need to ensure that the combinations of packages & versions will work together. This could be driven by the need to leverage existing code that was created using a specific package/library version. They want to avoid scenarios where the notebook won’t run successfully because of an incompatibility across different packages & versions.

Requirements:

1. P0: Users must be able to add & remove components/packages to/from an environment from a curated library directly via the UI.

Notes:

• Possible idea is to incorporate Guillaume’s module concept
• If applicable, UI should distinguish between “community” modules and Red Hat provided modules
• Red Hat doesn’t have to provide any modules

2. P0: Admins must be able to configure the module library - i.e. which modules are available for selection by users.