Updates to /jtdb-aem-migration

jtbd-aem-conversion/get_started/con-improve-ai-accuracy-with-feedback.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: CONCEPT
 [id="con-improve-ai-accuracy-with-feedback"]
 
-= Improve OpenShift Lightspeed accuracy by submitting response feedback
+= Improve response accuracy with feedback
 
 [role="_abstract"]
 Help improve the quality of {ols-official} responses by submitting feedback on the accuracy and usefulness of AI-generated answers. Your feedback is used to refine the model's performance over time.

jtbd-aem-conversion/integrate/con-govern-ai-operations.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: CONCEPT
 [id="con-govern-ai-operations"]
 
-= Govern with operations OpenShift Lightspeed performs autonomously
+= Govern autonomous cluster operations
 
 [role="_abstract"]
 Control the tools and operations that {ols-official} can invoke autonomously. Configure query-based tool filtering to restrict which tools the AI can select, and set up manual approval gates to require human confirmation before critical operations execute.

jtbd-aem-conversion/integrate/ols-configuring-custom-tls-certificates-aws-bedrock.adoc

@@ -0,0 +1,2 @@
+// Placeholder: Provider-specific version of modules/ols-configuring-custom-tls-certificates.adoc
+// Extract the AWS Bedrock-specific content from the shared module into this file.

jtbd-aem-conversion/integrate/ols-configuring-custom-tls-certificates-azure-openai.adoc

@@ -0,0 +1,68 @@
+:_mod-docs-content-type: PROCEDURE
+[id="ols-configuring-custom-tls-certificates-azure-openai"]
+
+= Configuring custom TLS certificates
+
+[role="_abstract"]
+Use the {ocp-product-title} web console to configure custom TLS certificates for secure communication between {ols-long} and your service endpoints.
+
+.Prerequisites
+
+* You have logged in to the {ocp-product-title} web console as a user with the `cluster-admin` role. As another option, you have logged in to a user account that has permission to create or edit the `OLSConfig` custom resource (CR).
+
+* You have a large language model (LLM) provider.
+
+* You have installed the {ols-long} Operator.
+
+* You have created the credentials secret and the `OLSconfig` CR.
+
+.Procedure
+
+. In the {ocp-product-title} web console, click *Operators* -> *Installed Operators*.
+
+. Select *All Projects* in the *Project* dropdown at the top of the screen.
+
+. Click {ols-long} Operator.
+
+. Click *OLSConfig*, then click the `cluster` configuration instance in the list.
+
+. Click the *YAML* tab.
+
+. Update the `OLSconfig` CR to contain the file that has the TLS secret.
++
+[source,yaml]
+----
+apiVersion: ols.openshift.io/v1alpha1
+kind: OLSConfig
+metadata:
+  name: cluster
+spec:
+  ols:
+    tlsConfig:
+      keyCertSecretRef:
+        name: <lightspeed_tls>
+---
+apiVersion: v1
+data:
+  tls.crt: LS0tLS1CRUd...
+  tls.key: LS0tLS1CRUd...
+kind: Secret
+metadata:
+  name: <lightspeed_tls>
+  namespace: <openshift_lightspeed>
+----
++
+* `spec.ols.tlsConfig.keyCertSecretRef.name` specifies the secret that has the `tls.crt` and `tls.key` file.
++
+* `apiVersion.data.tls` specifies that the name of the certificate must be `tls.crt` and the name of the key must be `tls.key`.
+
+. Click *Save*.
+
+.Verification
+
+. Verify that a new pod exists in the `lightspeed-app-server` deployment by running the following command:
++
+[source,terminal]
+----
+$ oc get pod -n openshift-lightspeed
+----

jtbd-aem-conversion/integrate/ols-configuring-custom-tls-certificates-google-vertex-ai.adoc

@@ -0,0 +1,68 @@
+:_mod-docs-content-type: PROCEDURE
+[id="ols-configuring-custom-tls-certificates-google-vertex-ai"]
+
+= Configuring custom TLS certificates
+
+[role="_abstract"]
+Use the {ocp-product-title} web console to configure custom TLS certificates for secure communication between {ols-long} and your service endpoints.
+
+.Prerequisites
+
+* You have logged in to the {ocp-product-title} web console as a user with the `cluster-admin` role. As another option, you have logged in to a user account that has permission to create or edit the `OLSConfig` custom resource (CR).
+
+* You have a large language model (LLM) provider.
+
+* You have installed the {ols-long} Operator.
+
+* You have created the credentials secret and the `OLSconfig` CR.
+
+.Procedure
+
+. In the {ocp-product-title} web console, click *Operators* -> *Installed Operators*.
+
+. Select *All Projects* in the *Project* dropdown at the top of the screen.
+
+. Click {ols-long} Operator.
+
+. Click *OLSConfig*, then click the `cluster` configuration instance in the list.
+
+. Click the *YAML* tab.
+
+. Update the `OLSconfig` CR to contain the file that has the TLS secret.
++
+[source,yaml]
+----
+apiVersion: ols.openshift.io/v1alpha1
+kind: OLSConfig
+metadata:
+  name: cluster
+spec:
+  ols:
+    tlsConfig:
+      keyCertSecretRef:
+        name: <lightspeed_tls>
+---
+apiVersion: v1
+data:
+  tls.crt: LS0tLS1CRUd...
+  tls.key: LS0tLS1CRUd...
+kind: Secret
+metadata:
+  name: <lightspeed_tls>
+  namespace: <openshift_lightspeed>
+----
++
+* `spec.ols.tlsConfig.keyCertSecretRef.name` specifies the secret that has the `tls.crt` and `tls.key` file.
++
+* `apiVersion.data.tls` specifies that the name of the certificate must be `tls.crt` and the name of the key must be `tls.key`.
+
+. Click *Save*.
+
+.Verification
+
+. Verify that a new pod exists in the `lightspeed-app-server` deployment by running the following command:
++
+[source,terminal]
+----
+$ oc get pod -n openshift-lightspeed
+----

jtbd-aem-conversion/integrate/ols-configuring-custom-tls-certificates-openai.adoc

@@ -0,0 +1,68 @@
+:_mod-docs-content-type: PROCEDURE
+[id="ols-configuring-custom-tls-certificates-openai"]
+
+= Configuring custom TLS certificates
+
+[role="_abstract"]
+Use the {ocp-product-title} web console to configure custom TLS certificates for secure communication between {ols-long} and your service endpoints.
+
+.Prerequisites
+
+* You have logged in to the {ocp-product-title} web console as a user with the `cluster-admin` role. As another option, you have logged in to a user account that has permission to create or edit the `OLSConfig` custom resource (CR).
+
+* You have a large language model (LLM) provider.
+
+* You have installed the {ols-long} Operator.
+
+* You have created the credentials secret and the `OLSconfig` CR.
+
+.Procedure
+
+. In the {ocp-product-title} web console, click *Operators* -> *Installed Operators*.
+
+. Select *All Projects* in the *Project* dropdown at the top of the screen.
+
+. Click {ols-long} Operator.
+
+. Click *OLSConfig*, then click the `cluster` configuration instance in the list.
+
+. Click the *YAML* tab.
+
+. Update the `OLSconfig` CR to contain the file that has the TLS secret.
++
+[source,yaml]
+----
+apiVersion: ols.openshift.io/v1alpha1
+kind: OLSConfig
+metadata:
+  name: cluster
+spec:
+  ols:
+    tlsConfig:
+      keyCertSecretRef:
+        name: <lightspeed_tls>
+---
+apiVersion: v1
+data:
+  tls.crt: LS0tLS1CRUd...
+  tls.key: LS0tLS1CRUd...
+kind: Secret
+metadata:
+  name: <lightspeed_tls>
+  namespace: <openshift_lightspeed>
+----
++
+* `spec.ols.tlsConfig.keyCertSecretRef.name` specifies the secret that has the `tls.crt` and `tls.key` file.
++
+* `apiVersion.data.tls` specifies that the name of the certificate must be `tls.crt` and the name of the key must be `tls.key`.
+
+. Click *Save*.
+
+.Verification
+
+. Verify that a new pod exists in the `lightspeed-app-server` deployment by running the following command:
++
+[source,terminal]
+----
+$ oc get pod -n openshift-lightspeed
+----

jtbd-aem-conversion/integrate/ols-configuring-custom-tls-certificates-openshift-ai.adoc

@@ -0,0 +1,68 @@
+:_mod-docs-content-type: PROCEDURE
+[id="ols-configuring-custom-tls-certificates-openshift-ai"]
+
+= Configuring custom TLS certificates
+
+[role="_abstract"]
+Use the {ocp-product-title} web console to configure custom TLS certificates for secure communication between {ols-long} and your service endpoints.
+
+.Prerequisites
+
+* You have logged in to the {ocp-product-title} web console as a user with the `cluster-admin` role. As another option, you have logged in to a user account that has permission to create or edit the `OLSConfig` custom resource (CR).
+
+* You have a large language model (LLM) provider.
+
+* You have installed the {ols-long} Operator.
+
+* You have created the credentials secret and the `OLSconfig` CR.
+
+.Procedure
+
+. In the {ocp-product-title} web console, click *Operators* -> *Installed Operators*.
+
+. Select *All Projects* in the *Project* dropdown at the top of the screen.
+
+. Click {ols-long} Operator.
+
+. Click *OLSConfig*, then click the `cluster` configuration instance in the list.
+
+. Click the *YAML* tab.
+
+. Update the `OLSconfig` CR to contain the file that has the TLS secret.
++
+[source,yaml]
+----
+apiVersion: ols.openshift.io/v1alpha1
+kind: OLSConfig
+metadata:
+  name: cluster
+spec:
+  ols:
+    tlsConfig:
+      keyCertSecretRef:
+        name: <lightspeed_tls>
+---
+apiVersion: v1
+data:
+  tls.crt: LS0tLS1CRUd...
+  tls.key: LS0tLS1CRUd...
+kind: Secret
+metadata:
+  name: <lightspeed_tls>
+  namespace: <openshift_lightspeed>
+----
++
+* `spec.ols.tlsConfig.keyCertSecretRef.name` specifies the secret that has the `tls.crt` and `tls.key` file.
++
+* `apiVersion.data.tls` specifies that the name of the certificate must be `tls.crt` and the name of the key must be `tls.key`.
+
+. Click *Save*.
+
+.Verification
+
+. Verify that a new pod exists in the `lightspeed-app-server` deployment by running the following command:
++
+[source,terminal]
+----
+$ oc get pod -n openshift-lightspeed
+----

jtbd-aem-conversion/integrate/ols-configuring-custom-tls-certificates-rhelai.adoc

@@ -0,0 +1,68 @@
+:_mod-docs-content-type: PROCEDURE
+[id="ols-configuring-custom-tls-certificates-rhelai"]
+
+= Configuring custom TLS certificates
+
+[role="_abstract"]
+Use the {ocp-product-title} web console to configure custom TLS certificates for secure communication between {ols-long} and your service endpoints.
+
+.Prerequisites
+
+* You have logged in to the {ocp-product-title} web console as a user with the `cluster-admin` role. As another option, you have logged in to a user account that has permission to create or edit the `OLSConfig` custom resource (CR).
+
+* You have a large language model (LLM) provider.
+
+* You have installed the {ols-long} Operator.
+
+* You have created the credentials secret and the `OLSconfig` CR.
+
+.Procedure
+
+. In the {ocp-product-title} web console, click *Operators* -> *Installed Operators*.
+
+. Select *All Projects* in the *Project* dropdown at the top of the screen.
+
+. Click {ols-long} Operator.
+
+. Click *OLSConfig*, then click the `cluster` configuration instance in the list.
+
+. Click the *YAML* tab.
+
+. Update the `OLSconfig` CR to contain the file that has the TLS secret.
++
+[source,yaml]
+----
+apiVersion: ols.openshift.io/v1alpha1
+kind: OLSConfig
+metadata:
+  name: cluster
+spec:
+  ols:
+    tlsConfig:
+      keyCertSecretRef:
+        name: <lightspeed_tls>
+---
+apiVersion: v1
+data:
+  tls.crt: LS0tLS1CRUd...
+  tls.key: LS0tLS1CRUd...
+kind: Secret
+metadata:
+  name: <lightspeed_tls>
+  namespace: <openshift_lightspeed>
+----
++
+* `spec.ols.tlsConfig.keyCertSecretRef.name` specifies the secret that has the `tls.crt` and `tls.key` file.
++
+* `apiVersion.data.tls` specifies that the name of the certificate must be `tls.crt` and the name of the key must be `tls.key`.
+
+. Click *Save*.
+
+.Verification
+
+. Verify that a new pod exists in the `lightspeed-app-server` deployment by running the following command:
++
+[source,terminal]
+----
+$ oc get pod -n openshift-lightspeed
+----