Skip to content

creating-plan-wizard-ova.adoc

Latest commit

 

History

History
187 lines (152 loc) · 9.28 KB

creating-plan-wizard-ova.adoc

File metadata and controls

187 lines (152 loc) · 9.28 KB
Raw

Creating an Open Virtualization Appliance (OVA) migration plan by using the MTV wizard

You can migrate Open Virtual Appliance (OVA) files that were created by {vmw} vSphere by using the {project-full} plan creation wizard.

The wizard is designed to lead you step-by-step in creating a migration plan.

Warning

Do not include virtual machines with guest-initiated storage connections, such as Internet Small Computer Systems Interface (iSCSI) connections or Network File System (NFS) mounts. These require either additional planning before migration or reconfiguration after migration.

This prevents concurrent disk access to the storage the guest points to.
Important

A plan cannot contain more than 500 VMs or 500 disks.
Important

When you click Create plan on the Review and create page of the wizard, {project-first} validates your plan. If everything is OK, the Plan details page for your plan opens. This page contains settings that do not appear in the wizard, but are important. Be sure to read and follow the instructions for this page carefully, even though it is outside the plan creation wizard. The page can be opened later, any time before you run the plan, so you can come back to it if needed.
Prerequisites

  • Have an OVA source provider and a {virt} destination provider. For more information, see Adding an Open Virtual Appliance (OVA) source provider or Adding {a-virt} destination provider.

  • If you plan to create a Network map or a Storage map that will be used by more than one migration plan, create it in the Network maps or Storage maps page of the UI before you create a migration plan that uses that map.

  • If you are using a user-defined network (UDN), note the name of its namespace as defined in {virt}.

Procedure

  1. In the {ocp} 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 project: Click the list and do one of the following:

      1. Select an existing project from the list.

      2. Create a new project by clicking Create project and doing the following:

        1. Enter the Name of the project. A project name must consist of lowercase alphanumeric characters or -. A project name must start and end with alphanumeric characters. For example, my-name or 123-abc.

        2. Optional: Enter a Display name for the project.

        3. Optional: Enter a Description of the project.

        4. Click Create Project.

  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 {project-short} 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 {project-short} 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 {virt}. 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 {ocp-short} network in the {ocp-short} web console, click Networking > NetworkAttachmentDefinitions.

      To learn more about the different types of networks {ocp-short} supports, see Additional Networks in OpenShift Container Platform.

    • To adjust the maximum transmission unit (MTU) of the {ocp-short} 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. {project-short} 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 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