-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
Task Description (Required)
The model catalog described in RHDP-1014 (see also https://docs.google.com/document/d/1bp_zvNEsxkz1-Im6sg6_1C78wcKPMDPJHPU3LcItwVY/edit), may make use of the catalog API in Backstage to define a custom catalog type for Models.
As a result, the Backstage catalog model API should be investigated:
- How to define custom types
- How to create entries in the catalog
- How to extend the catalog model
https://backstage.io/docs/features/software-catalog/extending-the-model/#adding-a-new-kind contains Backstage's documentation on extending the catalog API, and would be a good starting point
Burr also created a demo of a PoC model catalog in RHDH, and his model catalog yaml can be found here: https://github.com/burrsutter/model-catalog/blob/main/ai_models.yaml
Change Request
<Select which item is being changed>
[ ] Add New Tokens
[ ] Rotate Tokens
[ ] Remove Tokens
[ ] Others: (specify)
Environment
<Select which environment the change is being made on. If both, open a separate issue so changes are tracked in each environment>
[ ] Stage OR
[ ] Prod
Backout Plan
<State what steps are needed to roll back in case something goes wrong>
Downtime
<Is there any downtime for these changes? If so, for how long>
Risk Level
<How risky is this change?>
Testing
<How are changes verified?>
Communication
<How are service owners or consumers notified of these changes?>