[release-1.8] RHDHPAI-1091: Lightspeed Core Developer Lightspeed (redhat-developer#1545)

* Lightspeed Core Developer Lightspeed

* Incorporated some of the comments

* Fixed merge conflict

* Incorporated the remaining tech comments

* Incorporated Ben's comments

* Added some comments

* Incorporated some comments and added architecture image

* Minor change

* Added the new heading for install and configure

* Incorporated Tim's suggestions

* Fixing build error

* Minor changes and rebase

* updating rcs

* Minor change

* minor change

* Minor change

* Incorporated Jordan and Ben's comments

* Maysuns comments and updated screenshots

* rhdhbugs-2225

* Minor changes and rebase

* Incorporated Karthik's comments

* Added Maysun's and Stephanie's comments

* Incorporated Jordan's coments

* Minor

* Minor changes

* Minor changes

---------

Co-authored-by: Priyanka Abel <[email protected]>

Author: 2 people

artifacts/attributes.adoc

@@ -53,8 +53,8 @@
 :odf-name: OpenShift Data Foundation
 :osd-brand-name: Red Hat OpenShift Dedicated
 :osd-short: OpenShift Dedicated
-:rcs-name: Road-Core Service
-:rcs-short: RCS
+:lcs-name: Lightspeed Core Service
+:lcs-short: LCS
 :rhacs-brand-name: Red Hat Advanced Cluster Security
 :rhacs-short: Advanced Cluster Security
 :rhacs-very-short: ACS

assemblies/assembly-customizing-developer-lightspeed.adoc

@@ -4,9 +4,7 @@
 [id="{context}"]
 = Customizing {ls-short}
 
-You can customize {ls-short} functionalities, such as, question validation, gathering feedback, and storing chat history in PostgreSQL.
-
-include::modules/developer-lightspeed/proc-using-question-validation.adoc[leveloffset=+1]
+You can customize {ls-short} functionalities such as gathering feedback, storing chat history in PostgreSQL, and {model-context-protocol-link}#proc-configure-mcp-tools-for-developer-lightspeed_assembly-model-context-protocol-tools[configuring Model Context Protocol (MCP) tools].
 
 include::modules/developer-lightspeed/proc-gathering-feedback.adoc[leveloffset=+1]
 

assemblies/assembly-developer-lightspeed.adoc

@@ -8,7 +8,7 @@ include::modules/developer-lightspeed/con-about-developer-lightspeed.adoc[levelo
 
 include::modules/developer-lightspeed/con-supported-architecture.adoc[leveloffset=+1]
 
-include::modules/developer-lightspeed/con-about-road-core-service.adoc[leveloffset=+2]
+include::modules/developer-lightspeed/con-about-lightspeed-stack-and-llama-stack.adoc[leveloffset=+2]
 
 include::modules/developer-lightspeed/con-rag-embeddings.adoc[leveloffset=+1]
 

assemblies/assembly-using-developer-lightspeed.adoc

@@ -13,6 +13,15 @@ endif::[]
 
 {ls-brand-name} is designed to support you when performing various tasks during your development workflow.
 
+[NOTE]
+====
+The `Question Validation` feature is enabled by default if you are using the `quay.io/redhat-ai-dev/llama-stack` image without overriding the `run.yaml` configuration file in the image. To disable `Question Validation`, you must mount a `run.yaml` file to the container with the following sections removed:
+
+* `Safety`
+* `Shields`
+* `External_providers_dir` set to `null` 
+====
+
 With `Question Validation` enabled, you can ask {ls-short} the following types of questions:
 
 * “Tell me about {product}.”

images/rhdh-plugins-reference/developer-lightspeed-1-8-0.png

@@ -3,7 +3,7 @@
 [id="con-about-bring-your-own-model_{context}"]
 = About Bring Your Own Model
 
-{ls-short} does not provide its own inference services, but uses a _Bring Your Own Model_ approach. This means that you can configure the {rcs-name} to talk to the inference server or service of your choice. This also means that you are responsible for ensuring that the configured service meets your particular company policies and legal requirements, including any applicable terms with the third-party model provider.
+{ls-short} does not provide its own inference services, but uses a _Bring Your Own Model_ approach. This means that you can configure the {lcs-name} to talk to the inference server or service of your choice. This also means that you are responsible for ensuring that the configured service meets your particular company policies and legal requirements, including any applicable terms with the third-party model provider.
 //Add the cross reference to "Bring your own model"
 The only technical requirements for inference services are:
 

images/rhdh-plugins-reference/developer-lightspeed-architecture-1-8-0.png

@@ -14,7 +14,7 @@ This early access program enables customers to share feedback on the user experi
 You can experience {ls-short} Developer Preview by installing the Developer Lightspeed for {product} plugin within an existing {product-very-short} instance.
 Alternatively, if you prefer to test it locally first, you can try {ls-short} using {product-local-very-short}.
 
-image::rhdh-plugins-reference/developer-lightspeed.png[]
+image::rhdh-plugins-reference/developer-lightspeed-1-8-0.png[]
 
 .Additional resources
-* link:https://github.com/redhat-developer/rhdh-local/blob/main/README.md[{product-local-very-short}]
+* link:https://github.com/redhat-developer/rhdh-local/blob/main/README.md[{product-local-very-short}]

images/rhdh-plugins-reference/developer-lightspeed.png

@@ -0,0 +1,33 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="con-about-lightspeed-stack-and-llama-stack_{context}"]
+= About {lcs-name} and Llama Stack
+
+The {lcs-name} and Llama Stack deploy together as sidecar containers to augment {product-very-short} functionality.
+
+The Llama Stack delivers the augmented functionality by integrating and managing core components, which include:
+
+* Large language model (LLM) inference providers
+
+* Model Context Protocol (MCP) or Retrieval Augmented Generation (RAG) tool runtime providers
+
+* Safety providers
+
+* Vector database settings
+
+The {lcs-name} serves as the Llama Stack service intermediary. It manages the operational configuration and key data, specifically:
+
+* User feedback collection
+
+* MCP server configuration
+
+* Conversation history
+
+Llama Stack provides the inference functionality that {lcs-short} uses to process requests. For more information, see https://llamastack.github.io/docs#what-is-llama-stack[What is Llama Stack].
+
+The {ls-brand-name} plugin in {product-very-short} sends prompts and receives LLM responses through the {lcs-short} sidecar. {lcs-short} then uses the Llama Stack sidecar service to perform inference and MCP or RAG tool calling.
+
+[NOTE]
+====
+{ls-brand-name} is a Developer Preview release. You must manually deploy the {lcs-name} and Llama Stack sidecar containers, and install the {ls-brand-name} plugin on your {product-very-short} instance.
+====