-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
5
-
False
-
-
False
-
-
-
Sprint 11, Sprint 12, Sprint 13, Sprint 14, Sprint 15, Sprint 16
-
6
As part of the spike https://issues.redhat.com/browse/OSPRH-15230 it was decided that OpenStack Lightspeed will reuse the already existing "openstack" operator for OpenShift.
Now we need to integrate the new container containing the OpenStack/RHOSO RAG image into the existing "openstack" operator so it can be deployed and configured correctly.
Configuration:
The multiple RAG feature for OpenShift Lightspeed will be released on the version 0.3.4 according to it's developers, until then, Haoyu Sun has provided a catalog that can be used for our tests:
- Create a file called ols-catalog.yaml with the following contents:
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
name: lightspeed-operator-catalog
namespace: openshift-marketplace
spec:
displayName: OpenShift Lightspeed Operator
sourceType: grpc
image: docker.io/raptorsun/lightspeed-catalog:0.33.1
updateStrategy:
registryPoll:
interval: 10m
- Apply this file using oc apply -f:
oc apply -f ols-catalog.yaml
Once that's done, you can install the new Lightspeed operator via OperatorsHub.
- Apart from the normal configuration for Lightspeed (e.g creating the secret file, adding the extra certificate if needed etc...) below is a snippet of how to plug multiple RAGs in the OLSConfig ConfigMap:
apiVersion: ols.openshift.io/v1alpha1
kind: OLSConfig
metadata:
name: cluster
...
ols:
introspectionEnabled: true
rag:
- image: quay.io/...:latest
indexPath: /rag/vector_db
indexID: vector_db_index0
- image: quay.io/...:latest
indexPath: /rag/vector_db
indexID: vector_db_index1
Note that we still have the problem with the "question validator prompt" that will be addressed by https://issues.redhat.com/browse/OSPRH-16233
- depends on
-
OSPRH-16666 Include RHOSO RAG container into the product
-
- Refinement
-
- is depended on by
-
OSPRH-18800 Add OpenStack Lightspeed into install_yamls
-
- Backlog
-
- links to