Merge pull request #73143 from sbeskin-redhat/CNV_29468_Update_pipeline_documentation

CNV-29468: Update pipeline documentation

Author: adellape

modules/virt-about-ssp-operator.adoc

@@ -6,39 +6,4 @@
 [id="virt-about-ssp-operator_{context}"]
 = About the Scheduling, Scale, and Performance (SSP) Operator
 
-The SSP Operator, `ssp-operator`, deploys the common templates, the related default boot sources, and the template validator.
-
-image::cnv_components_ssp-operator.png[ssp-operator components]
-
-.SSP Operator components
-[cols="1,1"]
-|===
-|*Component* |*Description*
-
-|`deployment/create-vm-from-template`
-|	Creates a VM from a template.
-
-|`deployment/copy-template`
-|	Copies a VM template.
-
-|`deployment/modify-vm-template`
-|	Creates or removes a VM template.
-
-|`deployment/modify-data-object`
-|	Creates or removes data volumes or data sources.
-
-|`deployment/cleanup-vm`
-|	Runs a script or a command on a VM, then stops or deletes the VM afterward.
-
-|`deployment/disk-virt-customize`
-|	Runs a `customize` script on a target persistent volume claim (PVC) using `virt-customize`.
-
-|`deployment/disk-virt-sysprep`
-|	Runs a `sysprep` script on a target PVC by using `virt-sysprep`.
-
-|`deployment/wait-for-vmi-status`
-|	Waits for a specific virtual machine instance (VMI) status, then fails or succeeds according to that status.
-
-|`deployment/create-vm-from-manifest`
-|   Creates a VM from a manifest.
-|===
+The SSP Operator, `ssp-operator`, deploys the common templates, the related default boot sources, the pipeline tasks, and the template validator.

modules/virt-temporary-token-VNC.adoc

@@ -70,12 +70,12 @@ $ virtctl vnc <vm_name> -n <namespace>
 
 [WARNING]
 ====
-It is currently not possible to revoke a specific token. 
+It is currently not possible to revoke a specific token.
 
 To revoke a token, you must delete the service account that was used to create it. However, this also revokes all other tokens that were created by using the service account. Use the following command with caution:
 
 [source,terminal]
 ----
-$ virtctl delete serviceaccount --namespace "<namespace>" "<vm_name>-vnc-access" 
+$ virtctl delete serviceaccount --namespace "<namespace>" "<vm_name>-vnc-access"
 ----
 ====

virt/about_virt/virt-architecture.adoc

@@ -12,7 +12,6 @@ The Operator Lifecycle Manager (OLM) deploys operator pods for each component of
 * Storage: `cdi-operator`
 * Network: `cluster-network-addons-operator`
 * Scaling: `ssp-operator`
-* Templating: `tekton-tasks-operator`
 
 OLM also deploys the `hyperconverged-cluster-operator` pod, which is responsible for the deployment, configuration, and life cycle of other components, and several helper pods: `hco-webhook`, and `hyperconverged-cluster-cli-download`.
 

virt/live_migration/virt-configuring-live-migration.adoc

@@ -10,7 +10,7 @@ You can configure live migration settings to ensure that the migration processes
 
 You can configure live migration policies to apply different migration configurations to groups of virtual machines (VMs).
 
-include::modules/virt-configuring-live-migration-limits.adoc[leveloffset=+2]
+include::modules/virt-configuring-live-migration-limits.adoc[leveloffset=+1]
 
 [id="live-migration-policies"]
 == Live migration policies

virt/virtual_machines/virt-managing-vms-openshift-pipelines.adoc

@@ -14,39 +14,25 @@ The Scheduling, Scale, and Performance (SSP) Operator integrates {VirtProductNam
 * Run commands in VMs
 * Manipulate disk images with `libguestfs` tools
 
-:FeatureName: Managing virtual machines with {pipelines-title}
-include::snippets/technology-preview.adoc[]
-
-
 [id="prerequisites_virt-managing-vms-openshift-pipelines"]
 == Prerequisites
 
 * You have access to an {product-title} cluster with `cluster-admin` permissions.
 * You have installed the OpenShift CLI (`oc`).
 * You have link:https://docs.openshift.com/pipelines/latest/install_config/installing-pipelines.html[installed {pipelines-shortname}].
 
-
-include::modules/virt-deploying-ssp.adoc[leveloffset=+1]
-
 include::modules/virt-supported-ssp-tasks.adoc[leveloffset=+1]
 
+[id="windows-efi-installer-pipeline_{context}"]
+== Windows EFI installer pipeline
 
-[id="example-pipelines_virt-managing-vms-openshift-pipelines"]
-== Example pipelines
-
-The SSP Operator includes the following example `Pipeline` manifests. You can run the example pipelines by using the web console or CLI.
-
-You might have to run more than one installer pipeline if you need multiple versions of Windows. If you run more than one installer pipeline, each one requires unique parameters, such as the `autounattend` config map and base image name. For example, if you need Windows 10 and Windows 11 or Windows Server 2022 images, you have to run both the Windows efi installer pipeline and the Windows bios installer pipeline. However, if you need Windows 11 and Windows Server 2022 images, you have to run only the Windows efi installer pipeline.
-
-Windows EFI installer pipeline:: This pipeline installs Windows 11 or Windows Server 2022 into a new data volume from a Windows installation image (ISO file). A custom answer file is used to run the installation process.
-
-Windows BIOS installer pipeline:: This pipeline installs Windows 10 into a new data volume from a Windows installation image, also called an ISO file. A custom answer file is used to run the installation process.
+You can run the link:https://artifacthub.io/packages/tekton-pipeline/redhat-pipelines/windows-efi-installer[Windows EFI installer pipeline] by using the web console or CLI.
 
-Windows customize pipeline:: This pipeline clones the data volume of a basic Windows 10, 11, or Windows Server 2022 installation, customizes it by installing Microsoft SQL Server Express or Microsoft Visual Studio Code, and then creates a new image and template.
+The Windows EFI installer pipeline installs Windows 10, Windows 11, or Windows Server 2022 into a new data volume from a Windows installation image (ISO file). A custom answer file is used to run the installation process.
 
 [NOTE]
 ====
-The example pipelines use a config map file with `sysprep` predefined by {product-title} and suitable for Microsoft ISO files. For ISO files pertaining to different Windows editions, it may be necessary to create a new config map file with a system-specific sysprep definition.
+The Windows EFI installer pipeline uses a config map file with `sysprep` predefined by {product-title} and suitable for Microsoft ISO files. For ISO files pertaining to different Windows editions, it may be necessary to create a new config map file with a system-specific `sysprep` definition.
 ====
 
 include::modules/virt-running-ssp-pipeline-web.adoc[leveloffset=+2]