Chapter 9. Migrating virtual machines from OpenStack

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.
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 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 will then be 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. For each map, specify the following. 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 on which 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:

    Expand

    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

    Show more

Procedure

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

   The Plans list displays the source and target providers, the number of virtual machines (VMs) being migrated, the status, the date that the migration started, and the description of each plan.

2. Click Start beside a migration plan to start the migration.

3. Click Start in the confirmation window that opens.

   The plan’s Status changes to Running, and the migration’s progress is displayed.

   Warning

   Do not take a snapshot of a VM after you start a migration. Taking a snaphot after a migration starts might cause the migration to fail.

4. Optional: Click the links in the migration’s Status to see its overall status and the status of each VM:

   • The link on the left indicates whether the migration failed, succeeded, or is ongoing. It also reports the number of VMs whose migration succeeded, failed, or was canceled.

   • The link on the right opens the Virtual Machines tab of the Plan Details page. For each VM, the tab displays the following data:

     • The name of the VM
     • The start and end times of the migration
     • The amount of data copied

     • A progress pipeline for the VM’s migration

       Warning

       vMotion, including svMotion, and relocation must be disabled for VMs that are being imported to avoid data corruption.

5. Optional: To view your migration’s logs, either as it is running or after it is completed, perform the following actions:

   1. Click the Virtual Machines tab.

   2. Click the arrow (>) to the left of the virtual machine whose migration progress you want to check.

      The VM’s details are displayed.

   3. In the Pods section, in the Pod links column, click the Logs link.

      The Logs tab opens.

      Note

      Logs are not always available. The following are common reasons for logs not being available:

      • The migration is from OpenShift Virtualization to OpenShift Virtualization. In this case, virt-v2v is not involved, so no pod is required.
      • No pod was created.
      • The pod was deleted.
      • The migration failed before running the pod.
   4. To see the raw logs, click the Raw link.
   5. To download the logs, click the Download link.

Procedure

1. In the Red Hat OpenShift web console, click Plans for virtualization.
2. Click the name of a running migration plan to view the migration details.
3. Select one or more VMs and click Cancel.

4. Click Yes, cancel to confirm the cancellation.

   In the Migration details by VM list, the status of the canceled VMs is Canceled. The unmigrated and the migrated virtual machines are not affected.