Epic Goal

Per kicking off in the Feb 10 Weekly Sync by mutual request we are booting up the next iteration (where the first was the fall of 2024) of collaboration between the RHDHPAI team and the RHOAI KubeFlow Model Registry, ODH based operator, and KServe Model serving teams in order to facilitate various integrations around the population of the RHDH Model Catalog

In correlation with the content of the parent feature, this epic will touch on elements of key features 1, 4, and 5.

Why is this important?

Both teams' Summit goals include integration with each other

Scenarios

1. As a consumer of the broad RH AI portfolio, I would like to see how model metadata can propagate from RHOAI/ODH/Kubeflow/Kserve to RHDH/Backstage
2. As a consumer of the broad AI portfolio, I would like to see what tools RH will provide to allow my platform engineers to as needed propagate model metadata from RHOAI/ODH/Kubeflow/Kserve to RHDH/Backstage

Acceptance Criteria (Mandatory)

• regularly scheduled meetings established as needed
• coordinated understanding/interlock on respective schedules
• understanding of respective requirements
• consistent pipeline that delivers installable versions of each product that leads to something we can point to and reference at summit
• POC's (with demos) as appropriate
• Linked/children stories for delivering portions of the bridge (both long running services in OCP as well as complimentary CLI ) that interact with our AI plugin and the RHOAI services

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
•