Task Description (Required)

on the RHOAI side

So Kubeflow Model Registry is much more "un-opinionated" than RHDH AI on what bits of information to always collect for a model.  Instead they have several layers of labels and custom properties definable at the Registered Model, Model Version, and Model Artifact API types.

Now, RHOAI also will be providing a "model catalog" UI that is somewhat analogous to a IBM/RH centric HuggingFace, comprised of mostly IBM / NeuralMagic LLMs, where from the ODH Model Catalog panels, you'll be able to transfer models from the Model Catalog to the Model Registry.

The RHOAI Model Catalog is a bit more prescriptive wrt specific bits of metadata, and they are mapping those bits to various model registry custom properties.  The current version of that mapping they have provided to us is at https://docs.google.com/document/d/118D_cvFDKleBweR52x4y3o4U3z6Xwy4yID1a5c2fX28/edit?pli=1&tab=t.0 

We are still in discussions with RHOAI on items like their short and long term plans.  For example, they are looking at providing a REST API at some point.  They currently are storing the catalog in a ConfigMap, but they have already warned is that will be going away, and really don't want us parsing that.  Also, still  somewhat TBD if the names of the model registry custom properties devised for summit will change or not after summit.

We are driving those conversations in slack, via RHOAI RFEs, and our weekly sync calls.

on the RHDH side

in the interim for summit, we through a combination of the custom properties RHOAI defines at https://docs.google.com/document/d/118D_cvFDKleBweR52x4y3o4U3z6Xwy4yID1a5c2fX28/edit?pli=1&tab=t.0 plus any custom properties we document, we need to proscribe to consumers of the model catalog bridge:

• any AI platform engineers that register models via the RHOAI/ODH model registry UI
• any AI platform engineers responsible for the RHDH model catalog
• any UI built on the RHDHPAI side for consuming the RHDHAPAI model catalog produced by the model catalog bridge

which custom property k/v pairs will be mapped to the different fields in our new model catalog json schema over at https://github.com/redhat-ai-dev/model-catalog-bridge/blob/main/schema/model-catalog.schema.json 

Once we decide on the names of the custom properties for those various fields, update the code to us those mappings

NOTE: owner and lifecycle are special cases of the mapping, given their prior existence and specialized meaning in backstage.  The mgmt of that is tracked for summit by https://issues.redhat.com/browse/RHDHPAI-661 

Desired Outcomes

• Code changes made to model-catalog repo
• Mappings opened under https://issues.redhat.com/browse/RHDHPAI-614