From 15b67f4022b2593bba054d8c92c7d16a6666d068 Mon Sep 17 00:00:00 2001 From: Richard Hoch Date: Mon, 1 Sep 2025 14:00:45 +0300 Subject: [PATCH] MTV-3225: Replacing links that contain attributes --- .../accessing-default-validation-rules.adoc | 2 +- documentation/modules/accessing-logs-cli.adoc | 2 +- .../modules/adding-hook-using-cli.adoc | 2 +- .../modules/adding-hook-using-ui.adoc | 2 +- .../modules/adding-source-provider.adoc | 2 +- documentation/modules/common-attributes.adoc | 1 + .../modules/creating-plan-wizard-290-cnv.adoc | 2 +- .../creating-plan-wizard-290-ostack.adoc | 2 +- .../modules/creating-plan-wizard-290-ova.adoc | 2 +- .../modules/creating-plan-wizard-290-rhv.adoc | 2 +- .../creating-plan-wizard-290-vmware.adoc | 2 +- .../modules/creating-validation-rule.adoc | 2 +- .../modules/creating-vddk-image.adoc | 7 +---- documentation/modules/error-messages.adoc | 2 +- .../modules/network-prerequisites.adoc | 2 +- .../modules/status-vms-warm-migration.adoc | 2 +- documentation/modules/storage-support.adoc | 4 +-- documentation/modules/upgrading-mtv-ui.adoc | 12 +++----- documentation/modules/using-must-gather.adoc | 2 +- .../modules/vddk-validator-containers.adoc | 28 +++++++++++-------- 20 files changed, 40 insertions(+), 42 deletions(-) diff --git a/documentation/modules/accessing-default-validation-rules.adoc b/documentation/modules/accessing-default-validation-rules.adoc index 13221a22775..360000846f6 100644 --- a/documentation/modules/accessing-default-validation-rules.adoc +++ b/documentation/modules/accessing-default-validation-rules.adoc @@ -20,7 +20,7 @@ Example: If a default rule contains the line `default valid_input = false` and y $ {oc} rsh ---- -. 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 index 1bac1465f35..bea0aaadf8c 100644 --- a/documentation/modules/accessing-logs-cli.adoc +++ b/documentation/modules/accessing-logs-cli.adoc @@ -19,7 +19,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} CLI]. .Procedure diff --git a/documentation/modules/adding-hook-using-cli.adoc b/documentation/modules/adding-hook-using-cli.adoc index 9fcf67b019d..a23b3677cd6 100644 --- a/documentation/modules/adding-hook-using-cli.adoc +++ b/documentation/modules/adding-hook-using-cli.adoc @@ -31,7 +31,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 index ee29dbe99c2..026ff1bad80 100644 --- a/documentation/modules/adding-hook-using-ui.adoc +++ b/documentation/modules/adding-hook-using-ui.adoc @@ -31,7 +31,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 index 61df3dc805c..77a66e27da0 100644 --- a/documentation/modules/adding-source-provider.adoc +++ b/documentation/modules/adding-source-provider.adoc @@ -93,7 +93,7 @@ ifdef::rhv[] endif::[] ifdef::dest_vmware,dest_rhv,dest_ostack,dest_ova,dest_cnv[] -* 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 index 70093a5512c..c625a7abfb1 100644 --- 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 index 0f865348942..6af43c45dec 100644 --- a/documentation/modules/creating-plan-wizard-290-cnv.adoc +++ b/documentation/modules/creating-plan-wizard-290-cnv.adoc @@ -115,7 +115,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 index 181bb0093d9..6d61389ac5d 100644 --- a/documentation/modules/creating-plan-wizard-290-ostack.adoc +++ b/documentation/modules/creating-plan-wizard-290-ostack.adoc @@ -115,7 +115,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 index 74768871455..bac514e6d69 100644 --- a/documentation/modules/creating-plan-wizard-290-ova.adoc +++ b/documentation/modules/creating-plan-wizard-290-ova.adoc @@ -115,7 +115,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 index 8d0de9155dc..464f565716d 100644 --- a/documentation/modules/creating-plan-wizard-290-rhv.adoc +++ b/documentation/modules/creating-plan-wizard-290-rhv.adoc @@ -124,7 +124,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-vmware.adoc b/documentation/modules/creating-plan-wizard-290-vmware.adoc index e9ef1633071..f5cb21ddb3a 100644 --- a/documentation/modules/creating-plan-wizard-290-vmware.adoc +++ b/documentation/modules/creating-plan-wizard-290-vmware.adoc @@ -131,7 +131,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 index 75bae00a827..6bdaef40fa5 100644 --- a/documentation/modules/creating-validation-rule.adoc +++ b/documentation/modules/creating-validation-rule.adoc @@ -40,7 +40,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 index e48e9e92b91..4d62bfc4206 100644 --- a/documentation/modules/creating-vddk-image.adoc +++ b/documentation/modules/creating-vddk-image.adoc @@ -25,7 +25,7 @@ Storing the VDDK image in a public registry might violate the {vmw} license term .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} image configured for bare metal. For more information, see {ocp-doc}/registry/setting-up-and-configuring-the-registry#configuring-registry-storage-baremetal[Configuring the registry for bare metal]. * `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. @@ -42,11 +42,6 @@ $ mkdir /tmp/ && cd /tmp/ . 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 index 2d4bb86ea4f..273e0359f88 100644 --- a/documentation/modules/error-messages.adoc +++ b/documentation/modules/error-messages.adoc @@ -19,6 +19,6 @@ To resolve this problem, delete some of the CBT snapshots from the VM and restar [id="unable-resize-disk-image_{context}"] == 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 index 26bc741d7cf..8635c4a493e 100644 --- a/documentation/modules/network-prerequisites.adoc +++ b/documentation/modules/network-prerequisites.adoc @@ -11,7 +11,7 @@ The following network 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/status-vms-warm-migration.adoc b/documentation/modules/status-vms-warm-migration.adoc index 29de363a953..a14897d3b4b 100644 --- a/documentation/modules/status-vms-warm-migration.adoc +++ b/documentation/modules/status-vms-warm-migration.adoc @@ -28,7 +28,7 @@ A VM can support up to 28 CBT snapshots. If the source VM has too many CBT snaps The precopy stage runs until the cutover stage is started manually or is scheduled to start. [id="status-vms-warm-migration-cutover_{context}"] -==Cutover stage +== Cutover stage The VMs are shut down during the cutover stage, and the remaining data is migrated. Data stored in RAM is not migrated. diff --git a/documentation/modules/storage-support.adoc b/documentation/modules/storage-support.adoc index a0d5ec16c38..a82cdcb891c 100644 --- a/documentation/modules/storage-support.adoc +++ b/documentation/modules/storage-support.adoc @@ -61,7 +61,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 + @@ -70,7 +70,7 @@ 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 storage profiles] for details on applying settings to a storage profile. ==== [NOTE] diff --git a/documentation/modules/upgrading-mtv-ui.adoc b/documentation/modules/upgrading-mtv-ui.adoc index 515079909e7..01ebd628e4f 100644 --- a/documentation/modules/upgrading-mtv-ui.adoc +++ b/documentation/modules/upgrading-mtv-ui.adoc @@ -15,10 +15,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[Updating installed Operators] 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 the update channel for an Operator] 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: @@ -45,12 +45,8 @@ If you set *Update approval* on the *Subscriptions* tab to *Automatic*, the upgr . If you set *Update approval* on the *Subscriptions* tab to *Manual*, approve the upgrade. + 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. +See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending Operator 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 index 21bb254de38..b20bd588e81 100644 --- a/documentation/modules/using-must-gather.adoc +++ b/documentation/modules/using-must-gather.adoc @@ -19,7 +19,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} CLI]. .Procedure diff --git a/documentation/modules/vddk-validator-containers.adoc b/documentation/modules/vddk-validator-containers.adoc index 48b0186cbf5..2601a27309f 100644 --- a/documentation/modules/vddk-validator-containers.adoc +++ b/documentation/modules/vddk-validator-containers.adoc @@ -4,40 +4,46 @@ :_content-type: REFERENCE [id="vddk-validator-containers_{context}"] -= VDDK validator containers need requests and limits += Requests and limits for VDDK validator containers -[role="_abstract"] -If you have the link:https://docs.openshift.com/container-platform/{ocp-version}/applications/quotas/quotas-setting-per-project.html[cluster or project resource quotas set], you must ensure that you have a sufficient quota for the {project-short} pods to perform the migration.  +When you set cluster or project resource quotas, be sure that you have a sufficient quota for the {project-short} pods to perform the migration.  -You can see the defaults, which you can override in the `ForkliftController` custom resource (CR), listed as follows. If necessary, you can adjust these defaults.  +For more information on creating, setting, and viewing quotas, see {ocp-doc}/building_applications/index#quotas[Quotas]. -These settings are highly dependent on your environment. If there are many migrations happening at once and the quotas are not set enough for the migrations, then the migrations can fail. This can also be correlated to the `MAX_VM_INFLIGHT` setting that determines how many VMs/disks are migrated at once. +[id="defaults-that-can-be-overridden-in-forklift-controller_{context}"] +== Defaults that can be overridden in the ForkliftController CR: -The following defaults can be overriden in the `ForkliftController` CR: +The defaults that are related to VDDK validator containers are listed as follows. You can override these defaults in the `ForkliftController` custom resource (CR). -* Defaults that affect both cold and warm migrations: +[NOTE] +==== +These settings are highly dependent on your environment. If there are many migrations happening at once and the quotas are not set high enough for the migrations, then the migrations can fail. + +Migration success or failure is also connected to the `MAX_VM_INFLIGHT` setting that determines how many VMs or disks are migrated at once. +==== + +* These defaults affect both cold and warm migrations: + -For cold migration, it is likely to be more resource intensive as it performs the disk copy. For warm migration, you could potentially reduce the requests. +Cold migration is likely to be more resource intensive because it copies the disks. For warm migration, you could potentially reduce the requests. ** virt_v2v_container_limits_cpu: `4000m` ** virt_v2v_container_limits_memory: `8Gi` ** virt_v2v_container_requests_cpu: `1000m` ** virt_v2v_container_requests_memory: `1Gi` + - [NOTE] ==== Cold and warm migration using `virt-v2v` can be resource-intensive. For more details, see link:https://libguestfs.org/virt-v2v.1.html#compute-power-and-ram[Compute power and RAM]. ==== -* Defaults that affect any migrations with hooks: +* These defaults affect all migrations with hooks: ** hooks_container_limits_cpu: `1000m` ** hooks_container_limits_memory: `1Gi` ** hooks_container_requests_cpu: `100m` ** hooks_container_requests_memory: `150Mi` -* Defaults that affect any OVA migrations: +* These defaults affect all Open Virtual Appliance (OVA) file migrations: ** ova_container_limits_cpu: `1000m` ** ova_container_limits_memory: `1Gi`