Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10150

Convert current AI templates to single template, with option to select sample

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • None
    • Convert current AI templates to single template
    • False
    • False
    • Done
    • 0% To Do, 0% In Progress, 100% Done

      Epic (Required)

      As a developer consuming AI software templates, I would like the choice to choose between samples, no samples, or a repository of my choosing, when importing templates into my catalog.

      Background (Required)

      We recently discussed on a call that it would be better to have a general AI template that allowed users to select their sample (e.g. Chatbot, Codegen, no sample, or BYO repo), and also choose their deployment target (e.g. OpenShift, Podman Desktop, OpenShift+RHOAI, etc), rather than the current set up, where the templates are duplicated per sample repo. This will also make it easier to allow the template to be created with no sample, or with a repo of the user's choosing.

      This won't preclude other templates from being added (e.g. DEVHAS-673), but this will allow us to streamline a number of templates into one

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

       

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Required)

      • Software template that allows the choosing of sample repositories (in addition to allowing: no repository, or a user selected repository)

      Done Checklist

      Code is completed, reviewed, documented and checked in
      Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      Continuous Delivery pipeline(s) is able to proceed with new code included
      Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
      Acceptance criteria are met
      If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well

              Unassigned Unassigned
              johnmcollier John Collier
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: