Search federation across multiple Bailo instances

[ARADDCC002]

This feature adds the ability for a user to be able to include models from other Bailo instances when searching on the Bailo Marketplace.

Overview

Having the ability to discover and share models across different running instances of Bailo will help boost collaboration between different groups or organisations. Essentially, when setting up an instance of Bailo, admins will be given a choice to configure a list of additional instances of Bailo to share models with, which can be viewed on the Marketplace assuming that end users turn on the appropriate filter.

For example, if Instance A holds 10 models, and instance B holds 5, then if the user decides to turn the instance sharing filter on, they will see 15 models when they query for all available models.

Required Changes

Configuration

Each additional instance will have a number of properties that will need to be configured:

• Remote registry
• Base URL
• Location/Label
• User credentials
• Proxy address
• Proxy auth

Using this information for any additional instances, we should be able to retrieve a list of models based on the query that's sent.

Frontend Changes

• Add a new filter to the left-hand side that toggles on model sharing.
• Add a new label/tag to any models that appear in the marketplace so that it's clear if the model is from the instance the user is using, or one of any additional instances.

Backend Changes

• Update any model query API end points with a new filter that allows users to also query linked instances.
• New property on ModelSearchResult called "location" to store where the model came from (if it came from an additional instance.

Things to Consider

• Models hosted on other instances will only be read-only to begin with, unless clicking a remote hosted model takes you to that instance of Bailo instead.
• Consider what happens if two linked instances of Bailo are running different versions.
• Cache other instance results to reduce API delays due to expanded search.
• Handle duplicate names - decide if we want to:
  • Show duplicates
  • Remove duplicates
  • Prioritise local instance duplicates over remote

Future Improvements

It's likely that we won't add all features on day one. In the future, models hosted on remote instances should be able to be transferred from one instance to another. From a user perpsective, this should just be a single button press on the UI, but this will need a big backend change.