|
42 | 42 | "{{vmCount}} VM{{isPlural}} migration paused until cutover scheduled": "{{vmCount}} VM{{isPlural}} migration paused until cutover scheduled", |
43 | 43 | "{children}": "{children}", |
44 | 44 | "<0>{isOvaProvider\n ? ovaMigrationMessage\n : t('Start the {{migrationType}} migration for plan', { migrationType })} <2>{name}</2>?</0>{isOvaProvider ? null : <StackItem>{migrationMessage}</StackItem>}": "<0>{isOvaProvider\n ? ovaMigrationMessage\n : t('Start the {{migrationType}} migration for plan', { migrationType })} <2>{name}</2>?</0>{isOvaProvider ? null : <StackItem>{migrationMessage}</StackItem>}", |
| 45 | + "<0><0>{description}</0><1>Add labels to specify qualifying nodes. For each nodes label, set <2>key, value</2> pair(s). For example: key set to <5>beta.kubernetes.io/os</5> and value set to <7>linux</7></1></0>": "<0><0>{description}</0><1>Add labels to specify qualifying nodes. For each nodes label, set <2>key, value</2> pair(s). For example: key set to <5>beta.kubernetes.io/os</5> and value set to <7>linux</7></1></0>", |
| 46 | + "<0><0>{description}</0><1>Enter <1>key=value</1> pair(s). For example: project=myProject</1></0>": "<0><0>{description}</0><1>Enter <1>key=value</1> pair(s). For example: project=myProject</1></0>", |
45 | 47 | "<0><0>{TARGET_LABELS_DETAILS_ITEM_DESCRIPTION}</0><1>Enter <1>key=value</1> pair(s). For example: project=myProject</1></0>": "<0><0>{TARGET_LABELS_DETAILS_ITEM_DESCRIPTION}</0><1>Enter <1>key=value</1> pair(s). For example: project=myProject</1></0>", |
46 | 48 | "<0><0>{TARGET_NODE_SELECTOR_DETAILS_ITEM_DESCRIPTION}</0><1>Add labels to specify qualifying nodes. For each nodes label, set <2>key, value</2> pair(s). For example: key set to <5>beta.kubernetes.io/os</5> and value set to <7>linux</7></1></0>": "<0><0>{TARGET_NODE_SELECTOR_DETAILS_ITEM_DESCRIPTION}</0><1>Add labels to specify qualifying nodes. For each nodes label, set <2>key, value</2> pair(s). For example: key set to <5>beta.kubernetes.io/os</5> and value set to <7>linux</7></1></0>", |
47 | 49 | "<0><0>A root device is the storage device or partition that contains the root filesystem. For example, naming a root device \"/dev/sda2\" would mean to use the second partition on the first hard drive.</0><1>If you do not provide a root device, the first root device will be used. If the named root device does not exist or is not detected as a root device, the migration will fail.</1><2><0>Learn more</0></2></0>": "<0><0>A root device is the storage device or partition that contains the root filesystem. For example, naming a root device \"/dev/sda2\" would mean to use the second partition on the first hard drive.</0><1>If you do not provide a root device, the first root device will be used. If the named root device does not exist or is not detected as a root device, the migration will fail.</1><2><0>Learn more</0></2></0>", |
|
278 | 280 | "Controller transfer network": "Controller transfer network", |
279 | 281 | "Controls the interval at which a new snapshot is requested prior to initiating a warm migration. The default value is 60 minutes.": "Controls the interval at which a new snapshot is requested prior to initiating a warm migration. The default value is 60 minutes.", |
280 | 282 | "Conversion migration": "Conversion migration", |
| 283 | + "Convertor pod affinity rules": "Convertor pod affinity rules", |
| 284 | + "Convertor pod labels": "Convertor pod labels", |
| 285 | + "Convertor pod node selector": "Convertor pod node selector", |
281 | 286 | "Copied": "Copied", |
282 | 287 | "Copy to clipboard": "Copy to clipboard", |
283 | 288 | "Core concepts": "Core concepts", |
|
369 | 374 | "Edit affinity rule": "Edit affinity rule", |
370 | 375 | "Edit Ansible hook configuration for your migration plan. Hooks are applied to all virtual machines in the plan.": "Edit Ansible hook configuration for your migration plan. Hooks are applied to all virtual machines in the plan.", |
371 | 376 | "Edit appliance management": "Edit appliance management", |
| 377 | + "Edit convertor pod affinity rules": "Edit convertor pod affinity rules", |
| 378 | + "Edit convertor pod labels": "Edit convertor pod labels", |
| 379 | + "Edit convertor pod node selector": "Edit convertor pod node selector", |
372 | 380 | "Edit cutover": "Edit cutover", |
373 | 381 | "Edit default transfer network": "Edit default transfer network", |
374 | 382 | "Edit description": "Edit description", |
|
1080 | 1088 | "Source provider:": "Source provider:", |
1081 | 1089 | "Source storage": "Source storage", |
1082 | 1090 | "Specify a list of passphrases for the Linux Unified Key Setup (LUKS)-encrypted devices for the VMs that you want to migrate.": "Specify a list of passphrases for the Linux Unified Key Setup (LUKS)-encrypted devices for the VMs that you want to migrate.", |
| 1091 | + "Specify affinity rules for virt-v2v convertor pods during migration. This can apply hard and soft affinity and anti-affinity rules for convertor pods against workloads and nodes - for performance optimization (co-locating with storage) and ensuring network proximity to source infrastructure.": "Specify affinity rules for virt-v2v convertor pods during migration. This can apply hard and soft affinity and anti-affinity rules for convertor pods against workloads and nodes - for performance optimization (co-locating with storage) and ensuring network proximity to source infrastructure.", |
1083 | 1092 | "Specify affinity rules that will be applied after migration to all target virtual machines of the migration plan.\n This can apply hard and soft affinity and anti-affinity rules for migrated virtual machines against workloads (of virtual machines and Pods) and against nodes - for performance optimization (co-locating related workloads) and High availability (spread virtual machines across nodes or zones).": "Specify affinity rules that will be applied after migration to all target virtual machines of the migration plan.\n This can apply hard and soft affinity and anti-affinity rules for migrated virtual machines against workloads (of virtual machines and Pods) and against nodes - for performance optimization (co-locating related workloads) and High availability (spread virtual machines across nodes or zones).", |
1084 | 1093 | "Specify custom labels that will be applied after migration to all target virtual machines of the migration plan. This can apply organizational or operational labels to migrated virtual machines for further identification and management.": "Specify custom labels that will be applied after migration to all target virtual machines of the migration plan. This can apply organizational or operational labels to migrated virtual machines for further identification and management.", |
| 1094 | + "Specify custom labels to apply to virt-v2v convertor pods during migration. This can help with organizational labeling, monitoring, or targeting convertor pods with network policies.": "Specify custom labels to apply to virt-v2v convertor pods during migration. This can help with organizational labeling, monitoring, or targeting convertor pods with network policies.", |
1085 | 1095 | "Specify node labels that will be applied after migration to all target virtual machines of the migration plan for constraining virtual machines scheduling to specific nodes, based on node labels. This will ensure that the migrated virtual machines will run on nodes with required capabilities (GPU, storage type, CPU architecture).": "Specify node labels that will be applied after migration to all target virtual machines of the migration plan for constraining virtual machines scheduling to specific nodes, based on node labels. This will ensure that the migrated virtual machines will run on nodes with required capabilities (GPU, storage type, CPU architecture).", |
| 1096 | + "Specify node selector labels for virt-v2v convertor pods to constrain their scheduling to specific nodes. This ensures convertor pods run on nodes with required capabilities such as network proximity to source infrastructure or specific storage access.": "Specify node selector labels for virt-v2v convertor pods to constrain their scheduling to specific nodes. This ensures convertor pods run on nodes with required capabilities such as network proximity to source infrastructure or specific storage access.", |
1086 | 1097 | "Specify the type of source provider. Allowed values are ova, ovirt, vsphere,\n openshift, and openstack. This label is needed to verify the credentials are correct when the remote system is accessible and, for RHV, to retrieve the Manager CA certificate when\n a third-party certificate is specified.": "Specify the type of source provider. Allowed values are ova, ovirt, vsphere,\n openshift, and openstack. This label is needed to verify the credentials are correct when the remote system is accessible and, for RHV, to retrieve the Manager CA certificate when\n a third-party certificate is specified.", |
1087 | 1098 | "Staging": "Staging", |
1088 | 1099 | "Start": "Start", |
|
0 commit comments