AI: changed deployment profiling attribute

Author: tbazant

DC-AI-deployment

@@ -8,7 +8,7 @@ ADOC_TYPE=book
 ADOC_ATTRIBUTES=" --attribute env-daps=1"
 ADOC_ATTRIBUTES+=" --attribute PROF_PRODUCT=suseai"
 ADOC_ATTRIBUTES+=" --attribute PROF_PRODUCT=suseai"
-ADOC_ATTRIBUTES+=" --attribute deployment_standard"
+ADOC_ATTRIBUTES+=" --attribute PROF_DEPLOYMENT=standard"
 
 STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns"
 FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse-ns"

DC-AI-deployment-airgapped

@@ -7,7 +7,7 @@ ADOC_POST=yes
 ADOC_TYPE=book
 ADOC_ATTRIBUTES=" --attribute env-daps=1"
 ADOC_ATTRIBUTES+=" --attribute PROF_PRODUCT=suseai"
-ADOC_ATTRIBUTES+=" --attribute deployment_airgap"
+ADOC_ATTRIBUTES+=" --attribute PROF_DEPLOYMENT=airgapped"
 
 STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns"
 FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse-ns"

glues/ai-library-intro.adoc

@@ -34,12 +34,12 @@ Applications in the {sregistry} are not built by the {suse} build system.
 They are mirrored upstream projects with attached supply chain artifacts.
 These artifacts help you source popular applications and tools in the AI ecosystem from a single source and provide built-in visibility into their upstream origins.
 Learn more on the registry's link:https://registry.suse.com/[Web site]
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 and refer to xref:ai-library-apps-verifying[] to see how to verify the supply chain artifacts
 endif::[]
 .
 
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 You can install the required {ailibrary} component {helm} charts using one of the following methods:
 
 * Install each AI application manually using the {helm} CLI as described in xref:suse-ai-deploy-suse-ai[].

glues/ai-ssecurity-intro.adoc

@@ -2,6 +2,6 @@
 = Installing {ssecurity}
 
 This chapter describes how to install {ssecurity} to scan {suseai} nodes for vulnerabilities and improve data protection.
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 You can install it either using xref:suse-security-installation-rancher[{ranchermanager}] or on any xref:suse-security-installation-kubernetes[{kube} cluster].
 endif::[]

references/AI-installation-flowchart.adoc

@@ -21,7 +21,7 @@ endif::[]
 :override-abstract!:
 :override-title!:
 
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 The presented steps mainly relate to *manual* command-line installation.
 
 However, there are alternative installation methods that can ease parts of the installation process.
@@ -34,13 +34,13 @@ The chart focuses on the following possible scenarios:
 * You have a supported Linux operating system and {kube} distribution installed on cluster nodes.
 * You have {rancherprime} and all supportive components installed on the {kube} cluster and are prepared to install the required applications from the {ailibrary}.
 
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 [#fg-ai-installation-flowchart]
 .{productname} installation process
 image::ai-installation-flowchart.png[alt="{productname} installation process",width=100%]
 endif::[]
 
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 [#fg-ai-installation-flowchart-airgapped]
 .{productname} air-gapped installation process
 image::ai-installation-flowchart-airgapped.png[alt="{productname} air-gapped installation process",width=100%]

references/owui-helm-overrides.adoc

@@ -9,7 +9,7 @@ include::../snippets/helm-chart-overrides-intro.adoc[]
 .{owui} override file with {ollama} included
 ====
 The following override file installs {ollama} during the {owui} installation.
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 [source,yaml]
 ----
 global:
@@ -103,7 +103,7 @@ Refer to link:https://www.nltk.org/index.html[] for licensing information.
 <.> API key value for communication between {owui} and {owui} Pipelines.
 The default value is '0p3n-w3bu!'.
 endif::[]
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 [source,yaml]
 ----
 global:
@@ -206,7 +206,7 @@ endif::[]
 .{owui} override file with {ollama} installed separately
 ====
 The following override file installs {ollama} separately from the {owui} installation.
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 [source,yaml]
 ----
 global:
@@ -261,7 +261,7 @@ For production use, we recommend using a storage solution suitable for persisten
 <.> These values are optional, required only to receive telemetry data from {owui}.
 <.> The URL of the {otelemetry} Collector installed by the user.
 endif::[]
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 [source,yaml]
 ----
 global:
@@ -329,7 +329,7 @@ This simple filter adds a limit to the number of question and answer turns durin
 =====
 Pipelines normally require additional configuration provided either via environment variables or specified in the {owui} Web UI.
 =====
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 [source,yaml]
 ----
 global:
@@ -361,7 +361,7 @@ ingress:
 <.> A list of pipeline URLs to be downloaded and installed by default.
 Individual URLs are separated by a semicolon `;`.
 endif::[]
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 [source,yaml]
 ----
 global:
@@ -396,7 +396,7 @@ For air-gapped deployments, you need to provide the pipelines at URLs that are a
 endif::[]
 ====
 
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 [#owui-ollama-deploy-vllm]
 .{owui} override file with a connection to {vllm}
 ====

tasks/AI-deployment-ailibrary-installing.adoc

@@ -21,14 +21,14 @@ endif::[]
 :revdate: 2026-02-10
 :page-revdate: {revdate}
 
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 This procedure includes steps to install {ailibrary} applications.
 endif::[]
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 This procedure includes steps to install {ailibrary} applications in an air-gapped environments.
 endif::[]
 
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 [NOTE]
 ====
 If the following steps do not specify on which part of the air-gapped architecture--_local_ or _remote_--the task should be performed, assume _remote_.
@@ -42,11 +42,11 @@ It is a separate entitlement from {rancherprime}.
 . Visit link:https://apps.rancher.io/[] to perform the check for the {productname} entitlement.
 If the entitlement check is successful, you are given access to pull and deploy the {productname}-related {helm} charts and container images available on {sappco}.
 . Visit the {sappco}, sign in and get the user access token as described in link:https://docs.apps.rancher.io/get-started/authentication/[].
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 . Visit {scc}, select the organization with an active {productname} subscription from the left sidebar, and save the registration code for the {productname} subscription.
 . On the _local_ cluster, create a {kube} namespace if it does not already exist.
 endif::[]
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 . Create a {kube} namespace if it does not already exist.
 endif::[]
 The steps in this procedure assume that all containers are deployed into the same namespace, referred to as `SUSE_AI_NAMESPACE`.
@@ -94,7 +94,7 @@ The username is `regcode` and the password is the {scca} registration code of yo
   -u regcode \
   -p <SCC_REG_CODE>
 ----
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 . On the _remote_ host, download the `SUSE-AI-get-images.sh` script from the xref:ai-air-gap-stack[air-gap stack] and run it.
 +
 [source,bash,subs="+attributes"]
@@ -117,20 +117,20 @@ Set `DST_REGISTRY_USERNAME` and `DST_REGISTRY_PASSWORD` environment variables if
 endif::[]
 . Install {certmanager} as described in xref:cert-manager-installing[].
 . Install {ailibrary} components.
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 You can either install each component separately, or use the {saideployer} chart to install the components together as described in xref:ailibrary-installing-deployer[].
 endif::[]
 
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 .. Install {milvus} as described in xref:milvus-installing[].
 endif::[]
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 .. Install an application with vector database capabilities.
 {owui} supports either xref:opensearch-installing[{opensearch}] or xref:milvus-installing[{milvus}].
 endif::[]
 ..  _(Optional)_ Install {ollama} as described in xref:ollama-installing[].
 .. Install {owui} as described in xref:owui-installing[].
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 .. Install {vllm} as described in xref:vllm-installing[].
 .. Install {mcpo} as described in xref:mcpo-installing[].
 .. Install {pytorch} as described in xref:pytorch-installing[].

tasks/AI-deployment-cluster-preparation.adoc

@@ -24,10 +24,10 @@ endif::[]
 :page-revdate: {revdate}
 
 
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 . Install xref:rancher-installation-quickstart[{ranchermanager}].
 endif::[]
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 . Install xref:rancher-installation-airgapped[{ranchermanager}].
 endif::[]
 +

tasks/AI-deployment-kube-installing.adoc

@@ -41,10 +41,10 @@ include::../snippets/ai-separate-rancher-cluster.adoc[]
 +
 We recommend using the supported {rke2} distribution.
 Refer to
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
   xref:rke2-installation-quickstart[]
 endif::[]
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
   xref:rke2-installation-airgapped[]
 endif::[]
 for details.

tasks/NVIDIA-GPU-driver-installation-SLES.adoc

@@ -67,7 +67,7 @@ functional system.
 [#nvidia-gpu-pre-install-procedure-sles]
 == The installation procedure
 
-ifdef::deployment_airgap[]
+ifeval::["{PROF_DEPLOYMENT}" == "airgapped"]
 . On the *remote* host, run the script
   `SUSE-AI-mirror-nvidia.sh` from the air-gapped stack
   (see xref:ai-air-gap-stack[]) to download all required
@@ -85,7 +85,7 @@ After the download is complete, transfer the downloaded directory with
 all its content to each GPU-enabled *local* host.
 endif::[]
 
-ifdef::deployment_standard[]
+ifeval::["{PROF_DEPLOYMENT}" == "standard"]
 . Add a package repository from {nvidia}. This allows pulling in
   additional utilities, for example, `nvidia-smi`.
 +