Replies: 4 comments 1 reply
-
|
hi @rootfs , |
Beta Was this translation helpful? Give feedback.
-
|
@noalimoy - Could you please add you idea that we discusses earlier today? I think it's related to the last point that mentioned by @rootfs (Deployment point) |
Beta Was this translation helpful? Give feedback.
-
|
@senanz @noalimoy that's great! Intuitively, we want to have a chatbot-like UX that for a user input, the model will generate the config file. The workload can be improved to have an api service too so that the init container can use the api service to grab the config. The tuning and config verification will be in the heart of this project. If you can take these into action, that'll be great! |
Beta Was this translation helpful? Give feedback.
-
|
Hey, before starting the POC, I need some clarification (for anyone who would like to be involved). @senanz @rootfs @noalimoy 1. Use Case & User WorkflowPrimary Use Case - When is Config Generated?Current Understanding:
Clarification Needed:
Question: 2. API Service Deployment & ArchitectureCurrent Plan:
Questions:
3. Model DeploymentQuestions:
3. RAG System & MilvusCurrent Plan:
Questions:
4. Dashboard IntegrationCurrent Understanding:
Questions:
5. Scope & PrioritiesQuestions:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have a rapidly expanding configurations, it is likely a usability issue in the long term. We can keep up the documentation update but a more AI native solution is to use LLM to generate the configuration manifests.
A few actions for reviews:
Anything else?
Beta Was this translation helpful? Give feedback.
All reactions