Loading...

XML

Word

Printable

Epic Name:
Migrate backend implementation to use upstream ROAD chat framework
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Status:
Done
Feature Link:
RHDHPLAN-39 - RHDH Lightspeed - Incorporate RHDH specific knowledge in responses [RAG]
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Intelligence Requested:
Market:

Epic Goal

Migrate the existing lightspeed backend plugin implementation to use the upstream ROAD framework https://github.com/road-core/service
This issue includes:
- Replace our existing chat functions backend with the road-core service implementation
- Maintain a backend proxy for UI to interact with the road-core service
- Creation of the container image that runs the road-core service (will be done as part to the upstream road-core service project)
- Stood up the sidecar container for the road-core service as part of the RHDH plugin support (some changes on RHDH side may be needed)
- Any customization need on the road-core service, e.g. authentication, pluggable RAG, configurable database for chat persistence storage, etc., should be considered to be implemented on the upstream directly or provide extension points on the upstream to allow customization by our lightspeed plugin usage whenever is possible.

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
...

Acceptance criteria are met
Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
User Journey automation is delivered
Support and SRE teams are provided with enough skills to support the feature in production environment

is cloned by

RHIDP-10186 RAG support in RHDH lightspeed