Feature Overview:

The work in AIPCC-3511 will make the packages we build available to customers. We will only support those in "our base images". We need to produce those images and ensure that customers understand how to access them for creating their own model customization jobs.

We will also need to work with the workbench team to ensure their image, which starts with a jupyter notebook installed, can install packages from the index.

Product(s) associated:

RHOAI

Goals:
Provide high-level goal statement with user context and expected user outcome(s) for this Feature

• Provide base images for customers to build their own model customization images.
• Provide base images for the workbench team to use to make an image with a jupyter notebook.
• Ensure the images can easily access the correct package index by default, but that they can also point to a local mirror of that index for disconnected users.

Requirements:
A list of specific needs, capabilities, or objectives that a Feature must deliver.

Done - Acceptance Criteria:
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view

Use Cases - i.e. User Experience & Workflow:
Include use case diagrams, main success scenarios, alternative flow scenarios.

Out of Scope:
High-level list of items or personas that are out of scope.

Documentation Considerations :
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation.