From 6b58484348b831702db781b8154306162982cfa1 Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Wed, 18 Dec 2024 11:08:45 +0200 Subject: [PATCH] fixed file system overhead --- documentation/modules/adding-source-provider.adoc | 6 +++--- documentation/modules/creating-vddk-image.adoc | 4 ++-- documentation/modules/file-system-overhead.adoc | 7 +++---- documentation/modules/vmware-prerequisites.adoc | 8 ++++---- 4 files changed, 12 insertions(+), 13 deletions(-) diff --git a/documentation/modules/adding-source-provider.adoc b/documentation/modules/adding-source-provider.adoc index b2a831c6487..56dbf1b6153 100644 --- a/documentation/modules/adding-source-provider.adoc +++ b/documentation/modules/adding-source-provider.adoc @@ -15,9 +15,9 @@ EMS enforcement is disabled for migrations with VMware vSphere source providers .Prerequisites -[TIP] +[NOTE] ==== -To accelerate migration and reduce the risk of a migration plan failing, create a VMware Virtual Disk Development Kit (VDDK) image in a secure registry that is accessible to all clusters. If you are not using VDDK and a plan fails, then retry with VDDK installed. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image]. +Creating a VDDK image, although optional, is highly recommended. Using {project-short} without VDDK is not recommended and could result in significantly lower migration speeds. If you are not using VDDK and a plan fails, then retry with VDDK installed. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image]. ==== endif::[] @@ -92,7 +92,7 @@ ifdef::vmware[] * *Provider resource name*: Name of the source provider. * *Endpoint type*: Select the vSphere provider endpoint type. Options: *vCenter* or *ESXi*. You can migrate virtual machines from vCenter, an ESX/ESXi server that is not managed by vCenter, or from an ESX/ESXi server that is managed by vCenter but does not go through vCenter. * *URL*: URL of the SDK endpoint of the vCenter on which the source VM is mounted. Ensure that the URL includes the `sdk` path, usually `/sdk`. For example, `https://vCenter-host-example.com/sdk`. If a certificate for FQDN is specified, the value of this field needs to match the FQDN in the certificate. -* *VDDK init image*: `VDDKInitImage` path. It is strongly recommended to create a VDDK init image to accelerate migrations. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image]. +* *VDDK init image*: `VDDKInitImage` path. Creating a VDDK init image, although optional, is highly recommended. Using {project-short} without VDDK is not recommended and could result in significantly lower migration speeds.. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image]. + *Provider credentials* diff --git a/documentation/modules/creating-vddk-image.adoc b/documentation/modules/creating-vddk-image.adoc index fdfe929c4ae..e0557462c5e 100644 --- a/documentation/modules/creating-vddk-image.adoc +++ b/documentation/modules/creating-vddk-image.adoc @@ -14,9 +14,9 @@ It is strongly recommended that {project-first} should be used with the VMware V Creating a VDDK image, although optional, is highly recommended. Using {project-short} without VDDK is not recommended and could result in significantly lower migration speeds. ==== -To make use of this feature, you download the VMware Virtual Disk Development Kit (VDDK), build a VDDK image, and push the VDDK image to your image registry. +To make use of this feature, you download the VMware Virtual Disk Development Kit (VDDK), build a VDDK image, and push the VDDK image to a secure registry that is accessible to all clusters. -The VDDK package contains symbolic links, therefore, the procedure of creating a VDDK image must be performed on a file system that preserves symbolic links (symlinks). +The VDDK package contains symbolic li nks, therefore, the procedure of creating a VDDK image must be performed on a file system that preserves symbolic links (symlinks). [NOTE] ==== diff --git a/documentation/modules/file-system-overhead.adoc b/documentation/modules/file-system-overhead.adoc index a36ea67b21c..9c3e2a1dbf6 100644 --- a/documentation/modules/file-system-overhead.adoc +++ b/documentation/modules/file-system-overhead.adoc @@ -6,16 +6,15 @@ [id="file-system-overhead_{context}"] = File system overhead ifdef::rhv[] -When you run a cold migration from {rhv-full} to the {ocp} cluster that {project-full} is deployed on, the migration allocates persistent volumes without Customized Data Importer (CDI). In these cases, you might need to adjust the file system overhead. +When you run a cold migration from {rhv-full} to the {ocp} cluster that {project-full} is deployed on, the migration allocates persistent volumes without Customized Data Importer (CDI). In these cases, for volumes on a persistent volume claim that use the `volumeMode` file system, you might need to adjust the file system overhead. endif::[] ifdef::ostack[] -When you migrate from {osp} to the {ocp} cluster that {project-full} is deployed on, the migration allocates persistent volumes without Customized Data Importer (CDI). In these cases, you might need to adjust the file system overhead. +When you migrate from {osp} to the {ocp} cluster that {project-full} is deployed on, the migration allocates persistent volumes without Customized Data Importer (CDI).In these cases, for volumes on a persistent volume claim that use the `volumeMode` file system, you might need to adjust the file system overhead. endif::[] The configured file system overhead has a default value of 10%. If that is too low, the disk transfer fails due to lack of space. In this case, increase the file system overhead. -If you need to reduce storage consumption, decrease the file system overhead. - You can change the file system overhead by changing the value of the `controller_filesystem_overhead` in the `spec` portion of the `forklift-controller` CR, as described in xref:configuring-mtv-operator_mtv[Configuring the MTV Operator]. + diff --git a/documentation/modules/vmware-prerequisites.adoc b/documentation/modules/vmware-prerequisites.adoc index c70d7b7b5c8..9e613f614d6 100644 --- a/documentation/modules/vmware-prerequisites.adoc +++ b/documentation/modules/vmware-prerequisites.adoc @@ -17,17 +17,17 @@ The following prerequisites apply to VMware migrations: [IMPORTANT] ==== -In the event of a power outage, data might be lost for a VM with disabled hibernation. However, if hibernation is not disabled, migration will fail +In the event of a power outage, data might be lost for a VM with disabled hibernation. However, if hibernation is not disabled, migration will fail. ==== [NOTE] ==== -Neither {project-short} nor OpenShift Virtualization support conversion of Btrfs for migrating VMs from VMWare. +Neither {project-short} nor {virt} support conversion of Btrfs for migrating VMs from VMWare. ==== -[TIP] +[NOTE] ==== -To accelerate migration and reduce the risk of a migration plan failing, create a VMware Virtual Disk Development Kit (VDDK) image in a secure registry that is accessible to all clusters. If you are not using VDDK and a plan fails, then retry with VDDK installed. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image]. +Creating a VDDK image, although optional, is highly recommended. Using {project-short} without VDDK is not recommended and could result in significantly lower migration speeds. If you are not using VDDK and a plan fails, then retry with VDDK installed. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image]. ==== [TIP]