Chapter 12. Planning a migration of virtual machines from OVA

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

      Copy to Clipboard Toggle word wrap

      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:

    Expand

    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

    Show more

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'

   Copy to Clipboard Toggle word wrap

   Wait for the operator to redeploy the controller after updating the forklift-controller CR.

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, and add the applianceManagement field to the spec section. Set applianceManagement to 'true':

   Example:

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

   Copy to Clipboard Toggle word wrap
   • 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.