Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-2211

Custom notebooks - phase 1

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • Custom notebooks - phase 1
    • False
    • False
    • Hide
      1. Verify ability to import custom NB images and have the images be available for selection in the UI in the same way as out-of-the-box NB images.
      2. Verify ability for user/admin to export custom NB images and store on a local system.
      3. Verify ability to create a new image from scratch by defining image components/packages and have the image be available for selection in the UI like OOTB NB images.
      4. Verify ability to create a new image using a different Python version like Python 3.9 and have the image be available for selection in the UI like OOTB NB images.
      5. Verify ability to create a new NB image from an existing RHODS NB image (either custom or OTTB) and have the image be available for selection in the UI like OOTB NB images.
      6. Verify ability to dynamically add/remove packages/components to/from an environment via the “modules” UI.
      7. Verify ability to access a tool in the UI to identify and verify dependencies for components/packages during the process of creating a new custom NB image.
      8. TBD: Verify ability to create a new custom image and have the image only be available for selection for the user that created the new image.
      Show
      Verify ability to import custom NB images and have the images be available for selection in the UI in the same way as out-of-the-box NB images. Verify ability for user/admin to export custom NB images and store on a local system. Verify ability to create a new image from scratch by defining image components/packages and have the image be available for selection in the UI like OOTB NB images. Verify ability to create a new image using a different Python version like Python 3.9 and have the image be available for selection in the UI like OOTB NB images. Verify ability to create a new NB image from an existing RHODS NB image (either custom or OTTB) and have the image be available for selection in the UI like OOTB NB images. Verify ability to dynamically add/remove packages/components to/from an environment via the “modules” UI. Verify ability to access a tool in the UI to identify and verify dependencies for components/packages during the process of creating a new custom NB image. TBD: Verify ability to create a new custom image and have the image only be available for selection for the user that created the new image.
    • Yes
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • No
    • Yes
    • None

      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: Admins must be able to bring in/import existing notebook images for use in RHODS. The system must enable users to bring in/import notebook images via the RHODS UI (eg. users should not have to edit config files such as YAML files). After import, the images should be available for selection in the UI like out-of-the-box images. Note: by default, imported images would be available for all cluster users.

      Use case: Organizations have existing notebook images they created for past data science projects. They want to use these images in RHODS.

      Details for req 1: https://docs.google.com/document/d/1nd_WayY7RB3H7SlqMNlq1LsiS17CnG8V5D6UNsnmIYU/edit

      7. P0: Admins must be able to export custom images & store on a local system.

      Notes:

      • This could be provided as part of standard OSD capabilities
      • The idea is to give users an option to store custom images they create in a separate location for backup purposes.

              Unassigned Unassigned
              jdemoss@redhat.com Jeff DeMoss
              Luca Giorgi Luca Giorgi
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: