From 6929faf5441c2ad01dd693875d59fe824cd73c54 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Thu, 31 Oct 2024 19:06:58 +0200 Subject: [PATCH 1/7] Max concurrent virtual machine migrations Signed-off-by: RichardHoch --- .../master.adoc | 2 +- .../modules/configuring-mtv-operator.adoc | 10 ++++++++-- documentation/modules/max-concurrent-vms.adoc | 16 ++++++++++++++++ documentation/modules/mtv-settings.adoc | 19 +++++++++++++------ 4 files changed, 38 insertions(+), 9 deletions(-) create mode 100644 documentation/modules/max-concurrent-vms.adoc diff --git a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc index 125507d9dec..7d47b64fa3c 100644 --- a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc +++ b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc @@ -105,7 +105,7 @@ include::modules/installing-mtv-operator.adoc[leveloffset=+2] :mtv: include::modules/configuring-mtv-operator.adoc[leveloffset=+2] - +include::modules/max-concurrent-vms.adoc[leveloffset=+3] [id="migrating-vms-web-console_{context}"] == Migrating virtual machines by using the {ocp} web console diff --git a/documentation/modules/configuring-mtv-operator.adoc b/documentation/modules/configuring-mtv-operator.adoc index cfa66de78fc..244364285b6 100644 --- a/documentation/modules/configuring-mtv-operator.adoc +++ b/documentation/modules/configuring-mtv-operator.adoc @@ -8,7 +8,7 @@ You can configure all of the following settings of the {operator-name} by modifying the `ForkliftController` CR, or in the *Settings* section of the *Overview* page, unless otherwise indicated. -* Maximum number of virtual machines (VMs) per plan that can be migrated simultaneously. +* Maximum number of virtual machines (VMs) or disks per plan that {project-first} can migrate simultaneously. * How long `must gather` reports are retained before being automatically deleted. * CPU limit allocated to the main controller container. * Memory limit allocated to the main controller container. @@ -37,7 +37,13 @@ spec: |Label |Description |Default value |`controller_max_vm_inflight` -|The maximum number of VMs per plan that can be migrated simultaneously. +a|*Varies with provider as follows*: + +* {rhv-full}, {osp}, VMware warm migrations _or_ remote cold migrations: The maximum number of disks that {project-short} can transfer simultaneously. + +* OVA or VMware local cold migrations: The maximum number of VMs that {project-short} can migrate simultaneously. ++ +See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this setting. |`20` |`must_gather_api_cleanup_max_age` diff --git a/documentation/modules/max-concurrent-vms.adoc b/documentation/modules/max-concurrent-vms.adoc new file mode 100644 index 00000000000..d8f24a8172b --- /dev/null +++ b/documentation/modules/max-concurrent-vms.adoc @@ -0,0 +1,16 @@ + +// Module included in the following assemblies: +// +// * documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc + +:_content-type: PROCEDURE +[id="max-concurrent-vms_{context}"] += Configuring the controller_max_vm_inflight label + +For {rhv-full}, {osp}, VMware warm migrations _or_ remote cold migrations, the setting `controller_max_vm_inflight` (shown in the UI as *Max concurrent virtual machine migrations*) specifies the maximum number of _disks_ that {project-first} can transfer simultaneously. In these migrations, {project-short} migrates the disks in parallel. This means that if the combined number of disks that you want to migrate is greater than the value of the setting, additional disks must wait until the queue is free, without regard for whether a VM has finished being migrating. + +Example: If the value of the setting is 15, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks except for the 16th begin migrating at the same time. Once any of them has migrated, the 16th disk can be migrated, whether or not all the disks on VM A and VM B have finished migrating. + +However, for OVA or for local VMware local cold migrations, the setting specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. + +Example: If the value of the setting is 2, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks on VM C must wait until either all the disks on VM A or on VM B have finished migrating. \ No newline at end of file diff --git a/documentation/modules/mtv-settings.adoc b/documentation/modules/mtv-settings.adoc index 73c3d7b9dcd..3adb3c82ade 100644 --- a/documentation/modules/mtv-settings.adoc +++ b/documentation/modules/mtv-settings.adoc @@ -14,27 +14,33 @@ If you have Administrator privileges, you can access the *Overview* page and cha |Setting |Description |Default value |Max concurrent virtual machine migrations -|The maximum number of VMs per plan that can be migrated simultaneously +a|*Varies with provider as follows*: + +* {rhv-full}, {osp}, VMware warm migrations _or_ remote cold migrations: The maximum number of disks that {project-first} can transfer simultaneously. + +* OVA or VMware local cold migrations: The maximum number of VMs that {project-short} can migrate simultaneously. ++ +See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this setting. |20 |Must gather cleanup after (hours) -|The duration for retaining `must gather` reports before they are automatically deleted +|The duration for retaining `must gather` reports before they are automatically deleted. |Disabled |Controller main container CPU limit -|The CPU limit allocated to the main controller container +|The CPU limit allocated to the main controller container. |500 m |Controller main container Memory limit -|The memory limit allocated to the main controller container +|The memory limit allocated to the main controller container. |800 Mi |Precopy internal (minutes) -|The interval at which a new snapshot is requested before initiating a warm migration +|The interval at which a new snapshot is requested before initiating a warm migration. |60 |Snapshot polling interval (seconds) -|The frequency with which the system checks the status of snapshot creation or removal during a warm migration +|The frequency with which the system checks the status of snapshot creation or removal during a warm migration. |10 |=== @@ -44,3 +50,4 @@ If you have Administrator privileges, you can access the *Overview* page and cha . In the *Settings* list, click the Edit icon of the setting you want to change. . Choose a setting from the list. . Click *Save*. + From b0e59b974f2fcd9c4848bace4227696409bb22fa Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Sun, 24 Nov 2024 17:50:08 +0200 Subject: [PATCH 2/7] After Sharon --- documentation/modules/max-concurrent-vms.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/max-concurrent-vms.adoc b/documentation/modules/max-concurrent-vms.adoc index d8f24a8172b..e8df502be84 100644 --- a/documentation/modules/max-concurrent-vms.adoc +++ b/documentation/modules/max-concurrent-vms.adoc @@ -11,6 +11,6 @@ For {rhv-full}, {osp}, VMware warm migrations _or_ remote cold migrations, the s Example: If the value of the setting is 15, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks except for the 16th begin migrating at the same time. Once any of them has migrated, the 16th disk can be migrated, whether or not all the disks on VM A and VM B have finished migrating. -However, for OVA or for local VMware local cold migrations, the setting specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. +However, for OVA or for VMware local cold migrations, the setting specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. Example: If the value of the setting is 2, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks on VM C must wait until either all the disks on VM A or on VM B have finished migrating. \ No newline at end of file From b182fd72e6eda63eaa87961c85d8ff52436ff1eb Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Thu, 28 Nov 2024 15:12:06 +0200 Subject: [PATCH 3/7] After Sharon --- documentation/modules/configuring-mtv-operator.adoc | 4 ++-- documentation/modules/max-concurrent-vms.adoc | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/modules/configuring-mtv-operator.adoc b/documentation/modules/configuring-mtv-operator.adoc index 244364285b6..e8b8579d904 100644 --- a/documentation/modules/configuring-mtv-operator.adoc +++ b/documentation/modules/configuring-mtv-operator.adoc @@ -39,9 +39,9 @@ spec: |`controller_max_vm_inflight` a|*Varies with provider as follows*: -* {rhv-full}, {osp}, VMware warm migrations _or_ remote cold migrations: The maximum number of disks that {project-short} can transfer simultaneously. +* {rhv-full} migrations, {osp} migrations, VMware warm migrations, _or_ cold VMware migrations to a remote {ocp} cluster: The maximum number of disks that {project-short} can transfer simultaneously. -* OVA or VMware local cold migrations: The maximum number of VMs that {project-short} can migrate simultaneously. +* OVA migrations or cold VMware migrations using `virt-v2v` to a local {ocp} cluster: The maximum number of VMs that {project-short} can migrate simultaneously. + See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this setting. |`20` diff --git a/documentation/modules/max-concurrent-vms.adoc b/documentation/modules/max-concurrent-vms.adoc index e8df502be84..0980e9e11ab 100644 --- a/documentation/modules/max-concurrent-vms.adoc +++ b/documentation/modules/max-concurrent-vms.adoc @@ -7,10 +7,10 @@ [id="max-concurrent-vms_{context}"] = Configuring the controller_max_vm_inflight label -For {rhv-full}, {osp}, VMware warm migrations _or_ remote cold migrations, the setting `controller_max_vm_inflight` (shown in the UI as *Max concurrent virtual machine migrations*) specifies the maximum number of _disks_ that {project-first} can transfer simultaneously. In these migrations, {project-short} migrates the disks in parallel. This means that if the combined number of disks that you want to migrate is greater than the value of the setting, additional disks must wait until the queue is free, without regard for whether a VM has finished being migrating. +For {rhv-full} migrations, {osp} migrations, VMware warm migrations, _or_ cold VMware migrations to a remote {ocp} cluster the setting `controller_max_vm_inflight` (shown in the UI as *Max concurrent virtual machine migrations*) specifies the maximum number of _disks_ that {project-first} can transfer simultaneously. In these migrations, {project-short} migrates the disks in parallel. This means that if the combined number of disks that you want to migrate is greater than the value of the setting, additional disks must wait until the queue is free, without regard for whether a VM has finished migrating. Example: If the value of the setting is 15, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks except for the 16th begin migrating at the same time. Once any of them has migrated, the 16th disk can be migrated, whether or not all the disks on VM A and VM B have finished migrating. -However, for OVA or for VMware local cold migrations, the setting specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. +However, for OVA migrations or cold VMware migrations using `virt-v2v` to a local {ocp} cluster, the setting specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. Example: If the value of the setting is 2, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks on VM C must wait until either all the disks on VM A or on VM B have finished migrating. \ No newline at end of file From 463292f8feb2bb9c43e0e99ad2a47463366778fe Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Thu, 28 Nov 2024 15:59:48 +0200 Subject: [PATCH 4/7] After Sharon -- MTV Settings --- documentation/modules/mtv-settings.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/modules/mtv-settings.adoc b/documentation/modules/mtv-settings.adoc index 3adb3c82ade..603fe231989 100644 --- a/documentation/modules/mtv-settings.adoc +++ b/documentation/modules/mtv-settings.adoc @@ -16,9 +16,9 @@ If you have Administrator privileges, you can access the *Overview* page and cha |Max concurrent virtual machine migrations a|*Varies with provider as follows*: -* {rhv-full}, {osp}, VMware warm migrations _or_ remote cold migrations: The maximum number of disks that {project-first} can transfer simultaneously. +* {rhv-full} migrations, {osp} migrations, VMware warm migrations, _or_ cold VMware migrations to a remote {ocp} cluster: The maximum number of disks that {project-short} can transfer simultaneously. -* OVA or VMware local cold migrations: The maximum number of VMs that {project-short} can migrate simultaneously. +* OVA migrations or cold VMware migrations using `virt-v2v` to a local {ocp} cluster: The maximum number of VMs that {project-short} can migrate simultaneously. + See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this setting. |20 From b8b7f4f4dae3a5c22b5fcc3722f7633b6f116ed4 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Sun, 5 Jan 2025 17:42:04 +0200 Subject: [PATCH 5/7] After QE --- documentation/modules/configuring-mtv-operator.adoc | 10 ++++++++-- documentation/modules/mtv-settings.adoc | 10 ++++++++-- 2 files changed, 16 insertions(+), 4 deletions(-) diff --git a/documentation/modules/configuring-mtv-operator.adoc b/documentation/modules/configuring-mtv-operator.adoc index e8b8579d904..5fe501393e3 100644 --- a/documentation/modules/configuring-mtv-operator.adoc +++ b/documentation/modules/configuring-mtv-operator.adoc @@ -39,9 +39,15 @@ spec: |`controller_max_vm_inflight` a|*Varies with provider as follows*: -* {rhv-full} migrations, {osp} migrations, VMware warm migrations, _or_ cold VMware migrations to a remote {ocp} cluster: The maximum number of disks that {project-short} can transfer simultaneously. +* For {rhv-full} migrations and {osp} migrations: The maximum number of disks that {project-short} can transfer simultaneously. +* For OVA migrations: The maximum number of VMs that {project-short} can migrate simultaneously. +* For VMware simultaneous migration: +** Cold migration: -* OVA migrations or cold VMware migrations using `virt-v2v` to a local {ocp} cluster: The maximum number of VMs that {project-short} can migrate simultaneously. +*** To local {virt}: VMs for each ESXi host that can migrate simultaneously. +*** To remote {virt}: Disks for each ESXi host that can migrate simultaneously. + +** Warm migration: Disks for each ESXi host that can migrate simultaneously. + See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this setting. |`20` diff --git a/documentation/modules/mtv-settings.adoc b/documentation/modules/mtv-settings.adoc index 603fe231989..57c517d9e94 100644 --- a/documentation/modules/mtv-settings.adoc +++ b/documentation/modules/mtv-settings.adoc @@ -16,9 +16,15 @@ If you have Administrator privileges, you can access the *Overview* page and cha |Max concurrent virtual machine migrations a|*Varies with provider as follows*: -* {rhv-full} migrations, {osp} migrations, VMware warm migrations, _or_ cold VMware migrations to a remote {ocp} cluster: The maximum number of disks that {project-short} can transfer simultaneously. +* For {rhv-full} migrations and {osp} migrations: The maximum number of disks that {project-short} can transfer simultaneously. +* For OVA migrations: The maximum number of VMs that {project-short} can migrate simultaneously. +* For VMware simultaneous migration: +** Cold migration: -* OVA migrations or cold VMware migrations using `virt-v2v` to a local {ocp} cluster: The maximum number of VMs that {project-short} can migrate simultaneously. +*** To local {virt}: VMs for each ESXi host that can migrate simultaneously. +*** To remote {virt}: Disks for each ESXi host that can migrate simultaneously. + +** Warm migration: Disks for each ESXi host that can migrate simultaneously. + See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this setting. |20 From 947324fd6802f069ee4742e3516643bac3968cce Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Sun, 12 Jan 2025 13:58:28 +0200 Subject: [PATCH 6/7] After Martin --- documentation/modules/configuring-mtv-operator.adoc | 6 +++--- documentation/modules/max-concurrent-vms.adoc | 4 ++-- documentation/modules/mtv-settings.adoc | 6 +++--- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/documentation/modules/configuring-mtv-operator.adoc b/documentation/modules/configuring-mtv-operator.adoc index 5fe501393e3..e8f5d223a13 100644 --- a/documentation/modules/configuring-mtv-operator.adoc +++ b/documentation/modules/configuring-mtv-operator.adoc @@ -39,9 +39,9 @@ spec: |`controller_max_vm_inflight` a|*Varies with provider as follows*: -* For {rhv-full} migrations and {osp} migrations: The maximum number of disks that {project-short} can transfer simultaneously. -* For OVA migrations: The maximum number of VMs that {project-short} can migrate simultaneously. -* For VMware simultaneous migration: +* For {rhv-full} migrations or {osp} migrations: The maximum number of disks that {project-short} can transfer simultaneously. +* For OVA migrations or {virt} migrations: The maximum number of VMs that {project-short} can migrate simultaneously. +* For VMware migrations: ** Cold migration: *** To local {virt}: VMs for each ESXi host that can migrate simultaneously. diff --git a/documentation/modules/max-concurrent-vms.adoc b/documentation/modules/max-concurrent-vms.adoc index 0980e9e11ab..bbf29779275 100644 --- a/documentation/modules/max-concurrent-vms.adoc +++ b/documentation/modules/max-concurrent-vms.adoc @@ -7,10 +7,10 @@ [id="max-concurrent-vms_{context}"] = Configuring the controller_max_vm_inflight label -For {rhv-full} migrations, {osp} migrations, VMware warm migrations, _or_ cold VMware migrations to a remote {ocp} cluster the setting `controller_max_vm_inflight` (shown in the UI as *Max concurrent virtual machine migrations*) specifies the maximum number of _disks_ that {project-first} can transfer simultaneously. In these migrations, {project-short} migrates the disks in parallel. This means that if the combined number of disks that you want to migrate is greater than the value of the setting, additional disks must wait until the queue is free, without regard for whether a VM has finished migrating. +For {rhv-full} migrations, {osp} migrations, VMware warm migrations, or cold VMware migrations to a remote {ocp} cluster the setting `controller_max_vm_inflight` (shown in the UI as *Max concurrent virtual machine migrations*) specifies the maximum number of _disks_ that {project-first} can transfer simultaneously. In these migrations, {project-short} migrates the disks in parallel. This means that if the combined number of disks that you want to migrate is greater than the value of the setting, additional disks must wait until the queue is free, without regard for whether a VM has finished migrating. Example: If the value of the setting is 15, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks except for the 16th begin migrating at the same time. Once any of them has migrated, the 16th disk can be migrated, whether or not all the disks on VM A and VM B have finished migrating. -However, for OVA migrations or cold VMware migrations using `virt-v2v` to a local {ocp} cluster, the setting specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. +However, for OVA migrations, {virt} migrations, or cold VMware migrations using `virt-v2v` to a local {ocp} cluster, the setting specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. Example: If the value of the setting is 2, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks on VM C must wait until either all the disks on VM A or on VM B have finished migrating. \ No newline at end of file diff --git a/documentation/modules/mtv-settings.adoc b/documentation/modules/mtv-settings.adoc index 57c517d9e94..5e84e74be81 100644 --- a/documentation/modules/mtv-settings.adoc +++ b/documentation/modules/mtv-settings.adoc @@ -16,9 +16,9 @@ If you have Administrator privileges, you can access the *Overview* page and cha |Max concurrent virtual machine migrations a|*Varies with provider as follows*: -* For {rhv-full} migrations and {osp} migrations: The maximum number of disks that {project-short} can transfer simultaneously. -* For OVA migrations: The maximum number of VMs that {project-short} can migrate simultaneously. -* For VMware simultaneous migration: +* For {rhv-full} migrations or {osp} migrations: The maximum number of disks that {project-short} can transfer simultaneously. +* For OVA migrations or {virt} migrations: The maximum number of VMs that {project-short} can migrate simultaneously. +* For VMware migrations: ** Cold migration: *** To local {virt}: VMs for each ESXi host that can migrate simultaneously. From cb5e0b973a1ba2bb265fa6bc284a87a6e97cda1f Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Mon, 13 Jan 2025 16:08:57 +0200 Subject: [PATCH 7/7] Update on VMs --- .../modules/configuring-mtv-operator.adoc | 8 ++++---- documentation/modules/max-concurrent-vms.adoc | 19 +++++++++++++++---- documentation/modules/mtv-settings.adoc | 7 ++++--- 3 files changed, 23 insertions(+), 11 deletions(-) diff --git a/documentation/modules/configuring-mtv-operator.adoc b/documentation/modules/configuring-mtv-operator.adoc index e8f5d223a13..27fd955c1e1 100644 --- a/documentation/modules/configuring-mtv-operator.adoc +++ b/documentation/modules/configuring-mtv-operator.adoc @@ -39,9 +39,9 @@ spec: |`controller_max_vm_inflight` a|*Varies with provider as follows*: -* For {rhv-full} migrations or {osp} migrations: The maximum number of disks that {project-short} can transfer simultaneously. -* For OVA migrations or {virt} migrations: The maximum number of VMs that {project-short} can migrate simultaneously. -* For VMware migrations: +* For all migrations except OVA or VMware migrations: The maximum number of disks that {project-short} can transfer simultaneously. +* For OVA migrations: The maximum number of VMs that {project-short} can migrate simultaneously. +* For VMware migrations, the label has the following meanings: ** Cold migration: *** To local {virt}: VMs for each ESXi host that can migrate simultaneously. @@ -49,7 +49,7 @@ a|*Varies with provider as follows*: ** Warm migration: Disks for each ESXi host that can migrate simultaneously. + -See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this setting. +See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this label. |`20` |`must_gather_api_cleanup_max_age` diff --git a/documentation/modules/max-concurrent-vms.adoc b/documentation/modules/max-concurrent-vms.adoc index bbf29779275..288372bf534 100644 --- a/documentation/modules/max-concurrent-vms.adoc +++ b/documentation/modules/max-concurrent-vms.adoc @@ -7,10 +7,21 @@ [id="max-concurrent-vms_{context}"] = Configuring the controller_max_vm_inflight label -For {rhv-full} migrations, {osp} migrations, VMware warm migrations, or cold VMware migrations to a remote {ocp} cluster the setting `controller_max_vm_inflight` (shown in the UI as *Max concurrent virtual machine migrations*) specifies the maximum number of _disks_ that {project-first} can transfer simultaneously. In these migrations, {project-short} migrates the disks in parallel. This means that if the combined number of disks that you want to migrate is greater than the value of the setting, additional disks must wait until the queue is free, without regard for whether a VM has finished migrating. +The meaning of the `controller_max_vm_inflight` label, which is shown in the UI as *Max concurrent virtual machine migrations*, varies by the source provider of the migration -Example: If the value of the setting is 15, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks except for the 16th begin migrating at the same time. Once any of them has migrated, the 16th disk can be migrated, whether or not all the disks on VM A and VM B have finished migrating. +* For all migrations except OVA or VMware migrations, the label specifies the maximum number of _disks_ that {project-first} can transfer simultaneously. In these migrations, {project-short} migrates the disks in parallel. This means that if the combined number of disks that you want to migrate is greater than the value of the setting, additional disks must wait until the queue is free, without regard for whether a VM has finished migrating. ++ +Example: If the value of the label is 15, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks except for the 16th begin migrating at the same time. Once any of them has migrated, the 16th disk can be migrated, whether or not all the disks on VM A and VM B have finished migrating. -However, for OVA migrations, {virt} migrations, or cold VMware migrations using `virt-v2v` to a local {ocp} cluster, the setting specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. +* For OVA migrations, the label specifies the maximum number of _VMs_ that {project-short} can migrate simultaneously, meaning that all additional disks must wait until at least one VM has been completely migrated. ++ +Example: If the value of the label is 2, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks on VM C must wait until either all the disks on VM A or on VM B have finished migrating. -Example: If the value of the setting is 2, and VM A has 5 disks, VM B has 5 disks, and VM C has 6 disks, all the disks on VM C must wait until either all the disks on VM A or on VM B have finished migrating. \ No newline at end of file +* For VMware migrations, the label has the following meanings: + +** Cold migration: + +*** To local {virt}: VMs for each ESXi host that can migrate simultaneously. +*** To remote {virt}: Disks for each ESXi host that can migrate simultaneously. + +** Warm migration: Disks for each ESXi host that can migrate simultaneously. \ No newline at end of file diff --git a/documentation/modules/mtv-settings.adoc b/documentation/modules/mtv-settings.adoc index 5e84e74be81..2b03f9e389a 100644 --- a/documentation/modules/mtv-settings.adoc +++ b/documentation/modules/mtv-settings.adoc @@ -16,9 +16,9 @@ If you have Administrator privileges, you can access the *Overview* page and cha |Max concurrent virtual machine migrations a|*Varies with provider as follows*: -* For {rhv-full} migrations or {osp} migrations: The maximum number of disks that {project-short} can transfer simultaneously. -* For OVA migrations or {virt} migrations: The maximum number of VMs that {project-short} can migrate simultaneously. -* For VMware migrations: +* For all migrations except OVA or VMware migrations: The maximum number of disks that {project-short} can transfer simultaneously. +* For OVA migrations: The maximum number of VMs that {project-short} can migrate simultaneously. +* For VMware migrations, the setting has the following meanings:: ** Cold migration: *** To local {virt}: VMs for each ESXi host that can migrate simultaneously. @@ -26,6 +26,7 @@ a|*Varies with provider as follows*: ** Warm migration: Disks for each ESXi host that can migrate simultaneously. + ++ See xref:max-concurrent-vms_{context}[Configuring the controller_max_vm_inflight label] for a detailed explanation of this setting. |20