Story (Required)

As a AI platform engineer trying to inject AI model catalog information into RHDH I want the catalog-info.yaml produced from the CLI and Bridge to go under model-catalog-template validation

Background (Required)

During review of https://github.com/redhat-ai-dev/model-catalog-template/pull/2 johnmcollier and gmontero@redhat.com agreed that long term it would be great if that test framework in that repo could be structured in such a way that the parts that could be reused by other repositories that produced catalog-info.yaml output, where the validated the model catalog reqs against the data they produced.

We are opening this placeholder for this, where we will officially refine oncel model-catalog-templates is structured and ready for such reuse.

Out of scope

Approach (Required)

For now, we are waiting  https://issues.redhat.com/browse/RHDHPAI-538  is one and a clear recipe is in place for reusing the test framework in model-catalog-template

Dependencies

  https://issues.redhat.com/browse/RHDHPAI-538  

Use of git submodules or npm to get the model-catalog-template framework as a dependency should be determined

Acceptance Criteria (Required)

For now, we are waiting  https://issues.redhat.com/browse/RHDHPAI-538  is one and a clear recipe is in place for reusing the test framework in model-catalog-template

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