Epic Goal

• • • We have a number of AI software templates under https://github.com/redhat-ai-dev/ai-lab-template. Those templates requires long-term maintenance to ensure that the sample and their corresponding resources are up-to-date, e.g. free of security vulnerability and using recent models.

Why is this important?

• The software templates provides examples on the best practices for users on running applications and model servers. It is important that the samples are in good shape and also the resources are free of security vulnerabilities.

Scenarios

We will cover the long-term maintenance of the software templates by:

1. Ensure the resources in the template is up-to-date, including
   1. The applications used by the templates are updated to the most recent versions, sync with the Podman desktop ai-extensions if originated from it if necessary 
   2. Model server, containers, and source code are updated automatically, e.g. using renovate, to ensure the latest security patches are applied.
   3. A recent version of the model and model server are used
2. Docs updates
   1. Update the techdocs of the software templates to tailor the information for the specific application in the selection card
   2. Update each entry of software template to include more information that helps users to choose and use the software template, e.g. purpose, usage, model information, and model server information, etc.

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment