• Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • HAS Sprint 2266

      Story (Required)

      As a consumer of the AI software templates in https://github.com/redhat-ai-dev/ai-lab-template, I want to have my applications deployed to OpenShift AI. I should be presented with an option to deploy to OpenShift AI, and when selected, an OpenShift AI workbench should be created in the workspace of my choosing, with the source repository cloned within it.

       

      Background (Required)

      As part of DEVHAS-691, we determined the set of resources required to deploy to RHOAI. In this issue, we will add those resources to the software templates, as well as providing an option within the software templates to deploy to RHOAI.

      The software templates should also run a PipelinRun that detects when the workbench has started, and git clones the sample repository within the workbench.

      Out of scope

      • Running the application within the workbench (requires user intervention)
      • Deploying model servers via a model serving runtime or deploying the app through data science (see DEVHAS-673)

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

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

      Acceptance Criteria (Required)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      documentation updates (design docs, release notes etc)
      demo needed
      SOP required
      education module update (Filled by DEVHAS team only)
      R&D label required (Filled by DEVHAS team only)

      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

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

                Created:
                Updated:
                Resolved: