-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
Task Description (Required)
<Task description>
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
Acceptance Criteria
- RHDH config file can be passed to road-core container and road-core handles the data and loads it into the necessary objects.
- relates to
-
RHIDP-10550 Spike: Investigate adopt lightspeed plugin configuration in road-core configuration file
-
- Closed
-