Uploaded image for project: 'Red Hat Enterprise Linux AI'
  1. Red Hat Enterprise Linux AI
  2. RHELAI-2268

product-independent accelerator base images

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Wheel building
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected

      Feature Overview (mandatory - Complete while in New status)

      The AI Platform Core Components (AIPCC) team should provide base images with accelerator libraries pre-installed for product teams to use to build application and bootc images. This will ensure that all of our products use the same accelerator libraries compatible with the wheel artifacts we build, and that application and bootc images delivered together are compatible.

      Goals (mandatory - Complete while in New status)

      • Separate the accelerator-specific parts of the images from the application part so that the accelerator parts can be reused.
      • Define a separation of responsibility for the different image layers.
      • Pick a versioning scheme for the base images.

      Requirements (mandatory -_ Complete while in Refinement status):
      A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

      Requirement Notes isMVP?
      Build accelerator images to be used as base images for RHEL AI instructlab and bootc images    
      Separate the base image versions to the builder image versions from RHELAI-1893 so that they each have their own versioning scheme. We could, for example, use the accelerator library version for the base image version.    
      It should be possible to tell at image build time whether a collection of wheels was built using the same base image that it is being installed into, and for the installation script in the wheel collection to fail if the base images are not the same. (We could try to be smarter about checking for compatibility, but that is not necessary.)    
      It should be possible to tell at image build time or at runtime whether the base images version for the bootc image and the application image are the same and to fail to start the application if they are not. It would be better if we could do that check when building the bootc image, but that is not a hard requirement.    

       

      Done - Acceptance Criteria (mandatory - Complete while in Refinement status):

      A RHEL AI GA release is constructed using the new base images.

      Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):

      As an application developer, I want to be able to build images that work with our supported accelerators, without having to keep those image definitions in sync with the other components myself.

      Out of Scope {}{}(Initial completion while in Refinement status):

      We will not provide these images directly to customers in this iteration of the work.

      Documentation Considerations {}{}(Initial completion while in Refinement status):
      We will provide internal documentation for consuming the images.

      Questions to Answer {}{}(Initial completion while in Refinement status):
      Include a list of refinement / architectural questions that may need to be answered before coding can begin.
      https://docs.google.com/document/d/1WUeBieJL-Ws51ImbKowHVsobeDnyj1NRrvvAPRifrtc/edit?tab=t.0

      Background and Strategic Fit (Initial completion while in Refinement status):
      Provide any additional context is needed to frame the feature.
      <your text here>

      Customer Considerations {}{}(Initial completion while in Refinement status):
      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
      <your text here>

      Team Sign Off (Completion while in Planning status)

      • All required Epics (known at the time) are linked to the this Feature
      • All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
      • Add - Reviewers name, Team Name
      • Acceptance == Feature as "Ready" - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
      • Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone
      Reviewed By Team Name Accepted Notes
             
             
             
             

       

      • ...

              cheimes@redhat.com Christian Heimes
              dhellman@redhat.com Doug Hellmann
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: