From 6ad47db6ebb46432de60cef2f9698bd0dedcf673 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Wed, 13 Nov 2024 15:11:36 +0200 Subject: [PATCH 1/9] start Signed-off-by: RichardHoch --- .../master.adoc | 102 +++++++----------- ....adoc => creating-migration-plan-2-8.adoc} | 0 2 files changed, 41 insertions(+), 61 deletions(-) rename documentation/modules/{creating-migration-plan-2-6-3.adoc => creating-migration-plan-2-8.adoc} (100%) diff --git a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc index fa3510ab10d..58c52e002be 100644 --- a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc +++ b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc @@ -103,87 +103,68 @@ include::modules/installing-mtv-operator.adoc[leveloffset=+2] include::modules/configuring-mtv-operator.adoc[leveloffset=+2] +[id="migrating-vms-mtv-ui_{context}"] +=== Migrating virtual machines using the MTV user interface -[id="migrating-vms-web-console_{context}"] -== Migrating virtual machines by using the {ocp} web console - -You can migrate virtual machines (VMs) by using the {ocp} web console to: - -. xref:adding-source-providers[Create source providers] -. xref:adding-destination-providers[Create destination providers] -. xref:creating-migration-plans-ui[Create migration plans] - -[IMPORTANT] -==== -You must ensure that all xref:prerequisites_{context}[prerequisites] are met. - -VMware only: You must have the minimal set of xref:vmware-privileges_{context}[VMware privileges]. - -VMware only: Creating a xref:creating-vddk-image_{context}[VMware Virtual Disk Development Kit (VDDK)] image will increase migration speed. -==== - -include::modules/mtv-ui.adoc[leveloffset=+2] -include::modules/mtv-overview-page.adoc[leveloffset=+2] -include::modules/mtv-settings.adoc[leveloffset=+2] - -[id="adding-providers"] -=== Adding providers - -You can add source providers and destination providers for a virtual machine migration by using the {ocp} web console. - -[id="adding-source-providers"] -==== Adding source providers - -You can use {project-short} to migrate VMs from the following source providers: +You can use the {project-short} user interface to migrate VMs from the following providers: * VMware vSphere -* {rhv-full} +* {rhv-full} ({rhv-short}) * {osp} * Open Virtual Appliances (OVAs) that were created by VMware vSphere -* {virt} +* Remote {virt} clusters -You can add a source provider by using the {ocp} web console. +==== +// ANDY: Now we continue with the provider A-Z sections :!mtv: :context: vmware :vmware: -include::modules/adding-source-provider.adoc[leveloffset=+4] -include::modules/selecting-migration-network-for-vmware-source-provider.adoc[leveloffset=+5] -:!vmware: + +[id="migrating-vmware-ui"] +==== Migrating virtual machines from VMvSphere +// ANDY: VM prerequisites and provider instructions will go here + +include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] + +:vmware: + +// ANDY: Now RHV +==== Migrating virtual machines from RHV + :context: rhv :rhv: -include::modules/adding-source-provider.adoc[leveloffset=+4] +include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] :!rhv: + +// ANDY: Now OpenStack +==== Migrating virtual machines from OpenStack + :context: ostack :ostack: -include::modules/adding-source-provider.adoc[leveloffset=+4] +include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] :!ostack: + +// ANDY: Now OVA +==== Migrating virtual machines from OVA + :context: ova :ova: -include::modules/adding-source-provider.adoc[leveloffset=+4] +include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] :!ova: -:context: cnv -:cnv: -include::modules/adding-source-provider.adoc[leveloffset=+4] -:cnv!: -:context: mtv +:context: dest_ova -[id="adding-destination-providers"] -==== Adding destination providers +// ANDY: Now CNV +==== Migrating virtual machines from CNV -You can add a {virt} destination provider by using the {ocp} web console. +:context: cnv +:cnv: +include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] +:!cnv: -:mtv!: -:context: cnv2 -:cnv2: -include::modules/adding-source-provider.adoc[leveloffset=+4] -:cnv!: -:context: mtv -include::modules/selecting-migration-network-for-virt-provider.adoc[leveloffset=+4] +// ANDY: That's it for this PR. -// include::modules/creating-network-mapping.adoc[leveloffset=+2] -// include::modules/creating-storage-mapping.adoc[leveloffset=+2] [id="creating-migration-plans-ui"] === Creating migration plans @@ -192,8 +173,7 @@ You can create a migration plan by using the {ocp} web console to specify a sour For your convenience, there are two procedures to create migration plans, starting with either a source provider or with specific VMs: -* To start with a source provider, see xref:creating-migration-plan-2-6-3_provider[Creating a migration plan starting with a source provider]. -* To start with specific VMs, see xref:creating-migration-plan-2-6-3_vms[Creating a migration plan starting with specific VMs]. + [WARNING] ==== @@ -208,12 +188,12 @@ include::modules/snip_plan-limits.adoc[] :context: provider :provider: -include::modules/creating-migration-plan-2-6-3.adoc[leveloffset=+3] +include::modules/creating-migration-plan-2-8.adoc[leveloffset=+3] :provider!: :context: vms :vms: -include::modules/creating-migration-plan-2-6-3.adoc[leveloffset=+3] +include::modules/creating-migration-plan-2-8.adoc[leveloffset=+3] :vms!: :context: mtv diff --git a/documentation/modules/creating-migration-plan-2-6-3.adoc b/documentation/modules/creating-migration-plan-2-8.adoc similarity index 100% rename from documentation/modules/creating-migration-plan-2-6-3.adoc rename to documentation/modules/creating-migration-plan-2-8.adoc From df74ecfb12d52594ecc2e0396ba415d843d97323 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Thu, 14 Nov 2024 16:16:12 +0200 Subject: [PATCH 2/9] Creating migration plans per provider Signed-off-by: RichardHoch --- .../master.adoc | 84 ++++++++++--------- 1 file changed, 46 insertions(+), 38 deletions(-) diff --git a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc index 58c52e002be..00af016d9cc 100644 --- a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc +++ b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc @@ -103,6 +103,15 @@ include::modules/installing-mtv-operator.adoc[leveloffset=+2] include::modules/configuring-mtv-operator.adoc[leveloffset=+2] +[id="migrating-vms-ocp-web-console_{context}"] +== Migrating virtual machines by using the {ocp} web console + +You can migrate virtual machines (VMs) by using the {project-short} user interface, which is located in the *Virtualization* section of the {ocp} web console. + +include::modules/mtv-ui.adoc[leveloffset=+2] +include::modules/mtv-overview-page.adoc[leveloffset=+3] +include::modules/mtv-settings.adoc[leveloffset=+3] + [id="migrating-vms-mtv-ui_{context}"] === Migrating virtual machines using the MTV user interface @@ -114,35 +123,53 @@ You can use the {project-short} user interface to migrate VMs from the following * Open Virtual Appliances (OVAs) that were created by VMware vSphere * Remote {virt} clusters -==== - // ANDY: Now we continue with the provider A-Z sections :!mtv: :context: vmware :vmware: [id="migrating-vmware-ui"] -==== Migrating virtual machines from VMvSphere +==== Migrating virtual machines from VMware vSphere // ANDY: VM prerequisites and provider instructions will go here include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] -:vmware: +include::modules/running-migration-plan.adoc[leveloffset=+4] + +include::modules/migration-plan-options-ui.adoc[leveloffset=+4] + +include::modules/canceling-migration-ui.adoc[leveloffset=+4] + +:!vmware: // ANDY: Now RHV -==== Migrating virtual machines from RHV +==== Migrating virtual machines from {rhv-full} :context: rhv :rhv: include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] + +include::modules/running-migration-plan.adoc[leveloffset=+4] + +include::modules/migration-plan-options-ui.adoc[leveloffset=+4] + +include::modules/canceling-migration-ui.adoc[leveloffset=+4] + :!rhv: // ANDY: Now OpenStack -==== Migrating virtual machines from OpenStack +==== Migrating virtual machines from {ocp} :context: ostack :ostack: include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] + +include::modules/running-migration-plan.adoc[leveloffset=+4] + +include::modules/migration-plan-options-ui.adoc[leveloffset=+4] + +include::modules/canceling-migration-ui.adoc[leveloffset=+4] + :!ostack: // ANDY: Now OVA @@ -151,58 +178,39 @@ include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] :context: ova :ova: include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] + +include::modules/running-migration-plan.adoc[leveloffset=+4] + +include::modules/migration-plan-options-ui.adoc[leveloffset=+4] + +include::modules/canceling-migration-ui.adoc[leveloffset=+4] + :!ova: :context: dest_ova // ANDY: Now CNV -==== Migrating virtual machines from CNV +==== Migrating virtual machines from {virt} :context: cnv :cnv: include::modules/creating-migration-plan-2-8.adoc[leveloffset=+4] -:!cnv: - - -// ANDY: That's it for this PR. - - -[id="creating-migration-plans-ui"] -=== Creating migration plans -You can create a migration plan by using the {ocp} web console to specify a source provider, the virtual machines (VMs) you want to migrate, and other plan details. +include::modules/running-migration-plan.adoc[leveloffset=+4] -For your convenience, there are two procedures to create migration plans, starting with either a source provider or with specific VMs: +include::modules/migration-plan-options-ui.adoc[leveloffset=+4] +include::modules/canceling-migration-ui.adoc[leveloffset=+4] +:!cnv: -[WARNING] -==== -Virtual machines with guest initiated storage connections, such as Internet Small Computer Systems Interface (iSCSI) connections or Network File System (NFS) mounts, are not handled by {project-short} and could require additional planning before or reconfiguration after the migration. - -This is to ensure that no issues arise due to the addition or newly migrated VM accessing this storage. -==== - -include::modules/snip_plan-limits.adoc[] - -:mtv!: -:context: provider -:provider: -include::modules/creating-migration-plan-2-8.adoc[leveloffset=+3] +// ANDY: That's it for this PR. -:provider!: -:context: vms -:vms: -include::modules/creating-migration-plan-2-8.adoc[leveloffset=+3] -:vms!: :context: mtv :mtv: -include::modules/running-migration-plan.adoc[leveloffset=+2] -include::modules/migration-plan-options-ui.adoc[leveloffset=+2] -include::modules/canceling-migration-ui.adoc[leveloffset=+2] [id="migrating-virtual-machines-from-the-command-line_{context}"] == Migrating virtual machines from the command line From a3ae3a4da80de8f248678713437304e369f955d4 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Sun, 17 Nov 2024 12:03:06 +0200 Subject: [PATCH 3/9] Changed optional steps to INPORTANT notes, rather than sub-steps Signed-off-by: RichardHoch --- .../modules/creating-migration-plan-2-8.adoc | 55 +++++++++++-------- 1 file changed, 31 insertions(+), 24 deletions(-) diff --git a/documentation/modules/creating-migration-plan-2-8.adoc b/documentation/modules/creating-migration-plan-2-8.adoc index f6ff269dc3f..ff8353e4dea 100644 --- a/documentation/modules/creating-migration-plan-2-8.adoc +++ b/documentation/modules/creating-migration-plan-2-8.adoc @@ -1,11 +1,19 @@ // * documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc :_mod-docs-content-type: PROCEDURE -[id="creating-migration-plan-2-6-3_{context}"] -ifdef::provider[] -= Creating a migration plan starting with a source provider +[id="creating-migration-plan-2-8_{context}"] += Creating a migration plan -You can create a migration plan based on a source provider, starting on the *Plans for virtualization* page. Note the specific options for migrations from VMware or {rhv-short} providers. +You can create a migration plan by using the {ocp} web console to specify a source provider, the virtual machines (VMs) you want to migrate, and other plan details. + +[WARNING] +==== +Virtual machines with guest initiated storage connections, such as Internet Small Computer Systems Interface (iSCSI) connections or Network File System (NFS) mounts, are not handled by {project-short} and could require additional planning before or reconfiguration after the migration. + +This is to ensure that no issues arise due to the addition or newly migrated VM accessing this storage. +==== + +include::snip_plan-limits.adoc[] .Procedure @@ -16,21 +24,6 @@ The *Create migration plan* wizard opens to the *Select source provider* interfa + The *Select virtual machines* interface opens. . Select the VMs you want to migrate and click *Next*. -endif::[] - -ifdef::vms[] -= Creating a migration plan starting with specific VMs - -You can create a migration plan based on specific VMs, starting on the *Providers for virtualization* page. Note the specific options for migrations from VMware or {rhv-short} providers. - -.Procedure - -. In the {ocp} web console, click *Providers for virtualization*. -. In the row of the appropriate source provider, click *VMs*. -+ -The *Virtual Machines* tab opens. -. Select the VMs you want to migrate and click *Create migration plan*. -endif::[] + The *Create migration plan* pane opens. It displays the source provider's name and suggestions for a target provider and namespace, a network map, and a storage map. . Enter the *Plan name*. @@ -40,7 +33,11 @@ The *Create migration plan* pane opens. It displays the source provider's name a + {project-short} validates the migration plan and the *Plan details* page opens, indicating whether the plan is ready for use or contains an error. The details of the plan are listed, and you can edit the items you filled in on the previous page. If you make any changes, {project-short} validates the plan again. -. VMware source providers only (All optional): +ifdef::vmware[] ++ +[IMPORTANT] +==== +Check the following VMware-specific items. All are optional, but need special attention: * *Preserving static IPs of VMs*: By default, virtual network interface controllers (vNICs) change during the migration process. As a result, vNICs that are configured with a static IP linked to the interface name in the guest VM lose their IP. To avoid this, click the Edit icon next to *Preserve static IPs* and toggle the *Whether to preserve the static IPs* switch in the window that opens. Then click *Save*. + @@ -55,16 +52,26 @@ To specify a different root device, in the *Settings* section, click the Edit ic {project-short} uses the following format for disk location: `/dev/sd`. For example, if the second disk is the root device and the operating system is on the disk's second partition, the format would be: `/dev/sdb2`. After you enter the boot device, click *Save*. + If the conversion fails because the boot device provided is incorrect, it is possible to get the correct information by looking at the conversion pod logs. +==== -. {rhv-short} source providers only (Optional): +endif::[] +ifdef::rhv[] ++ +[IMPORTANT] +==== +Check the following {rhv-short}-specific items. All are optional, but need special attention: * *Preserving the CPU model of VMs that are migrated from {rhv-short}*: Generally, the CPU model (type) for {rhv-short} VMs is set at the cluster level, but it can be set at the VM level, which is called a custom CPU model. By default, {project-short} sets the CPU model on the destination cluster as follows: {project-short} preserves custom CPU settings for VMs that have them, but, for VMs without custom CPU settings, {project-short} does not set the CPU model. Instead, the CPU model is later set by {virt}. + To preserve the cluster-level CPU model of your {rhv-short} VMs, in the *Settings* section, click the Edit icon next to *Preserve CPU model*. Toggle the *Whether to preserve the CPU model* switch, and then click *Save*. +==== +endif::[] -. If the plan is valid, +. If your plan is valid: .. You can run the plan now by clicking *Start migration*. -.. You can run the plan later by selecting it on the *Plans for virtualization* page and following the procedure in xref:running-migration-plan_mtv[Running a migration plan]. -+ +.. You can run the plan later by selecting it on the *Plans for virtualization* page and following the procedure in xref:running-migration-plan_{context}[Running a migration plan]. + +ifdef::vmware[] include::snip_vmware-name-change.adoc[] +endif::[] From 122b71e6a2c4b5b01b82e98d91ef0b8f90276859 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Sun, 17 Nov 2024 15:40:19 +0200 Subject: [PATCH 4/9] formatting Signed-off-by: RichardHoch --- .../doc-Migration_Toolkit_for_Virtualization/master.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc index 00af016d9cc..bc307e96a17 100644 --- a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc +++ b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc @@ -158,7 +158,7 @@ include::modules/canceling-migration-ui.adoc[leveloffset=+4] :!rhv: // ANDY: Now OpenStack -==== Migrating virtual machines from {ocp} +==== Migrating virtual machines from {osp} :context: ostack :ostack: From 5fc8f6a8faaac8bd66e6cbc287feb69eb5c5d047 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Sun, 24 Nov 2024 16:02:33 +0200 Subject: [PATCH 5/9] after Nunzy --- .../master.adoc | 4 ++-- .../modules/creating-migration-plan-2-8.adoc | 12 ++++++------ 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc index bc307e96a17..17a1ddd9b63 100644 --- a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc +++ b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc @@ -106,7 +106,7 @@ include::modules/configuring-mtv-operator.adoc[leveloffset=+2] [id="migrating-vms-ocp-web-console_{context}"] == Migrating virtual machines by using the {ocp} web console -You can migrate virtual machines (VMs) by using the {project-short} user interface, which is located in the *Virtualization* section of the {ocp} web console. +Use the {project-short} user interface to migrate virtual machines (VMs). It is located in the *Virtualization* section of the {ocp} web console. include::modules/mtv-ui.adoc[leveloffset=+2] include::modules/mtv-overview-page.adoc[leveloffset=+3] @@ -115,7 +115,7 @@ include::modules/mtv-settings.adoc[leveloffset=+3] [id="migrating-vms-mtv-ui_{context}"] === Migrating virtual machines using the MTV user interface -You can use the {project-short} user interface to migrate VMs from the following providers: +Use the {project-short} user interface to migrate VMs from the following providers: * VMware vSphere * {rhv-full} ({rhv-short}) diff --git a/documentation/modules/creating-migration-plan-2-8.adoc b/documentation/modules/creating-migration-plan-2-8.adoc index ff8353e4dea..1717ceb38d6 100644 --- a/documentation/modules/creating-migration-plan-2-8.adoc +++ b/documentation/modules/creating-migration-plan-2-8.adoc @@ -4,7 +4,7 @@ [id="creating-migration-plan-2-8_{context}"] = Creating a migration plan -You can create a migration plan by using the {ocp} web console to specify a source provider, the virtual machines (VMs) you want to migrate, and other plan details. +Use the {ocp} web console to create a migration plan. Specify the source provider, the virtual machines (VMs) you want to migrate, and other plan details. [WARNING] ==== @@ -37,7 +37,7 @@ ifdef::vmware[] + [IMPORTANT] ==== -Check the following VMware-specific items. All are optional, but need special attention: +Check the following optional items related to VMware: * *Preserving static IPs of VMs*: By default, virtual network interface controllers (vNICs) change during the migration process. As a result, vNICs that are configured with a static IP linked to the interface name in the guest VM lose their IP. To avoid this, click the Edit icon next to *Preserve static IPs* and toggle the *Whether to preserve the static IPs* switch in the window that opens. Then click *Save*. + @@ -59,7 +59,7 @@ ifdef::rhv[] + [IMPORTANT] ==== -Check the following {rhv-short}-specific items. All are optional, but need special attention: +Check the following optional items related to {rhv-short}. * *Preserving the CPU model of VMs that are migrated from {rhv-short}*: Generally, the CPU model (type) for {rhv-short} VMs is set at the cluster level, but it can be set at the VM level, which is called a custom CPU model. By default, {project-short} sets the CPU model on the destination cluster as follows: {project-short} preserves custom CPU settings for VMs that have them, but, for VMs without custom CPU settings, {project-short} does not set the CPU model. Instead, the CPU model is later set by {virt}. @@ -68,9 +68,9 @@ To preserve the cluster-level CPU model of your {rhv-short} VMs, in the *Setting ==== endif::[] -. If your plan is valid: -.. You can run the plan now by clicking *Start migration*. -.. You can run the plan later by selecting it on the *Plans for virtualization* page and following the procedure in xref:running-migration-plan_{context}[Running a migration plan]. +. If your plan is valid, you can do one of the following: +.. Run the plan now by clicking *Start migration*. +.. Run the plan later by selecting it on the *Plans for virtualization* page and following the procedure in xref:running-migration-plan_{context}[Running a migration plan]. ifdef::vmware[] include::snip_vmware-name-change.adoc[] From bbb371125115b1b8355c2533d7587501e9caec28 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Sun, 24 Nov 2024 16:05:42 +0200 Subject: [PATCH 6/9] after Nunzy --- documentation/modules/creating-migration-plan-2-8.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/creating-migration-plan-2-8.adoc b/documentation/modules/creating-migration-plan-2-8.adoc index 1717ceb38d6..d35c2a0fbf7 100644 --- a/documentation/modules/creating-migration-plan-2-8.adoc +++ b/documentation/modules/creating-migration-plan-2-8.adoc @@ -10,7 +10,7 @@ Use the {ocp} web console to create a migration plan. Specify the source provide ==== Virtual machines with guest initiated storage connections, such as Internet Small Computer Systems Interface (iSCSI) connections or Network File System (NFS) mounts, are not handled by {project-short} and could require additional planning before or reconfiguration after the migration. -This is to ensure that no issues arise due to the addition or newly migrated VM accessing this storage. +This ensures that no issues arise when a newly added VM or a newly migrated VM accesses this storage.. ==== include::snip_plan-limits.adoc[] From 16cf72a9fb3fa79ce74d0f44c8090cdb5f381b90 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Thu, 28 Nov 2024 11:57:25 +0200 Subject: [PATCH 7/9] from Shruti --- .../modules/creating-migration-plan-2-8.adoc | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/documentation/modules/creating-migration-plan-2-8.adoc b/documentation/modules/creating-migration-plan-2-8.adoc index d35c2a0fbf7..9d71fc3bf34 100644 --- a/documentation/modules/creating-migration-plan-2-8.adoc +++ b/documentation/modules/creating-migration-plan-2-8.adoc @@ -10,7 +10,7 @@ Use the {ocp} web console to create a migration plan. Specify the source provide ==== Virtual machines with guest initiated storage connections, such as Internet Small Computer Systems Interface (iSCSI) connections or Network File System (NFS) mounts, are not handled by {project-short} and could require additional planning before or reconfiguration after the migration. -This ensures that no issues arise when a newly added VM or a newly migrated VM accesses this storage.. +This ensures that no issues arise when a newly added VM or a newly migrated VM accesses this storage. ==== include::snip_plan-limits.adoc[] @@ -39,19 +39,19 @@ ifdef::vmware[] ==== Check the following optional items related to VMware: -* *Preserving static IPs of VMs*: By default, virtual network interface controllers (vNICs) change during the migration process. As a result, vNICs that are configured with a static IP linked to the interface name in the guest VM lose their IP. To avoid this, click the Edit icon next to *Preserve static IPs* and toggle the *Whether to preserve the static IPs* switch in the window that opens. Then click *Save*. +* *Preserving static IPs of VMs*: By default, virtual network interface controllers (vNICs) change during the migration process. As a result, vNICs that are configured with a static IP linked to the interface name in the guest VM lose their IP. To avoid this, click the *Edit* icon next to *Preserve static IPs* and toggle the *Whether to preserve the static IPs* switch in the window that opens. Then click *Save*. + {project-short} then issues a warning message about any VMs for which vNIC properties are missing. To retrieve any missing vNIC properties, run those VMs in vSphere in order for the vNIC properties to be reported to {project-short}. -* *Entering a list of decryption passphrases for disks encrypted using Linux Unified Key Setup (LUKS)*: To enter a list of decryption passphrases for LUKS-encrypted devices, in the *Settings* section, click the Edit icon next to *Disk decryption passphrases*, enter the passphrases, and then click *Save*. You do not need to enter the passphrases in a specific order - for each LUKS-encrypted device, {project-short} tries each passphrase until one unlocks the device. +* *Entering a list of decryption passphrases for disks encrypted using Linux Unified Key Setup (LUKS)*: To enter a list of decryption passphrases for LUKS-encrypted devices, in the *Settings* section, click the *Edit* icon next to *Disk decryption passphrases*, enter the passphrases, and then click *Save*. You do not need to enter the passphrases in a specific order. For each LUKS-encrypted device, {project-short} tries each passphrase until one unlocks the device. * *Specifying a root device*: Applies to multi-boot VM migrations only. By default, {project-short} uses the first bootable device detected as the root device. + -To specify a different root device, in the *Settings* section, click the Edit icon next to *Root device* and choose a device from the list of commonly-used options, or enter a device in the text box. +To specify a different root device, in the *Settings* section, click the *Edit* icon next to *Root device* and choose a device from the list of commonly-used options, or enter a device in the text box. + {project-short} uses the following format for disk location: `/dev/sd`. For example, if the second disk is the root device and the operating system is on the disk's second partition, the format would be: `/dev/sdb2`. After you enter the boot device, click *Save*. + -If the conversion fails because the boot device provided is incorrect, it is possible to get the correct information by looking at the conversion pod logs. +If the conversion fails because the boot device provided is incorrect, it is possible to get the correct information by checking the conversion pod logs. ==== endif::[] @@ -62,9 +62,11 @@ ifdef::rhv[] Check the following optional items related to {rhv-short}. * *Preserving the CPU model of VMs that are migrated from {rhv-short}*: Generally, the CPU model (type) for {rhv-short} VMs is set at the cluster level, but it can be set at the VM level, which is called a custom CPU model. -By default, {project-short} sets the CPU model on the destination cluster as follows: {project-short} preserves custom CPU settings for VMs that have them, but, for VMs without custom CPU settings, {project-short} does not set the CPU model. Instead, the CPU model is later set by {virt}. +By default, {project-short} sets the CPU model on the destination cluster as follows: +** {project-short} preserves custom CPU settings for VMs that have them. +** For VMs without custom CPU settings, {project-short} does not set the CPU model. Instead, the CPU model is later set by {virt}. + -To preserve the cluster-level CPU model of your {rhv-short} VMs, in the *Settings* section, click the Edit icon next to *Preserve CPU model*. Toggle the *Whether to preserve the CPU model* switch, and then click *Save*. +To preserve the cluster-level CPU model of your {rhv-short} VMs, in the *Settings* section, click the *Edit* icon next to *Preserve CPU model*. Toggle the *Whether to preserve the CPU model* switch, and then click *Save*. ==== endif::[] From cbd8688a8429ba664916aecac04a19f01d19a3b0 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Thu, 28 Nov 2024 16:44:07 +0200 Subject: [PATCH 8/9] Changed warning after Nunzy and Fabian --- documentation/modules/creating-migration-plan-2-8.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/modules/creating-migration-plan-2-8.adoc b/documentation/modules/creating-migration-plan-2-8.adoc index 9d71fc3bf34..74ad4901558 100644 --- a/documentation/modules/creating-migration-plan-2-8.adoc +++ b/documentation/modules/creating-migration-plan-2-8.adoc @@ -8,9 +8,9 @@ Use the {ocp} web console to create a migration plan. Specify the source provide [WARNING] ==== -Virtual machines with guest initiated storage connections, such as Internet Small Computer Systems Interface (iSCSI) connections or Network File System (NFS) mounts, are not handled by {project-short} and could require additional planning before or reconfiguration after the migration. +Do not include virtual machines with guest initiated storage connections, such as Internet Small Computer Systems Interface (iSCSI) connections or Network File System (NFS) mounts. These require either additional planning before a migration or reconfiguration after the migration -This ensures that no issues arise when a newly added VM or a newly migrated VM accesses this storage. +This prevents concurrent disk access to the storage the guest points to. ==== include::snip_plan-limits.adoc[] From d73d6b7b7c036b51a136c69258f15d8511dfc286 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Mon, 2 Dec 2024 17:15:13 +0200 Subject: [PATCH 9/9] Adding warm/cold migration option --- .../modules/creating-migration-plan-2-8.adoc | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/documentation/modules/creating-migration-plan-2-8.adoc b/documentation/modules/creating-migration-plan-2-8.adoc index 74ad4901558..dd767e553cd 100644 --- a/documentation/modules/creating-migration-plan-2-8.adoc +++ b/documentation/modules/creating-migration-plan-2-8.adoc @@ -27,17 +27,19 @@ The *Select virtual machines* interface opens. + The *Create migration plan* pane opens. It displays the source provider's name and suggestions for a target provider and namespace, a network map, and a storage map. . Enter the *Plan name*. -. Make any needed changes to the editable items. -. Click *Add mapping* to edit a suggested network mapping or a storage mapping, or to add one or more additional mappings. +. To change the *Target provider*, the *Target namespace*, or elements of the *Network map* or the *Storage map*, select an item from the relevant list. +> To add either a *Network map* or a *Storage map*, click the *+* sign anf add a mapping. . Click *Create migration plan*. + -{project-short} validates the migration plan and the *Plan details* page opens, indicating whether the plan is ready for use or contains an error. The details of the plan are listed, and you can edit the items you filled in on the previous page. If you make any changes, {project-short} validates the plan again. +{project-short} validates the migration plan and the *Plan details* page opens, indicating whether the plan is ready for use or contains an error. ++ +The details of the plan are listed, and you can edit the items you filled in on the previous page. If you make any changes, {project-short} validates the plan again. ifdef::vmware[] -+ -[IMPORTANT] -==== -Check the following optional items related to VMware: + +. Check the following items related to VMware. All are optional except for *Warm migration*. + +* *Warm migration* By default, all migrations are cold migrations. For a warm migration, click the *Edit* icon, and select *Warm migration*. * *Preserving static IPs of VMs*: By default, virtual network interface controllers (vNICs) change during the migration process. As a result, vNICs that are configured with a static IP linked to the interface name in the guest VM lose their IP. To avoid this, click the *Edit* icon next to *Preserve static IPs* and toggle the *Whether to preserve the static IPs* switch in the window that opens. Then click *Save*. + @@ -52,14 +54,13 @@ To specify a different root device, in the *Settings* section, click the *Edit* {project-short} uses the following format for disk location: `/dev/sd`. For example, if the second disk is the root device and the operating system is on the disk's second partition, the format would be: `/dev/sdb2`. After you enter the boot device, click *Save*. + If the conversion fails because the boot device provided is incorrect, it is possible to get the correct information by checking the conversion pod logs. -==== endif::[] ifdef::rhv[] -+ -[IMPORTANT] -==== -Check the following optional items related to {rhv-short}. + +. Check the following items related to {rhv-short}. All are optional except for *Warm migration*. + +* *Warm migration* By default, all migrations are cold migrations. For a warm migration, click the *Edit* icon, and select *Warm migration*. * *Preserving the CPU model of VMs that are migrated from {rhv-short}*: Generally, the CPU model (type) for {rhv-short} VMs is set at the cluster level, but it can be set at the VM level, which is called a custom CPU model. By default, {project-short} sets the CPU model on the destination cluster as follows: @@ -67,7 +68,6 @@ By default, {project-short} sets the CPU model on the destination cluster as fol ** For VMs without custom CPU settings, {project-short} does not set the CPU model. Instead, the CPU model is later set by {virt}. + To preserve the cluster-level CPU model of your {rhv-short} VMs, in the *Settings* section, click the *Edit* icon next to *Preserve CPU model*. Toggle the *Whether to preserve the CPU model* switch, and then click *Save*. -==== endif::[] . If your plan is valid, you can do one of the following: