Skip to content

Commit 96b1fe5

Browse files
authored
Merge pull request #64967 from danielclowers/CNV-24705
[enterprise-4.14] CNV-24705: Update TTO and SSP downstream sections
2 parents dc3c88f + 0844b01 commit 96b1fe5

8 files changed

+26
-20
lines changed

modules/virt-about-ssp-operator.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
// Module included in the following assemblies:
22
//
3-
// * virt/virt-architecture.adoc
3+
// * virt/about_virt/virt-architecture.adoc
44

55
:_content-type: CONCEPT
66
[id="virt-about-ssp-operator_{context}"]
77
= About the Scheduling, Scale, and Performance (SSP) Operator
88

9-
The SSP Operator, `ssp-operator`, deploys the common templates, the related default boot sources, and the template validator.
9+
The SSP Operator, `ssp-operator`, deploys the common templates, the related default boot sources, the pipeline tasks, and the template validator.
1010

1111
image::cnv_components_ssp-operator.png[ssp-operator components]
1212

modules/virt-about-tekton-tasks-operator.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88

99
The Tekton Tasks Operator, `tekton-tasks-operator`, deploys example pipelines showing the usage of OpenShift Pipelines for virtual machines (VMs). This operator also deploys additional OpenShift Pipeline tasks that allow users to create VMs from templates, copy and modify templates, and create data volumes.
1010

11-
image::cnv_components_tekton-tasks-operator.png[tekton-tasks-operator components]
11+
//image::cnv_components_tekton-tasks-operator.png[tekton-tasks-operator components]
1212

1313
.Tekton Tasks Operator components
1414
[cols="1,1"]

modules/virt-deploying-tto.adoc renamed to modules/virt-deploying-ssp.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@
33
// * virt/virtual_machines/virt-managing-vms-openshift-pipelines.adoc
44

55
:_content-type: PROCEDURE
6-
[id="virt-deploying-tto_{context}"]
7-
= Deploying the Tekton Tasks Operator resources
6+
[id="virt-deploying-ssp_{context}"]
7+
= Deploying the Scheduling, Scale, and Performance (SSP) resources
88

9-
The Tekton Tasks Operator (TTO) tasks and example pipelines are not deployed by default when you install {VirtProductName}. To deploy TTO resources, enable the `deployTektonTaskResources` feature gate in the `HyperConverged` custom resource (CR).
9+
The SSP Operator example Tekton Tasks and Pipelines are not deployed by default when you install {VirtProductName}. To deploy the SSP Operator's Tekton resources, enable the `deployTektonTaskResources` feature gate in the `HyperConverged` custom resource (CR).
1010

1111
.Procedure
1212

@@ -33,7 +33,7 @@ spec:
3333
# ...
3434
----
3535
<1> The namespace where the pipelines are to be run.
36-
<2> The feature gate to be enabled to deploy TTO resources.
36+
<2> The feature gate to be enabled to deploy Tekton resources by SSP operator.
3737
+
3838
[NOTE]
3939
====
File renamed without changes.
File renamed without changes.

modules/virt-supported-tekton-tasks.adoc renamed to modules/virt-supported-ssp-tasks.adoc

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,16 +3,19 @@
33
// * virt/virtual_machines/virt-managing-vms-openshift-pipelines.adoc
44

55
:_content-type: REFERENCE
6-
[id="virt-supported-tekton-tasks_{context}"]
7-
= Virtual machine tasks supported by the Tekton Tasks Operator
6+
[id="virt-supported-ssp-tasks_{context}"]
7+
= Virtual machine tasks supported by the SSP Operator
88

9-
The following table shows the tasks that are included as part of the Tekton Tasks Operator.
9+
The following table shows the tasks that are included as part of the SSP Operator.
1010

11-
.Virtual machine tasks supported by the Tekton Tasks Operator
11+
.Virtual machine tasks supported by the SSP Operator
1212
[cols="1,1",options="header"]
1313
|===
1414
| Task | Description
1515

16+
| `create-vm-from-manifest`
17+
| Create a virtual machine from a provided manifest or with `virtctl`.
18+
1619
| `create-vm-from-template`
1720
| Create a virtual machine from a template.
1821

@@ -37,3 +40,8 @@ The following table shows the tasks that are included as part of the Tekton Task
3740
| `wait-for-vmi-status`
3841
| Wait for a specific status of a virtual machine instance and fail or succeed based on the status.
3942
|===
43+
44+
[NOTE]
45+
====
46+
Virtual machine creation in pipelines now utilizes `ClusterInstanceType` and `ClusterPreference` instead of template-based tasks, which have been deprecated. The `create-vm-from-template`, `copy-template`, and `modify-vm-template` commands remain available but are not used in default pipeline tasks.
47+
====

virt/about_virt/virt-architecture.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,4 @@ include::modules/virt-about-hpp-operator.adoc[leveloffset=+1]
3636

3737
include::modules/virt-about-ssp-operator.adoc[leveloffset=+1]
3838

39-
include::modules/virt-about-tekton-tasks-operator.adoc[leveloffset=+1]
40-
4139
include::modules/virt-about-virt-operator.adoc[leveloffset=+1]

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

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ toc::[]
88

99
link:https://docs.openshift.com/pipelines/latest/about/understanding-openshift-pipelines.html[{pipelines-title}] is a Kubernetes-native CI/CD framework that allows developers to design and run each step of the CI/CD pipeline in its own container.
1010

11-
The Tekton Tasks Operator (TTO) integrates {VirtProductName} with {pipelines-shortname}. TTO includes tasks and example pipelines that allow you to:
11+
The Scheduling, Scale, and Performance (SSP) Operator integrates {VirtProductName} with {pipelines-shortname}. The SSP Operator includes tasks and example pipelines that allow you to:
1212

1313
* Create and manage virtual machines (VMs), persistent volume claims (PVCs), and data volumes
1414
* Run commands in VMs
@@ -26,15 +26,15 @@ include::snippets/technology-preview.adoc[]
2626
* You have link:https://docs.openshift.com/pipelines/latest/install_config/installing-pipelines.html[installed {pipelines-shortname}].
2727

2828

29-
include::modules/virt-deploying-tto.adoc[leveloffset=+1]
29+
include::modules/virt-deploying-ssp.adoc[leveloffset=+1]
3030

31-
include::modules/virt-supported-tekton-tasks.adoc[leveloffset=+1]
31+
include::modules/virt-supported-ssp-tasks.adoc[leveloffset=+1]
3232

3333

3434
[id="example-pipelines_virt-managing-vms-openshift-pipelines"]
3535
== Example pipelines
3636

37-
The Tekton Tasks Operator includes the following example `Pipeline` manifests. You can run the example pipelines by using the web console or CLI.
37+
The SSP Operator includes the following example `Pipeline` manifests. You can run the example pipelines by using the web console or CLI.
3838

3939
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.
4040

@@ -46,12 +46,12 @@ Windows customize pipeline:: This pipeline clones the data volume of a basic Win
4646

4747
[NOTE]
4848
====
49-
The `tekton-tasks-operator` example pipelines use a config map file with `sysprep` predefined by {product-title} and suitable for Microsoft ISO files. For other ISO files, you might need to create a new config map file with a system-specific `sysprep` definition.
49+
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.
5050
====
5151

52-
include::modules/virt-running-tto-pipeline-web.adoc[leveloffset=+2]
52+
include::modules/virt-running-ssp-pipeline-web.adoc[leveloffset=+2]
5353

54-
include::modules/virt-running-tto-pipeline-cli.adoc[leveloffset=+2]
54+
include::modules/virt-running-ssp-pipeline-cli.adoc[leveloffset=+2]
5555

5656
[role="_additional-resources"]
5757
[id="additional-resources_virt-managing-vms-openshift-pipelines"]

0 commit comments

Comments
 (0)