MTV-3225: Replacing links that contain attributes

RichardHoch · RichardHoch · commit 50d3e0ccd43e · 2025-09-10T14:49:56.000+03:00
diff --git a/documentation/modules/accessing-default-validation-rules.adoc b/documentation/modules/accessing-default-validation-rules.adoc
@@ -19,7 +19,7 @@ Example: If a default rule contains the line `default valid_input = false` and y
 $ {oc} rsh <validation_pod>
 ----
 
-. Go to the OPA policies directory for your provider:
+. Go to the Open Policy Agent (OPA) policies directory for your provider:
 +
 [source,terminal]
 ----
diff --git a/documentation/modules/accessing-logs-cli.adoc b/documentation/modules/accessing-logs-cli.adoc
@@ -18,7 +18,7 @@ If you specify a non-existent resource in the filtered `must-gather` command, no
 .Prerequisites
 
 * You must be logged in to the {virt} cluster as a user with the `cluster-admin` role.
-* You must have the link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/cli_tools/openshift-cli-oc#cli-getting-started[{ocp} CLI (`oc`)] installed.
+* You must have the {ocp} CLI (`oc`) installed. For more information, see {ocp-doc}/cli_tools/openshift-cli-oc#cli-getting-started[Getting started with the {ocp-short}].
 
 .Procedure
 
diff --git a/documentation/modules/adding-hook-using-cli.adoc b/documentation/modules/adding-hook-using-cli.adoc
@@ -30,7 +30,7 @@ You can retrieve additional information stored in a secret or in a `ConfigMap` b
 * VMs running on Microsoft Server only: Remote Execution enabled
 
 .Additional resources
-For instructions for creating a service account, see link:https://docs.openshift.com/container-platform/{ocp-version}/authentication/understanding-and-creating-service-accounts.html[Understanding and creating service accounts].
+For instructions for creating a service account, see {ocp-doc}/authentication_and_authorization/index#understanding-and-creating-service-accounts[Understanding and creating service accounts].
 
 .Procedure
 . If needed, create a Secret with an SSH private key for the VM.
diff --git a/documentation/modules/adding-hook-using-ui.adoc b/documentation/modules/adding-hook-using-ui.adoc
@@ -25,7 +25,7 @@ You can run one pre-migration hook, one post-migration hook, or one of each per
 * VMs running on Microsoft Server only: Remote Execution enabled
 
 .Additional resources
-For instructions for creating a service account, see link:https://docs.openshift.com/container-platform/{ocp-version}/authentication/understanding-and-creating-service-accounts.html[Understanding and creating service accounts].
+For instructions for creating a service account, see {ocp-doc}/authentication_and_authorization/index#understanding-and-creating-service-accounts[Understanding and creating service accounts].
 
 .Procedure
 
diff --git a/documentation/modules/adding-source-provider.adoc b/documentation/modules/adding-source-provider.adoc
@@ -78,7 +78,7 @@ You can migrate VMs from the cluster that {project-short} is deployed on to anot
 
 .Prerequisites
 
-* You must have {a-virt} link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/authentication_and_authorization/using-service-accounts[service account token] with `cluster-admin` privileges.
+* You must have {a-virt} service account token with `cluster-admin` privileges. For more information on service account tokens, see {ocp-doc}/authentication_and_authorization/using-service-accounts#service-accounts-overview_using-service-accounts[Service accounts overview].
 endif::[]
 
 .Procedure
diff --git a/documentation/modules/common-attributes.adoc b/documentation/modules/common-attributes.adoc
@@ -11,6 +11,7 @@
 // when updating the ocp-version, update the ocp-y-version
 :ocp-version: 4.19
 :ocp-y-version: 4.19, 4.18, 4.17
+:ocp-doc: link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single
 :operator: mtv-operator
 :operator-name-ui: Migration Toolkit for Virtualization Operator
 :operator-name: MTV Operator
diff --git a/documentation/modules/creating-plan-wizard-290-cnv.adoc b/documentation/modules/creating-plan-wizard-290-cnv.adoc
@@ -114,7 +114,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-plan-wizard-290-ostack.adoc b/documentation/modules/creating-plan-wizard-290-ostack.adoc
@@ -114,7 +114,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-plan-wizard-290-ova.adoc b/documentation/modules/creating-plan-wizard-290-ova.adoc
@@ -114,7 +114,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-plan-wizard-290-rhv.adoc b/documentation/modules/creating-plan-wizard-290-rhv.adoc
@@ -123,7 +123,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
@@ -161,11 +161,11 @@ The *Plan settings* section of the page includes settings that you specified in
 
 . Check the following item on the *Plan settings* section of the page:
 
-* *Preserve CPU mode*: Generally, the CPU model (type) for RHV VMs is set at the cluster level. However, the CPU model can be set at the VM level, which is called a custom CPU model.
+* *Preserve CPU mode*: Generally, the CPU model (type) for {rhv-full} VMs is set at the cluster level. However, the CPU model can be set at the VM level, which is called a custom CPU model.
 +
 By default, MTV sets the CPU model on the destination cluster as follows: MTV preserves custom CPU settings for VMs that have them. For VMs without custom CPU settings, MTV does not set the CPU model. Instead, the CPU model is later set by OpenShift Virtualization.
 +
-To preserve the cluster-level CPU model of your RHV VMs, do the following:
+To preserve the cluster-level CPU model of your {rhv-full} VMs, do the following:
 
 .. Click the {kebab}.
 .. Toggle the *Whether to preserve the CPU model* switch.
diff --git a/documentation/modules/creating-plan-wizard-290-vmware.adoc b/documentation/modules/creating-plan-wizard-290-vmware.adoc
@@ -130,7 +130,7 @@ You do not need to enter the passphrases in a specific order. For each LUKS-encr
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 
diff --git a/documentation/modules/creating-validation-rule.adoc b/documentation/modules/creating-validation-rule.adoc
@@ -39,7 +39,7 @@ You create a link:https://www.openpolicyagent.org/docs/latest/policy-language/[R
 
 .Procedure
 
-. Create a config map CR according to the following example:
+. Create a config map custom resource (CR) according to the following example:
 +
 [source,yaml,subs="attributes+"]
 ----
diff --git a/documentation/modules/creating-vddk-image.adoc b/documentation/modules/creating-vddk-image.adoc
@@ -24,7 +24,7 @@ Storing the VDDK image in a public registry might violate the VMware license ter
 
 .Prerequisites
 
-* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/registry/setting-up-and-configuring-the-registry#configuring-registry-storage-baremetal[{ocp} image registry].
+* {ocp-doc}/registry/setting-up-and-configuring-the-registry#configuring-registry-storage-baremetal[{ocp} image registry].
 * `podman` installed.
 * You are working on a file system that preserves symbolic links (symlinks).
 * If you are using an external registry, {virt} must be able to access it.
@@ -41,11 +41,6 @@ $ mkdir /tmp/<dir_name> && cd /tmp/<dir_name>
 . In a browser, navigate to the link:https://developer.vmware.com/web/sdk/8.0/vddk[VMware VDDK version 8 download page].
 . Select version 8.0.1 and click *Download*.
 
-[NOTE]
-====
-In order to migrate to {virt} 4.12, download VDDK version 7.0.3.2 from the link:https://developer.vmware.com/web/sdk/7.0/vddk[VMware VDDK version 7 download page].
-====
-
 . Save the VDDK archive file in the temporary directory.
 . Extract the VDDK archive:
 +
diff --git a/documentation/modules/error-messages.adoc b/documentation/modules/error-messages.adoc
@@ -16,6 +16,6 @@ To resolve this problem, delete some of the CBT snapshots from the VM and restar
 
 .Unable to resize disk image to required size
 
-The `Unable to resize disk image to required size` error message is displayed when migration fails because a virtual machine on the target provider uses persistent volumes with an EXT4 file system on block storage. The problem occurs because the default overhead that is assumed by CDI does not completely include the reserved place for the root partition.
+The `Unable to resize disk image to required size` error message is displayed when migration fails because a virtual machine on the target provider uses persistent volumes with an EXT4 file system on block storage. The problem occurs because the default overhead that is assumed by Containerized Data Importer (CDI) does not completely include the reserved place for the root partition.
 
 To resolve this problem, increase the file system overhead in CDI to more than 10%.
diff --git a/documentation/modules/network-prerequisites.adoc b/documentation/modules/network-prerequisites.adoc
@@ -10,7 +10,7 @@ The following prerequisites apply to all migrations:
 
 * IP addresses, VLANs, and other network configuration settings must not be changed before or during migration. The MAC addresses of the virtual machines are preserved during migration.
 * The network connections between the source environment, the {virt} cluster, and the replication repository must be reliable and uninterrupted.
-* If you are mapping more than one source and destination network, you must create a link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/virtualization/virtual-machines#virt-creating-network-attachment-definition[network attachment definition] for each additional destination network.
+* If you are mapping more than one source and destination network, you must create a network attachment definition for each additional destination network. For more information, see {ocp-doc}/virtualization/index#virt-creating-vms-from-rh-images-overview[Creating virtual machines from Red Hat images overview].
 
 [id="ports_{context}"]
 == Ports
diff --git a/documentation/modules/storage-support.adoc b/documentation/modules/storage-support.adoc
@@ -60,7 +60,7 @@
 
 [NOTE]
 ====
-If the {virt} storage does not support link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/storage/dynamic-provisioning[dynamic provisioning], you must apply the following settings:
+If the {virt} storage does not support {ocp-doc}/storage/dynamic-provisioning#dynamic-provisioning[dynamic provisioning], you must apply the following settings:
 
 * `Filesystem` volume mode
 +
@@ -69,12 +69,12 @@ If the {virt} storage does not support link:https://access.redhat.com/documentat
 +
 `ReadWriteOnce` access mode does not support live virtual machine migration.
 
-See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/virtualization/virtual-machines#virt-customizing-storage-profile_virt-creating-data-volumes[Enabling a statically-provisioned storage class] for details on editing the storage profile.
+See {ocp-doc}/virtualization/storage#virt-configuring-storage-profile[Configuring the storage profile] for details on applying settings to a storage profile.
 ====
 
 [NOTE]
 ====
-If your migration uses block storage and persistent volumes created with an EXT4 file system, increase the file system overhead in CDI to be more than 10%. The default overhead that is assumed by CDI does not completely include the reserved place for the root partition. If you do not increase the file system overhead in CDI by this amount, your migration might fail.
+If your migration uses block storage and persistent volumes created with an EXT4 file system, increase the file system overhead in Containerized Data Importer (CDI) to be more than 10%. The default overhead that is assumed by CDI does not completely include the reserved place for the root partition. If you do not increase the file system overhead in CDI by this amount, your migration might fail.
 ====
 
 [NOTE]
diff --git a/documentation/modules/upgrading-mtv-ui.adoc b/documentation/modules/upgrading-mtv-ui.adoc
@@ -14,10 +14,10 @@ You can upgrade the {operator-name} by using the {ocp} web console to install th
 . Change the update channel to the correct release.
 +
 ifeval::["{build}" == "upstream"]
-See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-changing-update-channel_olm-upgrading-operators[Changing update channel] in the {ocp} documentation.
+See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-changing-update-channel_olm-upgrading-operators[Changing the manual update channel for an Operator] in the {ocp} documentation.
 endif::[]
 ifeval::["{build}" == "downstream"]
-See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-changing-update-channel_olm-upgrading-operators[Changing update channel] in the {ocp} documentation.
+See {ocp-doc}/operators/administrator-tasks#olm-changing-update-channel_olm-upgrading-operators[Changing update channel] in the {ocp} documentation.
 endif::[]
 
 . Confirm that *Upgrade status* changes from *Up to date* to *Upgrade available*. If it does not, restart the `CatalogSource` pod:
@@ -47,9 +47,5 @@ ifeval::["{build}" == "upstream"]
 See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
 endif::[]
 ifeval::["{build}" == "downstream"]
-See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
+See {ocp-doc}/operators/administrator-tasks#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
 endif::[]
-
-. If you are upgrading from {project-short} 2.2 and have defined VMware source providers, edit the VMware provider by adding a VDDK `init` image. Otherwise, the update will change the state of any VMware providers to `Critical`. For more information, see link:https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.4/html/installing_and_using_the_migration_toolkit_for_virtualization/migrating-vms-web-console#adding-source-provider_vmware[Adding a VMSphere source provider].
-
-. If you mapped to NFS on the {ocp} destination provider in {project-short} 2.2, edit the `AccessModes` and `VolumeMode` parameters in the NFS storage profile. Otherwise, the upgrade will invalidate the NFS mapping. For more information, see link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html-single/virtualization/index#virt-customizing-storage-profile_virt-creating-data-volumes[Customizing the storage profile].
diff --git a/documentation/modules/using-must-gather.adoc b/documentation/modules/using-must-gather.adoc
@@ -17,7 +17,7 @@ If you specify a non-existent resource in the filtered `must-gather` command, no
 .Prerequisites
 
 * You must be logged in to the {virt} cluster as a user with the `cluster-admin` role.
-* You must have the link:https://docs.openshift.com/container-platform/{ocp-version}/cli_reference/openshift_cli/getting-started-cli.html[{ocp} CLI (`oc`)] installed.
+* You must have the {ocp} CLI (`oc`) installed. For more information, see {ocp-doc}/cli_tools/openshift-cli-oc#cli-getting-started[Getting started with the {ocp-short}].
 
 .Collecting logs and CR information
 
diff --git a/documentation/modules/vddk-validator-containers.adoc b/documentation/modules/vddk-validator-containers.adoc
diff --git a/documentation/modules/virt-migration-workflow.adoc b/documentation/modules/virt-migration-workflow.adoc

Original file line number	Diff line number	Diff line change
@@ -19,7 +19,7 @@ Example: If a default rule contains the line `default valid_input = false` and y
`19`	`19`	`$ {oc} rsh <validation_pod>`
`20`	`20`	`----`
`21`	`21`
`22`		`-. Go to the OPA policies directory for your provider:`
	`22`	`+. Go to the Open Policy Agent (OPA) policies directory for your provider:`
`23`	`23`	`+`
`24`	`24`	`[source,terminal]`
`25`	`25`	`----`
Original file line number	Diff line number	Diff line change
`@@ -114,7 +114,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is`
`114`	`114`	`** To choose a different transfer network, select a different transfer network from the list.`
`115`	`115`	`** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click Networking > NetworkAttachmentDefinitions.`
`116`	`116`	`+`
`117`		`-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].`
	`117`	`+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].`
`118`	`118`
`119`	`119`	`** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].`
`120`	`120`
Original file line number	Diff line number	Diff line change
`@@ -123,7 +123,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is`
`123`	`123`	`** To choose a different transfer network, select a different transfer network from the list.`
`124`	`124`	`** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click Networking > NetworkAttachmentDefinitions.`
`125`	`125`	`+`
`126`		`-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].`
	`126`	`+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].`
`127`	`127`
`128`	`128`	`** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].`
`129`	`129`
`@@ -161,11 +161,11 @@ The Plan settings section of the page includes settings that you specified in`
`161`	`161`
`162`	`162`	`. Check the following item on the Plan settings section of the page:`
`163`	`163`
`164`		`-* Preserve CPU mode: Generally, the CPU model (type) for RHV VMs is set at the cluster level. However, the CPU model can be set at the VM level, which is called a custom CPU model.`
	`164`	`+* Preserve CPU mode: Generally, the CPU model (type) for {rhv-full} VMs is set at the cluster level. However, the CPU model can be set at the VM level, which is called a custom CPU model.`
`165`	`165`	`+`
`166`	`166`	`By default, MTV sets the CPU model on the destination cluster as follows: MTV preserves custom CPU settings for VMs that have them. For VMs without custom CPU settings, MTV does not set the CPU model. Instead, the CPU model is later set by OpenShift Virtualization.`
`167`	`167`	`+`
`168`		`-To preserve the cluster-level CPU model of your RHV VMs, do the following:`
	`168`	`+To preserve the cluster-level CPU model of your {rhv-full} VMs, do the following:`
`169`	`169`
`170`	`170`	`.. Click the {kebab}.`
`171`	`171`	`.. Toggle the Whether to preserve the CPU model switch.`