|
3 | 3 | [id="proc-installing-and-configuring-lightspeed_{context}"] |
4 | 4 | = Installing and configuring {ls-brand-name} |
5 | 5 |
|
6 | | -{ls-short} operates on a _Bring Your Own Model_ approach, meaning you must provide and configure access to your preferred Large Language Model (LLM) provider for the service to function. The {lcs-name} ({lcs-short}) acts as an intermediary and service layer for interfacing with LLM providers, relying on the Llama Stack service for core operations. {lcs-short} handles LLM provider setup, authentication, feedback, and Retrieval Augmented Generation (RAG). The {lcs-short} is designed to run as a sidecar container within the {product-very-short} Pod. |
| 6 | +{ls-short} includes three main components that work together to provide virtual assistant (chat) functionality to your developers. |
| 7 | + |
| 8 | +* Llama Stack server (container sidecar):: This server, based on open source Llama Stack, operates as the main gateway to your LLM inferencing provider for chat services. Its modular nature allows you to integrate other services, such as the Model Context Protocol (MCP). You must integrate your LLM provider with the Llama Stack server to support the chat functionality. This dependency on external LLM providers is called *Bring Your Own Model* (BYOM). |
| 9 | + |
| 10 | +* {lcs-name} (container sidecar):: This service, based on the open source Lightspeed Core, enables features that complement the Llama Stack server, including maintaining chat history and gathering user feedback. |
| 11 | + |
| 12 | +* {ls-short} (dynamic plugins):: These plugins are required to enable the {ls-short} user interface within your {product-very-short} instance. |
| 13 | + |
| 14 | +Configuring these components to initialise correctly and communicate with each other is essential in order to provide {ls-short} to your users. |
7 | 15 |
|
8 | 16 | [NOTE] |
9 | 17 | ==== |
10 | | -If you have already installed the previous {ls-short} (Developer Preview) with Road-Core Service (RCS), remove the previous {ls-short} configurations and settings and reinstall. |
11 | | -This step is necessary as {ls-short} originally required the use of the {rcs-name} as a sidecar container for interfacing with LLM providers. The updated architecture removes and replaces RCS with the new Lightspeed Core Service (LCS) and Llama Stack, which require a new configuration for volumes, containers, and secrets. |
| 18 | +If you have already installed the previous {ls-short} (Developer Preview) with Road-Core Service (RCS), you must remove the previous {ls-short} configurations and settings and reinstall. |
| 19 | +This step is necessary as {ls-short} has a new architecture. In the previous release, {ls-short} required the use of the {rcs-name} as a sidecar container for interfacing with LLM providers. The updated architecture removes and replaces RCS with the new {lcs-name} and Llama Stack server, and requires new configurations for the plugins, volumes, containers, and secrets. |
12 | 20 | ==== |
13 | 21 |
|
14 | 22 | .Prerequisites |
@@ -636,12 +644,12 @@ extraVolumes: |
636 | 644 | - mountPath: /app-root/config/lightspeed-stack.yaml |
637 | 645 | name: lightspeed-stack |
638 | 646 | ---- |
639 | | -... Add the {ls-short} and Llama Stack Secret file as shown in the following example: |
| 647 | +... Add the Llama Stack Secret file as shown in the following example: |
640 | 648 | + |
641 | 649 | [source,yaml] |
642 | 650 | ---- |
643 | 651 | extraEnvVarsSecrets: |
644 | | - - lightspeed-secrets |
| 652 | + - llama-stack-secrets |
645 | 653 | ---- |
646 | 654 | ... Add the {lcs-short} image as shown in the following example: |
647 | 655 | + |
@@ -717,7 +725,7 @@ upstream: |
717 | 725 | extraEnvVars: |
718 | 726 | ... |
719 | 727 | extraEnvVarsSecrets: |
720 | | - - lightspeed-secrets |
| 728 | + - llama-stack-secrets |
721 | 729 | extraVolumeMounts: |
722 | 730 | - mountPath: /app-root/config/lightspeed-stack.yaml |
723 | 731 | name: lightspeed-stack |
|
0 commit comments