Story (Required)

As a PE, I can point the catalog plugin to a remote server, and have the remote server push new/updated models/model servers to it. 

As an AI developer, I can access up to date and newly discovered models and model servers in RHDH

Background (Required)

As part of the initial investigation into catalog extensions in Backstage (RHDHPAI-505 and RHDHPAI-506), we found that using both entity providers and custom processors will allow for the most flexible range of operations needed on the catalog. 

The model catalog custom processor will allow for the model catalog plugin to ingest newly discovered model catalog from the Model Catalog Bridge, while also allowing for existing catalog entities to be updated.

Out of scope

• Model Catalog Bridge implementation (see RHDHPAI-606).

Approach (Required)

https://github.com/redhat-ai-dev/rhdh-plugins/tree/main/workspaces/rhdh-ai provides a prototype implementation of the custom processor

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