Story (Required)

As a user of the AI RHDH Installer trying to have a easy to use interface, I want to run and configure as few commands + settings as possible when setting up my environment.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

• The current AI RHDH Installer is a combination of a bunch of Bash scripts, rather than add model catalog bridge integration into the AI RHDH Installer we should look into wrapping the integration into a Go CLI
• This CLI can be extended in the future to easily incorporate new use-cases
  • E.g. Operator profiles, local deployment, etc
• Use a target flavour to configure model catalog bridge integration

Out of scope

• Any investigation work for the chosen RHDH flavor / profile to be used
• Investigation migration of AI RHDH installer to use this CLI tool (RHDHPAI-1069)
• Investigation into the utilization of GitOps resources for the installations

Approach (Required)

• Determine what are the model catalog bridge needs under a RHDH installation for a complete configuration
• Design the layout of packages / functions to be created
• Design the commands the user will use to directly interact with the setup
  • Updating the existing setup to add model bridge integrations

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 RHDHPAI team only)
R&D label required (Filled by RHDHPAI 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