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) 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.
-
Interval at which a new snapshot is requested before initiating a warm migration.
-
Frequency with which the system checks the status of snapshot creation or removal during a warm migration.
-
Percentage of space in persistent volumes allocated as file system overhead when the
storageclass
isfilesystem
(ForkliftController
CR only). -
Fixed amount of additional space allocated in persistent block volumes. This setting is applicable for any
storageclass
that is block-based (ForkliftController
CR only). -
Configuration map of operating systems to preferences for vSphere source providers (
ForkliftController
CR only). -
Configuration map of operating systems to preferences for {rhv-full} ({rhv-short}) source providers (
ForkliftController
CR only). -
Whether to retain importer pods so that the Containerized Data Importer (CDI) does not delete them during migration (
ForkliftController
CR only).
The procedure for configuring these settings using the user interface is presented in Configuring MTV settings. The procedure for configuring these settings by modifying the ForkliftController
CR is presented following.
-
Change a parameter’s value in the
spec
section of theForkliftController
CR by adding the parameter and value as follows:spec: parameter: value # (1)
-
Parameters that you can configure using the CLI are shown in the table that follows, along with a description of each parameter and its default value.
-
Parameter | Description | Default value |
---|---|---|
|
Varies with provider as follows:
|
|
|
The duration in hours for retaining |
|
|
The CPU limit allocated to the main controller container. |
|
|
The memory limit allocated to the main controller container. |
|
|
The interval in minutes at which a new snapshot is requested before initiating a warm migration. |
|
|
The frequency in seconds with which the system checks the status of snapshot creation or removal during a warm migration. |
|
|
Percentage of space in persistent volumes allocated as file system overhead when the
|
|
|
Fixed amount of additional space allocated in persistent block volumes. This setting is applicable for any
|
|
|
Configuration map for vSphere source providers. This configuration map maps the operating system of the incoming VM to a {virt} preference name. This configuration map needs to be in the namespace where the {project-short} Operator is deployed. To see the list of preferences in your {virt} environment, open the {ocp-name} web console and click Virtualization > Preferences. Add values to the configuration map when this parameter has the default value,
|
|
|
Configuration map for {rhv-short} source providers. This configuration map maps the operating system of the incoming VM to a {virt} preference name. This configuration map needs to be in the namespace where the {project-short} Operator is deployed. To see the list of preferences in your {virt} environment, open the {ocp-name} web console and click Virtualization → Preferences. You can add values to the configuration map when this parameter has the default value,
|
|
|
Whether to retain importer pods so that the Containerized Data Importer (CDI) does not delete them during migration.
|
|