Story (Required)

Background (Required)

Currently, we store copies of any sample applications that we use in the software templates in https://github.com/redhat-ai-dev/ai-lab-samples/ which then get pulled into software templates via generate.sh (and copied once more).

We recently discussed maintenance for the various AI software template repositories (ai-lab-app, ai-lab-samples, and ai-lab-template), and decided that for the main branch of the software template, it would be fine to directly reference the Git repositories that the samples come from (e.g. https://github.com/containers/ai-lab-recipes/tree/main/recipes/natural_language_processing/chatbot), as we do not currently make any modifications to them.

However, this change is restricted to just the main branch, for releases of the software template, they will point to a fixed copy of the sample(s). So the release process (see DEVHAS-710) should cover updating the templates to reference a local copy.

Out of scope

• Updating release process to update references to the samples (see https://issues.redhat.com/browse/DEVHAS-710)

Approach (Required)

• See if our software templates can directly reference the two samples we currently use: https://github.com/containers/ai-lab-recipes/tree/main/recipes/natural_language_processing/chatbot and https://github.com/containers/ai-lab-recipes/tree/main/recipes/natural_language_processing/codegen
• If no issues occur, update references to the samples in our software templates, specifically: https://github.com/redhat-ai-dev/ai-lab-template/blob/main/templates/chatbot/template.yaml#L140 and https://github.com/redhat-ai-dev/ai-lab-template/blob/main/templates/codegen/template.yaml#L140
• (Optional, not sure if out of scope, can be done as part DEVHAS-710): Create script to replace references to the repository with a cloned local copy, as part of the release process

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