Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ChatQnA demo yaml files integration between GMC and Oneclick #72

Merged
merged 8 commits into from
Jun 5, 2024
Merged
Show file tree
Hide file tree
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# Copyright (C) 2024 Intel Corporation
# SPDX-License-Identifier: Apache-2.0


---
apiVersion: v1
kind: Service
metadata:
Expand All @@ -27,7 +29,7 @@ spec:
labels:
app: router-service
spec:
serviceAccountName: gmc-service-sa
serviceAccountName: default
containers:
- name: router-server
image: zhlsunshine/gmcrouter:latest
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ rules:
resources:
- services
- secrets
- configmaps
verbs:
- create
- delete
Expand Down
39 changes: 0 additions & 39 deletions microservices-connector/config/samples/chatQnA.yaml

This file was deleted.

115 changes: 0 additions & 115 deletions microservices-connector/config/samples/chatQnA_v2.yaml
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's delete the old one and make this chatQnA.yaml, what do you say?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we will need two version: (one for gaudi, and one for xeon). for current one, Let's call it chatQnA-xeon.yaml

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we not put the yaml in GenAIExamples? Or are you thinking of a copy here for completeness. Is it possible instead to give a link to a file in another sub-project so we do not run into the issue of keeping things in sync?

This file was deleted.

71 changes: 71 additions & 0 deletions microservices-connector/config/samples/chatQnA_xeon.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,71 @@
# Copyright (C) 2024 Intel Corporation
# SPDX-License-Identifier: Apache-2.0

apiVersion: gmc.opea.io/v1alpha3
kind: GMConnector
metadata:
labels:
app.kubernetes.io/name: gmconnector
app.kubernetes.io/managed-by: kustomize
name: chatqa
namespace: chatqa
spec:
routerConfig:
name: router
nameSpace: chatqa
serviceName: router-service
nodes:
root:
routerType: Sequence
steps:
- name: Embedding
internalService:
nameSpace: chatqa
serviceName: embedding-svc
config:
endpoint: /v1/embeddings
- name: TeiEmbedding
internalService:
nameSpace: chatqa
serviceName: tei-embedding-svc
isDownstreamService: true
- name: Retriever
data: $response
internalService:
nameSpace: chatqa
serviceName: retriever-svc
config:
endpoint: /v1/retrieval
- name: VectorDB
internalService:
nameSpace: chatqa
serviceName: redis-vector-db
isDownstreamService: true
- name: Reranking
data: $response
internalService:
nameSpace: chatqa
serviceName: reranking-svc
config:
endpoint: /v1/reranking
- name: TeiReranking
internalService:
nameSpace: chatqa
serviceName: tei-reranking-svc
config:
endpoint: /rerank
isDownstreamService: true
- name: Llm
data: $response
internalService:
nameSpace: chatqa
serviceName: llm-svc
config:
endpoint: /v1/chat/completions
- name: Tgi
internalService:
nameSpace: chatqa
serviceName: tgi-svc
config:
endpoint: /generate
isDownstreamService: true

This file was deleted.

Loading
Loading