Story (Required)

With the completion of RHDHPAI-228, the investigation into the feasibility of taking a RHDH config file and passing it to the road-core container is complete. This issue is the implementation side responsible for making the necessary changes to facilitate this feature.

The RHDH config file can contain information related to databases as well as LLM servers (via Lightspeed). By passing this configuration file to the road-core container and having road-core ingest the data to include it alongside the required road-core config file we can avoid having to repeat ourselves in multiple config files.

As part of the prior investigation I was able to write-out a dirty solution for LLM servers being read and that can be used as a starting point for this issue. The proof-of-concept solution I came up with does not include any unit tests or handling for other fields (such as databases), and simply proves how we can facilitate the interaction between the two services. You will need to extend it to include all possible configurations that road-core can take from the RHDH config file.

You can reference the proof-of-concept solution in this Google Doc: https://docs.google.com/document/d/1ywl3vH8WAWuaxCMFd_8bivRnFFgRGjwrZs3wBAB-RwM/edit?usp=sharing

This issue will also include updating any necessary documentation for pre-existing/manual installations.

Background (Required)

<Describes the context or background related to this story>

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Required)

• RHDH config file can be passed to road-core container and road-core handles the data and loads it into the necessary objects.

<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