1. Start: When you click Start plan, MTV initiates the migration plan.
2. PreHook: If you added a pre-migration hook, MTV runs it now.
3. Create empty DataVolumes: MTV creates empty target DataVolumes in the target OpenShift Virtualization cluster. OpenShift Virtualization uses KubeVirt to handle the actual storage migration.
4. Ensure resources: MTV copies all secrets or config maps that are mounted by a source VM to the target namespace.
5. Create target VMs: MTV creates target VMs in a running state and creates a VirtualMachineInstanceMigration resource on each cluster. The VMs have a special KubeVirt annotation indicating to start them in migration target mode.
6. Wait for state transfer: MTV waits for KubeVirt to handle the state transfer and for the destination VMs to report as ready. KubeVirt also handles the shutdown of the source VMs after the state transfer.
7. PostHook: If you added a post-migration hook, MTV runs it now.
8. Completed: MTV indicates that the migration is finished.

Procedure

1. In the dashboard of the OpenStack web console, click Project > API Access.

2. Expand Download OpenStack RC file and click OpenStack RC file.

   The file that is downloaded, referred to here as <openstack_rc_file>, includes the following fields used for token authentication:

   OS_AUTH_URL
   OS_PROJECT_ID
   OS_PROJECT_NAME
   OS_DOMAIN_NAME
   OS_USERNAME

3. To get the data needed for token authentication, run the following command:

   $ openstack token issue

   The output, referred to here as <openstack_token_output>, includes the token, userID, and projectID that you need for authentication using a token with user ID.

4. Create a Secret manifest similar to the following:

   • For authentication using a token with user ID:

     cat << EOF | oc apply -f -
     apiVersion: v1
     kind: Secret
     metadata:
       name: openstack-secret-tokenid
       namespace: openshift-mtv
       labels:
         createdForProviderType: openstack
     type: Opaque
     stringData:
       authType: token
       token: <token_from_openstack_token_output>
       projectID: <projectID_from_openstack_token_output>
       userID: <userID_from_openstack_token_output>
       url: <OS_AUTH_URL_from_openstack_rc_file>
     EOF

   • For authentication using a token with user name:

     cat << EOF | oc apply -f -
     apiVersion: v1
     kind: Secret
     metadata:
       name: openstack-secret-tokenname
       namespace: openshift-mtv
       labels:
         createdForProviderType: openstack
     type: Opaque
     stringData:
       authType: token
       token: <token_from_openstack_token_output>
       domainName: <OS_DOMAIN_NAME_from_openstack_rc_file>
       projectName: <OS_PROJECT_NAME_from_openstack_rc_file>
       username: <OS_USERNAME_from_openstack_rc_file>
       url: <OS_AUTH_URL_from_openstack_rc_file>
     EOF

Procedure

1. In the dashboard of the OpenStack web console, click Project > API Access.

2. Expand Download OpenStack RC file and click OpenStack RC file.

   The file that is downloaded, referred to here as <openstack_rc_file>, includes the following fields used for application credential authentication:

   OS_AUTH_URL
   OS_PROJECT_ID
   OS_PROJECT_NAME
   OS_DOMAIN_NAME
   OS_USERNAME

3. To get the data needed for application credential authentication, run the following command:

   $ openstack application credential create --role member --role reader --secret redhat forklift

   The output, referred to here as <openstack_credential_output>, includes:

   • The id and secret that you need for authentication using an application credential ID
   • The name and secret that you need for authentication using an application credential name

4. Create a Secret manifest similar to the following:

   • For authentication using the application credential ID:

     cat << EOF | oc apply -f -
     apiVersion: v1
     kind: Secret
     metadata:
       name: openstack-secret-appid
       namespace: openshift-mtv
       labels:
         createdForProviderType: openstack
     type: Opaque
     stringData:
       authType: applicationcredential
       applicationCredentialID: <id_from_openstack_credential_output>
       applicationCredentialSecret: <secret_from_openstack_credential_output>
       url: <OS_AUTH_URL_from_openstack_rc_file>
     EOF

   • For authentication using the application credential name:

     cat << EOF | oc apply -f -
     apiVersion: v1
     kind: Secret
     metadata:
       name: openstack-secret-appname
       namespace: openshift-mtv
       labels:
         createdForProviderType: openstack
     type: Opaque
     stringData:
       authType: applicationcredential
       applicationCredentialName: <name_from_openstack_credential_output>
       applicationCredentialSecret: <secret_from_openstack_credential_output>
       domainName: <OS_DOMAIN_NAME_from_openstack_rc_file>
       username: <OS_USERNAME_from_openstack_rc_file>
       url: <OS_AUTH_URL_from_openstack_rc_file>
     EOF

Procedure

1. In the Red Hat OpenShift web console, click Operators → OperatorHub.
2. Use the Filter by keyword field to search for mtv-operator.
3. Click Migration Toolkit for Virtualization Operator and then click Install.
4. Click Create ForkliftController when the button becomes active.

5. Click Create.

   Your ForkliftController appears in the list that is displayed.

6. Click Workloads → Pods to verify that the MTV pods are running.

7. Click Operators → Installed Operators to verify that Migration Toolkit for Virtualization Operator appears in the openshift-mtv project with the status Succeeded.

   When the plugin is ready you will be prompted to reload the page. The Migration menu item is automatically added to the navigation bar, displayed on the left of the Red Hat OpenShift web console.

Procedure

1. Create the openshift-mtv project:

   $ cat << EOF | oc apply -f -
   apiVersion: project.openshift.io/v1
   kind: Project
   metadata:
     name: openshift-mtv
   EOF

2. Create an OperatorGroup CR called migration:

   $ cat << EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1
   kind: OperatorGroup
   metadata:
     name: migration
     namespace: openshift-mtv
   spec:
     targetNamespaces:
       - openshift-mtv
   EOF

3. Create a Subscription CR for the Operator:

   $ cat << EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: mtv-operator
     namespace: openshift-mtv
   spec:
     channel: release-v2.10
     installPlanApproval: Automatic
     name: mtv-operator
     source: redhat-operators
     sourceNamespace: openshift-marketplace
     startingCSV: "mtv-operator.v2.10.0"
   EOF

4. Create a ForkliftController CR:

   $ cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: ForkliftController
   metadata:
     name: forklift-controller
     namespace: openshift-mtv
   spec:
     olm_managed: true
   EOF

5. Verify that the MTV pods are running:

   $ oc get pods -n openshift-mtv

   The following is example output:

   Example

   NAME                                                    READY   STATUS    RESTARTS   AGE
   forklift-api-bb45b8db4-cpzlg                            1/1     Running   0          6m34s
   forklift-controller-7649db6845-zd25p                    2/2     Running   0          6m38s
   forklift-must-gather-api-78fb4bcdf6-h2r4m               1/1     Running   0          6m28s
   forklift-operator-59c87cfbdc-pmkfc                      1/1     Running   0          28m
   forklift-ui-plugin-5c5564f6d6-zpd85                     1/1     Running   0          6m24s
   forklift-validation-7d84c74c6f-fj9xg                    1/1     Running   0          6m30s
   forklift-volume-populator-controller-85d5cb64b6-mrlmc   1/1     Running   0          6m36s

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Migration plans.
2. Open the Plan Details page for your migration plan.
3. Click the Virtual Machines tab to view a table of all VMs from the configured source provider.
4. If the Target name column does not already show in the VM table, click Manage columns to select Target name and display the column.
5. Identify non-conformant names in the list of VMs by checking the alerts in the Concerns column.
6. To rename a VM, click the More icon at the end of the row for the VM, and click Edit target name.
7. Enter and save a new name for the VM. Ensure that the new name consists only of alphanumeric characters (a-z, 0-9) and hyphens. Ensure that the name does not start or end with a hyphen or contain consecutive hyphens and is less than 63 characters long.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Network maps.

2. Click Create NetworkMap.

   The Create NetworkMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of network maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.
2. Click Create storage map > Create with form.

3. Specify the following:

   • Map name: Name of the storage map.
   • Project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Source storage: Select from the list.
   • Target storage: Select from the list

4. Optional: If this is a storage map for a migration using storage copy offload, specify the following offload options:

   • Offload plugin: Select from the list.
   • Storage secret: Select from the list.

   • Storage product: Select from the list

     Important

     Storage copy offload is Developer Preview software only. Developer Preview software is not supported by Red Hat in any way and is not functionally complete or production-ready. Do not use Developer Preview software for production or business-critical workloads. Developer Preview software provides early access to upcoming product software in advance of its possible inclusion in a Red Hat product offering. Customers can use this software to test functionality and provide feedback during the development process. This software might not have any documentation, is subject to change or removal at any time, and has received limited testing. Red Hat might provide ways to submit feedback on Developer Preview software without an associated SLA.

     For more information about the support scope of Red Hat Developer Preview software, see Developer Preview Support Scope.

5. Optional: Click Add mapping to create additional storage maps, including mapping multiple storage sources to a single target storage class.

6. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.

2. Click Create storage map > Create with YAML.

   The Create StorageMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. Access the Create provider page for VMware by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click VMware.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click VMware.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click VMware when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   1. Provider details

      • 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 Creating a VDDK image.

        Do one of the following:

        • Select the Skip VMWare Virtual Disk Development Kit (VDDK) SDK acceleration (not recommended).
        • Enter the path in the VDDK init image text box. Format: <registry_route_or_server_path>/vddk:<tag>.

        • Upload a VDDK archive and build a VDDK init image from the archive by doing the following:

          • Click Browse next to the VDDK init image archive text box, select the desired file, and click Select.

          • Click Upload.

            The URL of the uploaded archive is displayed in the VDDK init image archive text box.

   2. Provider credentials

      • Username: vCenter user or ESXi user. For example, user@vsphere.local.
      • Password: vCenter user password or ESXi user password.

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

   Note

   It might take a few minutes for the provider to have the status Ready.

6. Optional: Add access to the UI of the provider:

   1. On the Providers page, click the provider.

      The Provider details page opens.

   2. Click the Edit icon under External UI web link.

   3. Enter the link and click Save.

      Note

      If you do not enter a link, MTV attempts to calculate the correct link.

      • If MTV succeeds, the hyperlink of the field points to the calculated link.
      • If MTV does not succeed, the field remains empty.

Procedure

1. In the Red Hat OpenShift web console, click Migration → Providers for virtualization.
2. Click the host number in the Hosts column beside a provider to view a list of hosts.
3. Select one or more hosts and click Select migration network.

4. Specify the following fields:

   • Network: Network name
   • ESXi host admin username: For example, root
   • ESXi host admin password: Password
5. Click Save.

6. Verify that the status of each host is Ready.

   If a host status is not Ready, the host might be unreachable on the migration network or the credentials might be incorrect. You can modify the host configuration and save the changes.

Procedure

1. Access the Create OpenShift Virtualization provider interface by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click OpenShift Virtualization.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click OpenShift Virtualization.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click OpenShift Virtualization when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider
   • URL: URL of the endpoint of the API server

   • Service account bearer token: Token for a service account with cluster-admin privileges

     If both URL and Service account bearer token are left blank, the local OpenShift cluster is used.

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

Procedure

1. In the Red Hat OpenShift web console, click Migration > Providers for virtualization.

2. Click the OpenShift Virtualization provider whose migration network you want to change.

   When the Providers detail page opens:

3. Click the Networks tab.
4. Click Set default transfer network.
5. Select a default transfer network from the list and click Save.

6. Configure a gateway in the network used for MTV migrations by completing the following steps:

   1. In the Red Hat OpenShift web console, click Networking > NetworkAttachmentDefinitions.
   2. Select the appropriate default transfer network NAD.
   3. Click the YAML tab.

   4. Add forklift.konveyor.io/route to the metadata:annotations section of the YAML, as in the following example:

      apiVersion: k8s.cni.cncf.io/v1
      kind: NetworkAttachmentDefinition
      metadata:
        name: localnet-network
        namespace: mtv-test
        annotations:
          forklift.konveyor.io/route: <IP address> 1

      1

      The NetworkAttachmentDefinition parameter is needed to configure an IP address for the interface, either from the Dynamic Host Configuration Protocol (DHCP) or statically. Configuring the IP address enables the interface to reach the configured gateway.

   5. Click Save.

Procedure

1. On the Red Hat OpenShift web console, click Migration for Virtualization > Migration plans.

2. Click Create plan.

   The Create migration plan wizard opens.

3. On the General page, specify the following fields:

   • Plan name: Enter a name.
   • Plan project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Target project: Select from the list. If you are using a UDN, this is the namespace defined in OpenShift Virtualization.
4. Click Next.
5. On the Virtual machines page, select the virtual machines you want to migrate and click Next.
6. If you are using a UDN, verify that the IP address of the provider is outside the subnet of the UDN. If the IP address is within the subnet of the UDN, the migration fails.

7. On the Network map page, choose one of the following options:

   • Use an existing network map: Select an existing network map from the list.

     These are network maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use a new network map: Allows you to create a new network map by supplying the following data. This map is attached to this plan, which is then considered to be its owner. Maps that you create using this option are not available in the Use an existing network map option because each is created with an owner.

     Note

     You can create an ownerless network map, which you and others can use for additional migration plans, in the Network Maps section of the UI.

     • Source network: Select from the list.

     • Target network: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Network map name: Enter a name or let MTV automatically generate a name for the network map.
8. Click Next.

9. On the Storage map page, choose one of the following options:

   • Use an existing storage map: Select an existing storage map from the list.

     These are storage maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use new storage map: Allows you to create one or two new storage maps by supplying the following data. These maps are attached to this plan, which is then their owner. Maps that you create using this option are not available in the Use an existing storage map option because each is created with an owner.

     Note

     You can create an ownerless storage map, which you and others can use for additional migration plans, in the Storage Maps section of the UI.

     • Source storage: Select from the list.

     • Target storage: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Storage map name: Enter a name or let MTV automatically generate a name for the storage map.
10. Click Next.

11. On the Migration type page, choose one of the following:

    • Cold migration (default)
    • Warm migration
12. Click Next.

13. On the Other settings (optional) page, specify any of the following settings that are appropriate for your plan. All are optional.

    • Disk decryption passphrases: For disks encrypted using Linux Unified Key Setup (LUKS).

      • Enter a decryption passphrase for a LUKS-encrypted device.
      • To add another passphrase, click Add passphrase and add a passphrase.

      • Repeat as needed.

        You do not need to enter the passphrases in a specific order. For each LUKS-encrypted device, MTV tries each passphrase until one unlocks the device.

    • Transfer Network: The network used to transfer the VMs to OpenShift Virtualization. This is the default transfer network of the provider.

      • Verify that the transfer network is in the selected target project.
      • To choose a different transfer network, select a different transfer network from the list.

      • Optional: To configure another OpenShift network in the OpenShift web console, click Networking > NetworkAttachmentDefinitions.

        To learn more about the different types of networks OpenShift supports, see Additional Networks in OpenShift Container Platform.

      • To adjust the maximum transmission unit (MTU) of the OpenShift transfer network, you must also change the MTU of the VMware migration network. For more information, see Selecting a migration network for a VMware source provider.

    • Preserve static IPs: 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 during migration.

      • To preserve static IPs, select the Preserve the static IPs checkbox.

        MTV then issues a warning message about any VMs whose vNIC properties are missing. To retrieve any missing vNIC properties, run those VMs in vSphere. This causes the vNIC properties to be reported to MTV.

    • Root device: Applies to multi-boot VM migrations only. By default, MTV uses the first bootable device detected as the root device.

      • To specify a different root device, enter it in the text box.

        MTV uses the following format for disk location: /dev/sd<disk_identifier><disk_partition>. 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.

    • Shared disks: Applies to cold migrations only. Shared disks are disks that are attached to multiple VMs and that use the multi-writer option. These characteristics make shared disks difficult to migrate. By default, MTV migrates shared disks.

      Note

      Migrating shared disks might slow down the migration process.

      • To migrate shared disks in the migration plan, verify that Shared disks is selected in the checkbox.
      • To avoid migrating shared disks, clear the Shared disks checkbox.
14. Click Next.
15. On the Hooks (optional) page, you can add a pre-migration hook, a post-migration hook, or both types of migration hooks. All are optional.
16. To add a hook, select the appropriate Enable hook checkbox.
17. Enter the Hook runner image.

18. Enter the Ansible playbook of the hook in the window.

    Note

    You cannot include more than one pre-migration hook or more than one post-migration hook in a migration plan.

19. Click Next.
20. On the Review and Create page, review the information displayed.

21. Edit any item by doing the following:

    1. Click its Edit step link.

       The wizard opens to the page where you defined the item.

    2. Edit the item.
    3. Either click Next to advance to the next page of the wizard, or click Skip to review to return directly to the Review and create page.

22. When you finish reviewing the details of the plan, click Create plan. MTV validates your plan.

    When your plan is validated, the Plan details page for your plan opens in the Details tab.

    The Plan settings section of the page includes settings that you specified in the Other settings (optional) page and some additional optional settings. The steps below refer to the additional optional steps, but all of the settings can be edited by clicking the Options menu , making the change, and then clicking Save.

23. Check the following items on the Plan settings section of the page:

    • Volume name template: Specifies a template for the volume interface name for the VMs in your plan.

      The template follows the Go template syntax and has access to the following variables:

      • .PVCName: Name of the PVC mounted to the VM using this volume

      • .VolumeIndex: Sequential index of the volume interface (0-based)

        Examples

      • "disk-{{.VolumeIndex}}"

      • "pvc-{{.PVCName}}"

        Variable names cannot exceed 63 characters.

      • To specify a volume name template for all the VMs in your plan, do the following:

        • Click the Edit icon.
        • Click Enter custom naming template.
        • Enter the template according to the instructions.
        • Click Save.

      • To specify a different volume name template only for specific VMs, do the following:

        • Click the Virtual Machines tab.
        • Select the desired VMs.
        • Click the Options menu of the VM.
        • Select Edit Volume name template.
        • Enter the template according to the instructions.

        • Click Save.

          Important

          Changes you make on the Virtual Machines tab override any changes on the Plan details page.

    • PVC name template: Specifies a template for the name of the persistent volume claim (PVC) for the VMs in your plan.

      The template follows the Go template syntax and has access to the following variables:

      • .VmName: Name of the VM
      • .PlanName: Name of the migration plan
      • .DiskIndex: Initial volume index of the disk

      • .RootDiskIndex: Index of the root disk

        Examples

      • "{{.VmName}}-disk-{{.DiskIndex}}"

      • "{{if eq .DiskIndex .RootDiskIndex}}root{{else}}data{{end}}-{{.DiskIndex}}"

        Variable names cannot exceed 63 characters.

      • To specify a PVC name template for all the VMs in your plan, do the following:

        • Click the Edit icon.
        • Click Enter custom naming template.
        • Enter the template according to the instructions.
        • Click Save.

      • To specify a PVC name template only for specific VMs, do the following:

        • Click the Virtual Machines tab.
        • Select the desired VMs.
        • Click the Options menu of the VM.
        • Select Edit PVC name template.
        • Enter the template according to the instructions.

        • Click Save.

          Important

          Changes you make on the Virtual Machines tab override any changes on the Plan details page.

    • Network name template: Specifies a template for the network interface name for the VMs in your plan.

      The template follows the Go template syntax and has access to the following variables:

      • .NetworkName: If the target network is multus, add the name of the Multus Network Attachment Definition. Otherwise, leave this variable empty.
      • .NetworkNamespace: If the target network is multus, add the namespace where the Multus Network Attachment Definition is located.
      • .NetworkType: Network type. Options: multus or pod.

      • .NetworkIndex: Sequential index of the network interface (0-based).

        Examples

      • "net-{{.NetworkIndex}}"

      • {{if eq .NetworkType "pod"}}pod{{else}}multus-{{.NetworkIndex}}{{end}}"

        Variable names cannot exceed 63 characters.

      • To specify a network name template for all the VMs in your plan, do the following:

        • Click the Edit icon.
        • Click Enter custom naming template.
        • Enter the template according to the instructions.
        • Click Save.

      • To specify a different network name template only for specific VMs, do the following:

        • Click the Virtual Machines tab.
        • Select the desired VMs.
        • Click the Options menu of the VM.
        • Select Edit Network name template.
        • Enter the template according to the instructions.

        • Click Save.

          Important

          Changes you make on the Virtual Machines tab override any changes on the Plan details page.

    • Raw copy mode: By default, during migration, virtual machines (VMs) are converted using a tool named virt-v2v that makes them compatible with OpenShift Virtualization. For more information about the virt-v2v conversion process, see How MTV uses the virt-v2v tool in Migrating your virtual machines to Red Hat OpenShift Virtualization. Raw copy mode copies VMs without converting them. This allows for faster conversions, migrating VMs running a wider range of operating systems, and supporting migrating disks encrypted using Linux Unified Key Setup (LUKS) without needing keys. However, VMs migrated using raw copy mode might not function properly on OpenShift Virtualization.

      • To use raw copy mode for your migration plan, do the following:

        • Click the Edit icon.
        • Toggle the Raw copy mode switch.

        • Click Save.

          MTV validates any changes you made on this page.

24. In addition to listing details based on your entries in the wizard, the Plan details tab includes the following two sections after the details of the plan:

    • Migration history: Details about successful and unsuccessful attempts to run the plan
    • Conditions: Any changes that need to be made to the plan so that it can run successfully

25. When you have fixed all conditions listed, you can run your plan from the Plans page.

    The Plan details page also includes five additional tabs, which are described in the table that follows:

    Table 9.1. Tabs of the Plan details page

    YAML	Virtual Machines	Resources	Mappings	Hooks
    Editable YAML Plan manifest based on your plan’s details including source provider, network and storage maps, VMs, and any issues with your VMs	The VMs the plan migrates	Calculated resources: VMs, CPUs, and total memory for both total VMs and running VMs	Editable specification of the network and storage maps used by your plan	Updatable specification of the hooks used by your plan, if any

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Network maps.

2. Click Create NetworkMap.

   The Create NetworkMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of network maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.
2. Click Create storage map > Create with form.

3. Specify the following:

   • Map name: Name of the storage map.
   • Project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Source storage: Select from the list.
   • Target storage: Select from the list
4. Optional: Click Add mapping to create additional storage maps, including mapping multiple storage sources to a single target storage class.

5. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.

2. Click Create storage map > Create with YAML.

   The Create StorageMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. Access the Create provider page for Red Hat Virtualization by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click Red Hat Virtualization.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click Red Hat Virtualization.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click Red Hat Virtualization when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider.
   • URL: URL of the API endpoint of the Red Hat Virtualization Manager (RHVM) on which the source VM is mounted. Ensure that the URL includes the path leading to the RHVM API server, usually /ovirt-engine/api. For example, https://rhv-host-example.com/ovirt-engine/api.
   • Username: Username.
   • Password: Password.

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

6. Optional: Add access to the UI of the provider:

   1. On the Providers page, click the provider.

      The Provider details page opens.

   2. Click the Edit icon under External UI web link.

   3. Enter the link and click Save.

      Note

      If you do not enter a link, MTV attempts to calculate the correct link.

      • If MTV succeeds, the hyperlink of the field points to the calculated link.
      • If MTV does not succeed, the field remains empty.

Procedure

1. Access the Create OpenShift Virtualization provider interface by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click OpenShift Virtualization.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click OpenShift Virtualization.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click OpenShift Virtualization when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider
   • URL: URL of the endpoint of the API server

   • Service account bearer token: Token for a service account with cluster-admin privileges

     If both URL and Service account bearer token are left blank, the local OpenShift cluster is used.

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

Procedure

1. In the Red Hat OpenShift web console, click Migration > Providers for virtualization.

2. Click the OpenShift Virtualization provider whose migration network you want to change.

   When the Providers detail page opens:

3. Click the Networks tab.
4. Click Set default transfer network.
5. Select a default transfer network from the list and click Save.

6. Configure a gateway in the network used for MTV migrations by completing the following steps:

   1. In the Red Hat OpenShift web console, click Networking > NetworkAttachmentDefinitions.
   2. Select the appropriate default transfer network NAD.
   3. Click the YAML tab.

   4. Add forklift.konveyor.io/route to the metadata:annotations section of the YAML, as in the following example:

      apiVersion: k8s.cni.cncf.io/v1
      kind: NetworkAttachmentDefinition
      metadata:
        name: localnet-network
        namespace: mtv-test
        annotations:
          forklift.konveyor.io/route: <IP address> 1

      1

      The NetworkAttachmentDefinition parameter is needed to configure an IP address for the interface, either from the Dynamic Host Configuration Protocol (DHCP) or statically. Configuring the IP address enables the interface to reach the configured gateway.

   5. Click Save.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Migration plans.

2. Click Create plan.

   The Create migration plan wizard opens.

3. On the General page, specify the following fields:

   • Plan name: Enter a name.
   • Plan project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Target project: Select from the list. If you are using a UDN, this is the namespace defined in OpenShift Virtualization.
4. Click Next.
5. On the Virtual machines page, select the virtual machines you want to migrate and click Next.
6. If you are using a UDN, verify that the IP address of the provider is outside the subnet of the UDN. If the IP address is within the subnet of the UDN, the migration fails.

7. On the Network map page, choose one of the following options:

   • Use an existing network map: Select an existing network map from the list.

     These are network maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use a new network map: Allows you to create a new network map by supplying the following data. This map is attached to this plan, which is then considered to be its owner. Maps that you create using this option are not available in the Use an existing network map option because each is created with an owner.

     Note

     You can create an ownerless network map, which you and others can use for additional migration plans, in the Network Maps section of the UI.

     • Source network: Select from the list.

     • Target network: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Network map name: Enter a name or let MTV automatically generate a name for the network map.
8. Click Next.

9. On the Storage map page, choose one of the following options:

   • Use an existing storage map: Select an existing storage map from the list.

     These are storage maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use new storage map: Allows you to create one or two new storage maps by supplying the following data. These maps are attached to this plan, which is then their owner. Maps that you create using this option are not available in the Use an existing storage map option because each is created with an owner.

     Note

     You can create an ownerless storage map, which you and others can use for additional migration plans, in the Storage Maps section of the UI.

     • Source storage: Select from the list.

     • Target storage: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Storage map name: Enter a name or let MTV automatically generate a name for the storage map.
10. Click Next.

11. On the Migration type page, choose one of the following:

    • Cold migration (default)
    • Warm migration
12. Click Next.

13. On the Other settings (optional) page, you have the option to change the Transfer network of your migration plan.

    The transfer network is the network used to transfer the VMs to OpenShift Virtualization. This is the default transfer network of the provider.

    • Verify that the transfer network is in the selected target project.
    • To choose a different transfer network, select a different transfer network from the list.

    • Optional: To configure another OpenShift network in the OpenShift web console, click Networking > NetworkAttachmentDefinitions.

      To learn more about the different types of networks OpenShift supports, see Additional Networks in OpenShift Container Platform.

    • To adjust the maximum transmission unit (MTU) of the OpenShift transfer network, you must also change the MTU of the VMware migration network. For more information, see Selecting a migration network for a VMware source provider.
14. Click Next.
15. On the Hooks (optional) page, you can add a pre-migration hook, a post-migration hook, or both types of migration hooks. All are optional.
16. To add a hook, select the appropriate Enable hook checkbox.
17. Enter the Hook runner image.

18. Enter the Ansible playbook of the hook in the window.

    Note

    You cannot include more than one pre-migration hook or more than one post-migration hook in a migration plan.

19. Click Next.
20. On the Review and Create page, review the information displayed.

21. Edit any item by doing the following:

    1. Click its Edit step link.

       The wizard opens to the page where you defined the item.

    2. Edit the item.
    3. Either click Next to advance to the next page of the wizard, or click Skip to review to return directly to the Review and create page.

22. When you finish reviewing the details of the plan, click Create plan. MTV validates your plan.

    When your plan is validated, the Plan details page for your plan opens in the Details tab.

    The Plan settings section of the page includes settings that you specified in the Other settings (optional) page and some additional optional settings. The steps below refer to the additional optional steps, but all of the settings can be edited by clicking the Options menu , making the change, and then clicking Save.

23. Check the following item on the Plan settings section of the page:

    • Preserve CPU mode: Generally, the CPU model (type) for Red Hat Virtualization VMs is set at the cluster level. However, the CPU model can be set at the VM level, which is called a custom CPU model.

      By default, MTV sets the CPU model on the destination cluster as follows: MTV preserves custom CPU settings for VMs that have them. For VMs without custom CPU settings, MTV does not set the CPU model. Instead, the CPU model is later set by OpenShift Virtualization.

      To preserve the cluster-level CPU model of your Red Hat Virtualization VMs, do the following:

      1. Click the Options menu .
      2. Toggle the Whether to preserve the CPU model switch.

      3. Click Save.

         MTV validates any changes you made on this page.

24. In addition to listing details based on your entries in the wizard, the Plan details tab includes the following two sections after the details of the plan:

    • Migration history: Details about successful and unsuccessful attempts to run the plan
    • Conditions: Any changes that need to be made to the plan so that it can run successfully

25. When you have fixed all conditions listed, you can run your plan from the Plans page.

    The Plan details page also includes five additional tabs, which are described in the table that follows:

    Table 10.1. Tabs of the Plan details page

    YAML	Virtual Machines	Resources	Mappings	Hooks
    Editable YAML Plan manifest based on your plan’s details including source provider, network and storage maps, VMs, and any issues with your VMs	The VMs the plan migrates	Calculated resources: VMs, CPUs, and total memory for both total VMs and running VMs	Editable specification of the network and storage maps used by your plan	Updatable specification of the hooks used by your plan, if any

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Network maps.

2. Click Create NetworkMap.

   The Create NetworkMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of network maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.
2. Click Create storage map > Create with form.

3. Specify the following:

   • Map name: Name of the storage map.
   • Project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Source storage: Select from the list.
   • Target storage: Select from the list
4. Optional: Click Add mapping to create additional storage maps, including mapping multiple storage sources to a single target storage class.

5. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.

2. Click Create storage map > Create with YAML.

   The Create StorageMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. Access the Create provider page for OpenStack by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click OpenStack.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click OpenStack.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click OpenStack when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider.
   • URL: URL of the OpenStack Identity (Keystone) endpoint. For example, http://controller:5000/v3.

   • Authentication type: Choose one of the following methods of authentication and supply the information related to your choice. For example, if you choose Application credential ID as the authentication type, the Application credential ID and the Application credential secret fields become active, and you need to supply the ID and the secret.

     • Application credential ID

       • Application credential ID: OpenStack application credential ID
       • Application credential secret: OpenStack application credential Secret

     • Application credential name

       • Application credential name: OpenStack application credential name
       • Application credential secret: OpenStack application credential Secret
       • Username: OpenStack username
       • Domain: OpenStack domain name

     • Token with user ID

       • Token: OpenStack token
       • User ID: OpenStack user ID
       • Project ID: OpenStack project ID

     • Token with user Name

       • Token: OpenStack token
       • Username: OpenStack username
       • Project: OpenStack project
       • Domain name: OpenStack domain name

     • Password

       • Username: OpenStack username
       • Password: OpenStack password
       • Project: OpenStack project
       • Domain: OpenStack domain name

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

6. Optional: Add access to the UI of the provider:

   1. On the Providers page, click the provider.

      The Provider details page opens.

   2. Click the Edit icon under External UI web link.

   3. Enter the link and click Save.

      Note

      If you do not enter a link, MTV attempts to calculate the correct link.

      • If MTV succeeds, the hyperlink of the field points to the calculated link.
      • If MTV does not succeed, the field remains empty.

Procedure

1. Access the Create OpenShift Virtualization provider interface by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click OpenShift Virtualization.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click OpenShift Virtualization.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click OpenShift Virtualization when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider
   • URL: URL of the endpoint of the API server

   • Service account bearer token: Token for a service account with cluster-admin privileges

     If both URL and Service account bearer token are left blank, the local OpenShift cluster is used.

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

Procedure

1. In the Red Hat OpenShift web console, click Migration > Providers for virtualization.

2. Click the OpenShift Virtualization provider whose migration network you want to change.

   When the Providers detail page opens:

3. Click the Networks tab.
4. Click Set default transfer network.
5. Select a default transfer network from the list and click Save.

6. Configure a gateway in the network used for MTV migrations by completing the following steps:

   1. In the Red Hat OpenShift web console, click Networking > NetworkAttachmentDefinitions.
   2. Select the appropriate default transfer network NAD.
   3. Click the YAML tab.

   4. Add forklift.konveyor.io/route to the metadata:annotations section of the YAML, as in the following example:

      apiVersion: k8s.cni.cncf.io/v1
      kind: NetworkAttachmentDefinition
      metadata:
        name: localnet-network
        namespace: mtv-test
        annotations:
          forklift.konveyor.io/route: <IP address> 1

      1

      The NetworkAttachmentDefinition parameter is needed to configure an IP address for the interface, either from the Dynamic Host Configuration Protocol (DHCP) or statically. Configuring the IP address enables the interface to reach the configured gateway.

   5. Click Save.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Migration plans.

2. Click Create plan.

   The Create migration plan wizard opens.

3. On the General page, specify the following fields:

   • Plan name: Enter a name.
   • Plan project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Target project: Select from the list. If you are using a UDN, this is the namespace defined in OpenShift Virtualization.
4. Click Next.
5. On the Virtual machines page, select the virtual machines you want to migrate and click Next.
6. If you are using a UDN, verify that the IP address of the provider is outside the subnet of the UDN. If the IP address is within the subnet of the UDN, the migration fails.

7. On the Network map page, choose one of the following options:

   • Use an existing network map: Select an existing network map from the list.

     These are network maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use a new network map: Allows you to create a new network map by supplying the following data. This map is attached to this plan, which is then considered to be its ownerr. Maps that you create using this option are not available in the Use an existing network map option because each is created with an owner.

     Note

     You can create an ownerless network map, which you and others can use for additional migration plans, in the Network Maps section of the UI.

     • Source network: Select from the list.

     • Target network: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Network map name: Enter a name or let MTV automatically generate a name for the network map.
8. Click Next.

9. On the Storage map page, choose one of the following options:

   • Use an existing storage map: Select an existing storage map from the list.

     These are storage maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use new storage map: Allows you to create one or two new storage maps by supplying the following data. These maps are attached to this plan, which is then their owner. Maps that you create using this option are not available in the Use an existing storage map option because each is created with an owner.

     Note

     You can create an ownerless storage map, which you and others can use for additional migration plans, in the Storage Maps section of the UI.

     • Source storage: Select from the list.

     • Target storage: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Storage map name: Enter a name or let MTV automatically generate a name for the storage map.
10. Click Next.

11. On the Other settings (optional) page, you have the option to change the Transfer network of your migration plan.

    The transfer network is the network used to transfer the VMs to OpenShift Virtualization. This is the default transfer network of the provider.

    • Verify that the transfer network is in the selected target project.
    • To choose a different transfer network, select a different transfer network from the list.

    • Optional: To configure another OpenShift network in the OpenShift web console, click Networking > NetworkAttachmentDefinitions.

      To learn more about the different types of networks OpenShift supports, see Additional Networks in OpenShift Container Platform.

    • To adjust the maximum transmission unit (MTU) of the OpenShift transfer network, you must also change the MTU of the VMware migration network. For more information, see Selecting a migration network for a VMware source provider.
12. Click Next.
13. On the Hooks (optional) page, you can add a pre-migration hook, a post-migration hook, or both types of migration hooks. All are optional.
14. To add a hook, select the appropriate Enable hook checkbox.
15. Enter the Hook runner image.

16. Enter the Ansible playbook of the hook in the window.

    Note

    You cannot include more than one pre-migration hook or more than one post-migration hook in a migration plan.

17. Click Next.
18. On the Review and Create page, review the information displayed.

19. Edit any item by doing the following:

    1. Click its Edit step link.

       The wizard opens to the page where you defined the item.

    2. Edit the item.
    3. Either click Next to advance to the next page of the wizard, or click Skip to review to return directly to the Review and create page.

20. When you finish reviewing the details of the plan, click Create plan. MTV validates your plan.

    When your plan is validated, the Plan details page for your plan opens in the Details tab.

21. In addition to listing details based on your entries in the wizard, the Plan details tab includes the following two sections after the details of the plan:

    • Migration history: Details about successful and unsuccessful attempts to run the plan
    • Conditions: Any changes that need to be made to the plan so that it can run successfully

22. When you have fixed all conditions listed, you can run your plan from the Plans page.

    The Plan details page also includes five additional tabs, which are described in the table that follows:

    Table 11.1. Tabs of the Plan details page

    YAML	Virtual Machines	Resources	Mappings	Hooks
    Editable YAML Plan manifest based on your plan’s details including source provider, network and storage maps, VMs, and any issues with your VMs	The VMs the plan migrates	Calculated resources: VMs, CPUs, and total memory for both total VMs and running VMs	Editable specification of the network and storage maps used by your plan	Updatable specification of the hooks used by your plan, if any

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Network maps.

2. Click Create NetworkMap.

   The Create NetworkMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of network maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.
2. Click Create storage map > Create with form.

3. Specify the following:

   • Map name: Name of the storage map.
   • Project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Source storage: Select from the list.
   • Target storage: Select from the list
4. Optional: Click Add mapping to create additional storage maps, including mapping multiple storage sources to a single target storage class.

5. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.

2. Click Create storage map > Create with YAML.

   The Create StorageMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. Access the Create provider page for Open Virtual Appliance by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click Open Virtual Appliance.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click Open Virtual Appliance.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click Open Virtual Appliance when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider
   • URL: URL of the NFS file share that serves the OVA

3. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

   Note

   An error message might appear that states that an error has occurred. You can ignore this message.

Procedure

1. Access the Create OpenShift Virtualization provider interface by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click OpenShift Virtualization.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click OpenShift Virtualization.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click OpenShift Virtualization when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider
   • URL: URL of the endpoint of the API server

   • Service account bearer token: Token for a service account with cluster-admin privileges

     If both URL and Service account bearer token are left blank, the local OpenShift cluster is used.

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

Procedure

1. In the Red Hat OpenShift web console, click Migration > Providers for virtualization.

2. Click the OpenShift Virtualization provider whose migration network you want to change.

   When the Providers detail page opens:

3. Click the Networks tab.
4. Click Set default transfer network.
5. Select a default transfer network from the list and click Save.

6. Configure a gateway in the network used for MTV migrations by completing the following steps:

   1. In the Red Hat OpenShift web console, click Networking > NetworkAttachmentDefinitions.
   2. Select the appropriate default transfer network NAD.
   3. Click the YAML tab.

   4. Add forklift.konveyor.io/route to the metadata:annotations section of the YAML, as in the following example:

      apiVersion: k8s.cni.cncf.io/v1
      kind: NetworkAttachmentDefinition
      metadata:
        name: localnet-network
        namespace: mtv-test
        annotations:
          forklift.konveyor.io/route: <IP address> 1

      1

      The NetworkAttachmentDefinition parameter is needed to configure an IP address for the interface, either from the Dynamic Host Configuration Protocol (DHCP) or statically. Configuring the IP address enables the interface to reach the configured gateway.

   5. Click Save.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Migration plans.

2. Click Create plan.

   The Create migration plan wizard opens.

3. On the General page, specify the following fields:

   • Plan name: Enter a name.
   • Plan project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Target project: Select from the list. If you are using a UDN, this is the namespace defined in OpenShift Virtualization.
4. Click Next.
5. On the Virtual machines page, select the virtual machines you want to migrate and click Next.
6. If you are using a UDN, verify that the IP address of the provider is outside the subnet of the UDN. If the IP address is within the subnet of the UDN, the migration fails.

7. On the Network map page, choose one of the following options:

   • Use an existing network map: Select an existing network map from the list.

     These are network maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use a new network map: Allows you to create a new network map by supplying the following data. This map is attached to this plan, which is then considered to be its owner. Maps that you create using this option are not available in the Use an existing network map option because each is created with an owner.

     Note

     You can create an ownerless network map, which you and others can use for additional migration plans, in the Network Maps section of the UI.

     • Source network: Select from the list.

     • Target network: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Network map name: Enter a name or let MTV automatically generate a name for the network map.
8. Click Next.

9. On the Storage map page, choose one of the following options:

   • Use an existing storage map: Select an existing storage map from the list.

     These are storage maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use new storage map: Allows you to create one or two new storage maps by supplying the following data. These maps are attached to this plan, which is then their owner. Maps that you create using this option are not available in the Use an existing storage map option because each is created with an owner.

     Note

     You can create an ownerless storage map, which you and others can use for additional migration plans, in the Storage Maps section of the UI.

     • Source storage: Select from the list.

     • Target storage: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Storage map name: Enter a name or let MTV automatically generate a name for the storage map.
10. Click Next.

11. On the Other settings (optional) page, you have the option to change the Transfer network of your migration plan.

    The transfer network is the network used to transfer the VMs to OpenShift Virtualization. This is the default transfer network of the provider.

    • Verify that the transfer network is in the selected target project.
    • To choose a different transfer network, select a different transfer network from the list.

    • Optional: To configure another OpenShift network in the OpenShift web console, click Networking > NetworkAttachmentDefinitions.

      To learn more about the different types of networks OpenShift supports, see Additional Networks in OpenShift Container Platform.

    • To adjust the maximum transmission unit (MTU) of the OpenShift transfer network, you must also change the MTU of the VMware migration network. For more information, see Selecting a migration network for a VMware source provider.
12. Click Next.
13. On the Hooks (optional) page, you can add a pre-migration hook, a post-migration hook, or both types of migration hooks. All are optional.
14. To add a hook, select the appropriate Enable hook checkbox.
15. Enter the Hook runner image.

16. Enter the Ansible playbook of the hook in the window.

    Note

    You cannot include more than one pre-migration hook or more than one post-migration hook in a migration plan.

17. Click Next.
18. On the Review and Create page, review the information displayed.

19. Edit any item by doing the following:

    1. Click its Edit step link.

       The wizard opens to the page where you defined the item.

    2. Edit the item.
    3. Either click Next to advance to the next page of the wizard, or click Skip to review to return directly to the Review and create page.

20. When you finish reviewing the details of the plan, click Create plan. MTV validates your plan.

    When your plan is validated, the Plan details page for your plan opens in the Details tab.

21. In addition to listing details based on your entries in the wizard, the Plan details tab includes the following two sections after the details of the plan:

    • Migration history: Details about successful and unsuccessful attempts to run the plan
    • Conditions: Any changes that need to be made to the plan so that it can run successfully

22. When you have fixed all conditions listed, you can run your plan from the Plans page.

    The Plan details page also includes five additional tabs, which are described in the table that follows:

    Table 12.1. Tabs of the Plan details page

    YAML	Virtual Machines	Resources	Mappings	Hooks
    Editable YAML Plan manifest based on your plan’s details including source provider, network and storage maps, VMs, and any issues with your VMs	The VMs the plan migrates	Calculated resources: VMs, CPUs, and total memory for both total VMs and running VMs	Editable specification of the network and storage maps used by your plan	Updatable specification of the hooks used by your plan, if any

Procedure

1. In the Red Hat OpenShift web console, click Operators > Installed Operators.

2. Click Migration Toolkit for Virtualization Operator.

   The Operator Details page opens in the Details tab.

3. Click the ForkliftController tab, and open the forklift-controller resource.

4. Click the forklift-controller YAML tab, and add the feature_ova_appliance_management field to the spec section of the forklift-controller custom resource (CR):

   Example:

   spec:
     ...
     feature_ova_appliance_management: 'true'

5. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

6. Click the provider to open the Details page. Click the provider’s YAML tab.

   For information about creating a provider, see Adding an Open Virtual Appliance (OVA) source provider.

7. Scroll down the provider’s YAML file to spec.settings.applianceManagement, and set applianceManagement to 'true':

   Example:

   spec:
     secret:
       ...
     settings:
       applianceManagement: 'true'
     type: ova
     ...

   • A temporary ConnectionTestFailed error message displays while the update is processing. You can ignore the error message.
8. Click the provider’s Details tab, and scroll down to the Conditions section. Verify that ApplianceManagementEnabled shows as True in the list of conditions.
9. In the Upload local OVA files section, click Browse to find a valid .ova file.

10. Click Upload.

    A success message confirms the file upload. After several seconds, the number of virtual machines increases under the Provider inventory section.

    • If your OVA appliance is large, you might receive a request timeout error message.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Network maps.

2. Click Create NetworkMap.

   The Create NetworkMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of network maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.
2. Click Create storage map > Create with form.

3. Specify the following:

   • Map name: Name of the storage map.
   • Project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Source storage: Select from the list.
   • Target storage: Select from the list
4. Optional: Click Add mapping to create additional storage maps, including mapping multiple storage sources to a single target storage class.

5. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Storage maps.

2. Click Create storage map > Create with YAML.

   The Create StorageMap page opens.

3. Enter the YAML or JSON definitions into the editor, or drag and drop a file into the editor.
4. If you enter YAML definitions, use the following:

5. Optional: To download your input, click Download.

6. Click Create.

   Your map appears in the list of storage maps.

Procedure

1. Access the Create provider interface OpenShift Virtualization by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click OpenShift Virtualization.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click OpenShift Virtualization.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click OpenShift Virtualization when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider
   • URL: URL of the endpoint of the API server

   • Service account bearer token: Token for a service account with cluster-admin privileges

     If both URL and Service account bearer token are left blank, the local OpenShift cluster is used.

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

6. Optional: Add access to the UI of the provider:

   1. On the Providers page, click the provider.

      The Provider details page opens.

   2. Click the Edit icon under External UI web link.

   3. Enter the link and click Save.

      Note

      If you do not enter a link, MTV attempts to calculate the correct link.

      • If MTV succeeds, the hyperlink of the field points to the calculated link.
      • If MTV does not succeed, the field remains empty.

Procedure

1. Access the Create OpenShift Virtualization provider interface by doing one of the following:

   1. In the Red Hat OpenShift web console, click Migration for Virtualization > Providers.

      1. Click Create Provider.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

      3. Click OpenShift Virtualization.

   2. If you have Administrator privileges, in the Red Hat OpenShift web console, click Migration for Virtualization > Overview.

      1. In the Welcome pane, click OpenShift Virtualization.

         If the Welcome pane is not visible, click Show the welcome card in the upper-right corner of the page, and click OpenShift Virtualization when the Welcome pane opens.

      2. Select a Project from the list. The default project shown depends on the active project of MTV.

         If the active project is All projects, then the default project is openshift-mtv. Otherwise, the default project is the same as the active project.

         If you have Administrator privileges, you can see all projects, otherwise, you can see only the projects you are authorized to work with.

2. Specify the following fields:

   • Provider resource name: Name of the source provider
   • URL: URL of the endpoint of the API server

   • Service account bearer token: Token for a service account with cluster-admin privileges

     If both URL and Service account bearer token are left blank, the local OpenShift cluster is used.

3. Choose one of the following options for validating CA certificates:

   • Use a custom CA certificate: Migrate after validating a custom CA certificate.
   • Use the system CA certificate: Migrate after validating the system CA certificate.

   • Skip certificate validation : Migrate without validating a CA certificate.

     1. To use a custom CA certificate, leave the Skip certificate validation switch toggled to left, and either drag the CA certificate to the text box or browse for it and click Select.
     2. To use the system CA certificate, leave the Skip certificate validation switch toggled to the left, and leave the CA certificate text box empty.
     3. To skip certificate validation, toggle the Skip certificate validation switch to the right.

4. Optional: Ask MTV to fetch a custom CA certificate from the provider’s API endpoint URL.

   1. Click Fetch certificate from URL. The Verify certificate window opens.

   2. If the details are correct, select the I trust the authenticity of this certificate checkbox, and then, click Confirm. If not, click Cancel, and then, enter the correct certificate information manually.

      Once confirmed, the CA certificate will be used to validate subsequent communication with the API endpoint.

5. Click Create provider to add and save the provider.

   The provider appears in the list of providers.

Procedure

1. In the Red Hat OpenShift web console, click Migration > Providers for virtualization.

2. Click the OpenShift Virtualization provider whose migration network you want to change.

   When the Providers detail page opens:

3. Click the Networks tab.
4. Click Set default transfer network.
5. Select a default transfer network from the list and click Save.

6. Configure a gateway in the network used for MTV migrations by completing the following steps:

   1. In the Red Hat OpenShift web console, click Networking > NetworkAttachmentDefinitions.
   2. Select the appropriate default transfer network NAD.
   3. Click the YAML tab.

   4. Add forklift.konveyor.io/route to the metadata:annotations section of the YAML, as in the following example:

      apiVersion: k8s.cni.cncf.io/v1
      kind: NetworkAttachmentDefinition
      metadata:
        name: localnet-network
        namespace: mtv-test
        annotations:
          forklift.konveyor.io/route: <IP address> 1

      1

      The NetworkAttachmentDefinition parameter is needed to configure an IP address for the interface, either from the Dynamic Host Configuration Protocol (DHCP) or statically. Configuring the IP address enables the interface to reach the configured gateway.

   5. Click Save.

Procedure

1. In the Red Hat OpenShift web console, click Migration for Virtualization > Migration plans.

2. Click Create plan.

   The Create migration plan wizard opens.

3. On the General page, specify the following fields:

   • Plan name: Enter a name.
   • Plan project: Select from the list.
   • Source provider: Select from the list.
   • Target provider: Select from the list.
   • Target project: Select from the list.
4. Click Next.
5. On the Virtual machines page, select the virtual machines you want to migrate and click Next.

6. On the Network map page, choose one of the following options:

   • Use an existing network map: Select an existing network map from the list.

     These are network maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and target provider as the ones you want to use in your plan.

   • Use a new network map: Allows you to create a new network map by supplying the following data. This map is attached to this plan, which is then considered to be its owner. Maps that you create using this option are not available in the Use an existing network map option because each is created with an owner.

     Note

     You can create an ownerless network map, which you and others can use for additional migration plans, in the Network Maps section of the UI.

     • Source network: Select from the list.

     • Target network: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Network map name: Enter a name or let MTV automatically generate a name for the network map.
7. Click Next.

8. On the Storage map page, choose one of the following options:

   • Use an existing storage map: Select an existing storage map from the list.

     These are storage maps available for all plans, and therefore, they are ownerless in terms of the system. If you select this option and choose a map, a copy of that map is attached to your plan, and your plan is the owner of that copy. Any changes you make to your copy do not affect the original plan or any copies that other users have.

     Note

     If you choose an existing map, be sure it has the same source provider and the same target provider as the ones you want to use in your plan.

   • Use new storage map: Allows you to create one or two new storage maps by supplying the following data. These maps are attached to this plan, which is then their owner. Maps that you create using this option are not available in the Use an existing storage map option because each is created with an owner.

     Note

     You can create an ownerless storage map, which you and others can use for additional migration plans, in the Storage Maps section of the UI.

     • Source storage: Select from the list.

     • Target storage: Select from the list.

       If needed, click Add mapping to add another mapping.

     • Storage map name: Enter a name or let MTV automatically generate a name for the storage map.
9. Click Next.

10. On the Other settings (optional) page, you have the option to change the Transfer network of your migration plan.

    The transfer network is the network used to transfer the VMs to OpenShift Virtualization. This is the default transfer network of the provider.

    • Verify that the transfer network is in the selected target project.
    • To choose a different transfer network, select a different transfer network from the list.

    • Optional: To configure another OpenShift network in the OpenShift web console, click Networking > NetworkAttachmentDefinitions.

      To learn more about the different types of networks OpenShift supports, see Additional Networks in OpenShift Container Platform.

    • To adjust the maximum transmission unit (MTU) of the OpenShift transfer network, you must also change the MTU of the VMware migration network. For more information, see Selecting a migration network for a VMware source provider.
11. Click Next.
12. On the Hooks (optional) page, you can add a pre-migration hook, a post-migration hook, or both types of migration hooks. All are optional.
13. To add a hook, select the appropriate Enable hook checkbox.
14. Enter the Hook runner image.

15. Enter the Ansible playbook of the hook in the window.

    Note

    You cannot include more than one pre-migration hook or more than one post-migration hook in a migration plan.

16. Click Next.
17. On the Review and Create page, review the information displayed.

18. Edit any item by doing the following:

    1. Click its Edit step link.

       The wizard opens to the page where you defined the item.

    2. Edit the item.
    3. Either click Next to advance to the next page of the wizard, or click Skip to review to return directly to the Review and create page.

19. When you finish reviewing the details of the plan, click Create plan. MTV validates your plan.

    When your plan is validated, the Plan details page for your plan opens in the Details tab.

20. In addition to listing details based on your entries in the wizard, the Plan details tab includes the following two sections after the details of the plan:

    • Migration history: Details about successful and unsuccessful attempts to run the plan
    • Conditions: Any changes that need to be made to the plan so that it can run successfully

21. When you have fixed all conditions listed, you can run your plan from the Plans page.

    The Plan details page also includes five additional tabs, which are described in the table that follows:

    Table 13.1. Tabs of the Plan details page

    YAML	Virtual Machines	Resources	Mappings	Hooks
    Editable YAML Plan manifest based on your plan’s details including source provider, network and storage maps, VMs, and any issues with your VMs	The VMs the plan migrates	Calculated resources: VMs, CPUs, and total memory for both total VMs and running VMs	Editable specification of the network and storage maps used by your plan	Updatable specification of the hooks used by your plan, if any