Defect fixes for VSS and ChatQnA (open-edge-platform#630)

Author: bharagha

sample-applications/chat-question-and-answer-core/docs/user-guide/build-from-source.md

@@ -8,6 +8,9 @@ If you want to build the images via `docker compose`, please refer to the sectio
 
 Once all the images are built, go back to `chat-question-and-answer-core` directory by using `cd ..` command. Then, you can proceed to start the service using the `docker compose` command as described in the [Get Started](./get-started.md) page.
 
+> **Note:** 
+> - The build instruction is applicable only on an Ubuntu system. Build from source is not supported for the sample application on [Edge Microvisor Toolkit (EMT)](https://github.com/open-edge-platform/edge-microvisor-toolkit). The user is recommended to use prebuilt images on EMT. 
+
 ## Building the Backend Image
 To build the Docker image for the `Chat Question-and-Answer Core` application, follow these steps:
 

sample-applications/chat-question-and-answer/docs/user-guide/build-from-source.md

@@ -2,6 +2,10 @@
 
 This guide provides step-by-step instructions for building the ChatQ&A Sample Application from source.
 
+> **Note:** 
+> - The dependent microservices must be built separately from their respective microservice folders.
+> - The build instruction is applicable only on an Ubuntu system. Build from source is not supported either for the sample application or the dependent microservices on [Edge Microvisor Toolkit (EMT)](https://github.com/open-edge-platform/edge-microvisor-toolkit). The user is recommended to use prebuilt images on EMT. 
+
 ## Prerequisites
 
 Before you begin, ensure that you have the following prerequisites:

sample-applications/chat-question-and-answer/docs/user-guide/deploy-with-edge-orchestrator.md

@@ -18,9 +18,9 @@ To deploy the **ChatQ&A** Application with the Edge Orchestrator, follow the ste
 
 ### Prerequisites
 
-1. Access to the web interface of the Edge Orchestrator with one or more [Edge Nodes Onboarded](<https://docs.openedgeplatform.intel.com/edge-manage-docs/main/user_guide/set_up_edge_infra/edge_node_onboard.html>) to the Edge Orchestrator.
+1. Access to the web interface of the Edge Orchestrator with one or more [Edge Nodes Onboarded](<https://docs.openedgeplatform.intel.com/edge-manage-docs/main/user_guide/set_up_edge_infra/edge_node_onboard/index.html>) to the Edge Orchestrator.
 
-1. Clusters with a [privilege template](<https://docs.openedgeplatform.intel.com/edge-manage-docs/main/user_guide/additional_howtos/set_up_a_cluster_template.html>) have been created on the needed Edge Nodes following the procedures described in [Create Cluster](<https://docs.openedgeplatform.intel.com/edge-manage-docs/main/user_guide/set_up_edge_infra/create_clusters.html#create-cluster>).
+1. Clusters with a [privilege template](<https://docs.openedgeplatform.intel.com/edge-manage-docs/main/user_guide/advanced_functionality/set_up_a_cluster_template.html>) have been created on the needed Edge Nodes following the procedures described in [Create Cluster](<https://docs.openedgeplatform.intel.com/edge-manage-docs/main/user_guide/set_up_edge_infra/clusters/create_clusters.html#create-cluster>).
 
 ### Making the Deployment Package Available
 
@@ -79,7 +79,7 @@ For more information on setting up a deployment, see [Set up a Deployment](<http
 
 ### Access the **ChatQ&A** AI-Suite
 
-1. Download the kubeconfig of the cluster of the Edge Node on which the Application has been deployed. Refer [Kubeconfig Download](<https://docs.openedgeplatform.intel.com/edge-manage-docs/main/user_guide/set_up_edge_infra/accessing_clusters.html#organize-cluster-access-with-a-kubeconfig-file>).
+1. Download the kubeconfig of the cluster of the Edge Node on which the Application has been deployed. Refer [Kubeconfig Download](<https://docs.openedgeplatform.intel.com/edge-manage-docs/main/user_guide/set_up_edge_infra/clusters/accessing_clusters.html>).
 
 1. Follow the steps described in the **ChatQ&A** [Documentation](<deploy-with-helm.md>) on usage of the application.
 

sample-applications/document-summarization/docs/user-guide/build-from-source.md

@@ -2,6 +2,9 @@
 
 This section shows how to build the Document Summarization Sample Application from the source.
 
+> **Note:** 
+> - The build instruction is applicable only on an Ubuntu system. Build from source is not supported for the sample application on [Edge Microvisor Toolkit (EMT)](https://github.com/open-edge-platform/edge-microvisor-toolkit). The user is recommended to use prebuilt images on EMT. 
+
 ## Prerequisites
 
 Before you begin, ensure that you have the following prerequisites:

sample-applications/video-search-and-summarization/docs/user-guide/build-from-source.md

@@ -2,7 +2,9 @@
 
 This section shows how to build the Video Search and Summary sample application from source.
 
-> **Note:** The dependent microservices must be built separately from their respective microservice folders.
+> **Note:** 
+> - The dependent microservices can be built separately from their respective microservice folders which is recommended. There is an option provided to build dependencies along with sample application if required.
+> - The build instruction is applicable only on an Ubuntu system. Build from source is not supported either for the sample application or the dependent microservices on [Edge Microvisor Toolkit (EMT)](https://github.com/open-edge-platform/edge-microvisor-toolkit). The user is recommended to use prebuilt images on EMT. 
 
 ## Prerequisites
 

sample-applications/video-search-and-summarization/docs/user-guide/deploy-with-helm.md

@@ -8,6 +8,7 @@ Before you begin, ensure that you have the following:
 - The cluster must support **dynamic provisioning of Persistent Volumes (PV)**. Refer to the [Kubernetes Dynamic Provisioning Guide](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/) for more details.
 - Install `kubectl` on your system. See the [Installation Guide](https://kubernetes.io/docs/tasks/tools/install-kubectl/). Ensure access to the Kubernetes cluster. 
 - Helm chart installed on your system. See the [Installation Guide](https://helm.sh/docs/intro/install/).
+- Video Search and Summary requires PVC storage class to support `RWMany` mode. In case the default storage class used does not support it, consider using storage solution like [LongHorn](https://longhorn.io/docs/) that provides this support. Video Search and Summary intends to remove this prerequisite in future release and use only `RWOnce` mode. 
 
 ## Steps to deploy with Helm
 Do the following to deploy VSS using Helm chart. 

sample-applications/video-search-and-summarization/docs/user-guide/release-notes.md

@@ -2,6 +2,25 @@
 
 
 ## Current Release
+**Version**: RC4.1 \
+**Release Date**: 29 July 2025  
+
+**Features**:
+- This is an incremental release on top of RC4 providing fixes for issues found on RC4. The notes provided under RC4 apply for this incremental release too.
+- Issues fixed are listed below:
+    - Error message is displayed on the UI when invalid video is uploaded in both video summary and video search modes.
+    - Only mp4 format is supported currently. For other formats, error message is displayed on the UI.
+    - Fix to ensure that the sample application can be shutdown in a terminal different from the one in which it was started.
+    - A few minor documentation issues have been fixed.
+    - Provided a means to manage the PVC in values.yaml file.
+    - Fixed an issue where video summary progress is kept in the pipeline manager service even if the specific video summary is deleted
+    - Issues around tag handling for videos has been fixed.
+    - Trouble shooting section updated with observed useful information.
+    - Enabled a minimum configuration of video summary to work on older Xeon configurations. Note that there is no official support for versions of Xeon earlier than Xeon 4.
+
+
+## Previous releases
+
 **Version**: RC4 \
 **Release Date**: 18 June 2025  
 
@@ -29,10 +48,3 @@
 - The Helm chart presently supports only CPU deployments.
 - Known issues are internally tracked. Reference not provided here.
 - `how-to-performance` document is not updated yet. HW sizing details will be added to this section shortly.
-
-## Previous releases
-
-**Version**:  \
-**Release Date**:  
-
-- <Previous release notes>