Installing and using the Migration Toolkit for Virtualization

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.5
     installPlanApproval: Automatic
     name: mtv-operator
     source: redhat-operators
     sourceNamespace: openshift-marketplace
     startingCSV: "mtv-operator.v2.5.7"
   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

   Example output

   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 → Overview. The Settings list is on the right-hand side of the page.
2. In the Settings list, click the Edit icon of the setting you want to change.
3. Choose a setting from the list.
4. Click Save.

Procedure

1. In the Red Hat OpenShift web console, click Migration → NetworkMaps for virtualization.
2. Click Create NetworkMap.

3. Specify the following fields:

   • Name: Enter a name to display in the network mappings list.
   • Source provider: Select a source provider.
   • Target provider: Select a target provider.
4. Select a Source network and a Target namespace/network.
5. Optional: Click Add to create additional network mappings or to map multiple source networks to a single target network.
6. If you create an additional network mapping, select the network attachment definition as the target network.

7. Click Create.

   The network mapping is displayed on the NetworkMaps screen.

Procedure

1. In the Red Hat OpenShift web console, click Migration → StorageMaps for virtualization.
2. Click Create StorageMap.

3. Specify the following fields:

   • Name: Enter a name to display in the storage mappings list.
   • Source provider: Select a source provider.
   • Target provider: Select a target provider.

4. To create a storage mapping, click Add and map storage sources to target storage classes as follows:

   1. If your source provider is VMware vSphere, select a Source datastore and a Target storage class.
   2. If your source provider is Red Hat Virtualization, select a Source storage domain and a Target storage class.
   3. If your source provider is OpenStack, select a Source volume type and a Target storage class.
   4. If your source provider is a set of one or more OVA files, select a Source and a Target storage class for the dummy storage that applies to all virtual disks within the OVA files.
   5. If your storage provider is OpenShift Virtualization. select a Source storage class and a Target storage class.
   6. Optional: Click Add to create additional storage mappings, including mapping multiple storage sources to a single target storage class.

5. Click Create.

   The mapping is displayed on the StorageMaps page.

Procedure

1. In the Red Hat OpenShift web console, click Migration → Plans for virtualization.
2. Click Create plan.

3. Specify the following fields:

   • Plan name: Enter a migration plan name to display in the migration plan list.
   • Plan description: Optional: Brief description of the migration plan.
   • Source provider: Select a source provider.
   • Target provider: Select a target provider.

   • Target namespace: Do one of the following:

     • Select a target namespace from the list
     • Create a target namespace by typing its name in the text box, and then clicking create "<the_name_you_entered>"

   • You can change the migration transfer network for this plan by clicking Select a different network, selecting a network from the list, and then clicking Select.

     If you defined a migration transfer network for the OpenShift Virtualization provider and if the network is in the target namespace, the network that you defined is the default network for all migration plans. Otherwise, the pod network is used.

4. Click Next.
5. Select options to filter the list of source VMs and click Next.
6. Select the VMs to migrate and then click Next.
7. Select an existing network mapping or create a new network mapping.

8. . Optional: Click Add to add an additional network mapping.

   To create a new network mapping:

   • Select a target network for each source network.
   • Optional: Select Save current mapping as a template and enter a name for the network mapping.
9. Click Next.

10. Select an existing storage mapping, which you can modify, or create a new storage mapping.

    To create a new storage mapping:

    1. If your source provider is VMware, select a Source datastore and a Target storage class.
    2. If your source provider is Red Hat Virtualization, select a Source storage domain and a Target storage class.
    3. If your source provider is OpenStack, select a Source volume type and a Target storage class.
11. Optional: Select Save current mapping as a template and enter a name for the storage mapping.
12. Click Next.

13. Select a migration type and click Next.

    • Cold migration: The source VMs are stopped while the data is copied.

    • Warm migration: The source VMs run while the data is copied incrementally. Later, you will run the cutover, which stops the VMs and copies the remaining VM data and metadata.

      Note

      Warm migration is supported only from vSphere and Red Hat Virtualization.

14. Click Next.

15. Optional: You can create a migration hook to run an Ansible playbook before or after migration:

    1. Click Add hook.
    2. Select the Step when the hook will be run: pre-migration or post-migration.

    3. Select a Hook definition:

       • Ansible playbook: Browse to the Ansible playbook or paste it into the field.

       • Custom container image: If you do not want to use the default hook-runner image, enter the image path: <registry_path>/<image_name>:<tag>.

         Note

         The registry must be accessible to your Red Hat OpenShift cluster.

16. Click Next.

17. Review your migration plan and click Finish.

    The migration plan is saved on the Plans page.

    You can click the Options menu of the migration plan and select View details to verify the migration plan details.

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, 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 Migration details by VM screen opens, displaying the migration’s progress

   Warm migration only:

   • The precopy stage starts.
   • Click Cutover to complete the migration.

4. If the migration fails:

   1. Click Get logs to retrieve the migration logs.
   2. Click Get logs in the confirmation window that opens.
   3. Wait until Get logs changes to Download logs and then click the button to download the logs.

5. Click a migration’s Status, whether it failed or succeeded or is still ongoing, to view the details of the migration.

   The Migration details by VM screen opens, displaying the start and end times of the migration, the amount of data copied, and a progress pipeline for each VM being migrated.

6. Expand an individual VM to view its steps and the elapsed time and state of each step.

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.

Procedure

1. Retrieve the routes for the project:

   oc get route -n openshift-mtv

2. Retrieve the Inventory service route:

   $ oc get route <inventory_service> -n openshift-mtv

3. Retrieve the access token:

   $ TOKEN=$(oc whoami -t)

4. Retrieve the moRef of a VMware vSphere provider:

   $ curl -H "Authorization: Bearer $TOKEN"  https://<inventory_service_route>/providers/vsphere -k

5. Retrieve the datastores of a VMware vSphere source provider:

   $ curl -H "Authorization: Bearer $TOKEN"  https://<inventory_service_route>/providers/vsphere/<provider id>/datastores/ -k

   Example output

   [
     {
       "id": "datastore-11",
       "parent": {
         "kind": "Folder",
         "id": "group-s5"
       },
       "path": "/Datacenter/datastore/v2v_general_porpuse_ISCSI_DC",
       "revision": 46,
       "name": "v2v_general_porpuse_ISCSI_DC",
       "selfLink": "providers/vsphere/01278af6-e1e4-4799-b01b-d5ccc8dd0201/datastores/datastore-11"
     },
     {
       "id": "datastore-730",
       "parent": {
         "kind": "Folder",
         "id": "group-s5"
       },
       "path": "/Datacenter/datastore/f01-h27-640-SSD_2",
       "revision": 46,
       "name": "f01-h27-640-SSD_2",
       "selfLink": "providers/vsphere/01278af6-e1e4-4799-b01b-d5ccc8dd0201/datastores/datastore-730"
     },
    ...

Procedure

1. Create a Secret manifest for the source provider credentials:

   $ cat << EOF | oc apply -f -
   apiVersion: v1
   kind: Secret
   metadata:
     name: <secret>
     namespace: <namespace>
     ownerReferences: 1
       - apiVersion: forklift.konveyor.io/v1beta1
         kind: Provider
         name: <provider_name>
         uid: <provider_uid>
     labels:
       createdForProviderType: <provider_type> 2
       createdForResourceType: providers
   type: Opaque
   stringData: 3
     user: <user> 4
     password: <password> 5
     insecureSkipVerify: <true/false> 6
     domainName: <domain_name> 7
     projectName: <project_name> 8
     regionName: <region name> 9
     cacert: | 10
       <ca_certificate>
     url: <api_end_point> 11
     thumbprint: <vcenter_fingerprint> 12
     token: <service_account_bearer_token> 13
   EOF

   1

   The ownerReferences section is optional.

   2

   Specify the type of source provider. Allowed values are ovirt, vsphere, openstack, ova, and openshift. This label is needed to verify the credentials are correct when the remote system is accessible and, for RHV, to retrieve the Manager CA certificate when a third-party certificate is specified.

   3

   The stringData section for OVA is different and is described in a note that follows the description of the Secret manifest.

   4

   Specify the vCenter user, the RHV Manager user, or the OpenStack user.

   5

   Specify the user password.

   6

   Specify <true> to skip certificate verification, which proceeds with an insecure migration and then the certificate is not required. Insecure migration means that the transferred data is sent over an insecure connection and potentially sensitive data could be exposed. Specifying <false> verifies the certificate.

   7

   OpenStack only: Specify the domain name.

   8

   OpenStack only: Specify the project name.

   9

   OpenStack only: Specify the name of the OpenStack region.

   10

   RHV and OpenStack only: For RHV, enter the Manager CA certificate unless it was replaced by a third-party certificate, in which case, enter the Manager Apache CA certificate. You can retrieve the Manager CA certificate at https://<engine_host>/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA. For OpenStack, enter the CA certificate for connecting to the source environment. The certificate is not used when insecureSkipVerify is set to <true>.

   11

   Specify the API end point URL, for example, https://<vCenter_host>/sdk for vSphere, https://<engine_host>/ovirt-engine/api for RHV, or https://<identity_service>/v3 for OpenStack.

   12

   VMware only: Specify the vCenter SHA-1 fingerprint.

   13

   OpenShift only: Token for a service account with cluster-admin privileges.

   Note

   The stringData section for an OVA Secret manifest is as follows:

   stringData:
     url: <nfs_server:/nfs_path>

   where:
   nfs_server: An IP or hostname of the server where the share was created.
   nfs_path : The path on the server where the OVA files are stored.

2. Create a Provider manifest for the source provider:

   $ cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: Provider
   metadata:
     name: <source_provider>
     namespace: <namespace>
   spec:
     type: <provider_type> 1
     url: <api_end_point> 2
     settings:
       vddkInitImage: <registry_route_or_server_path>/vddk:<tag> 3
     secret:
       name: <secret> 4
       namespace: <namespace>
   EOF

   1

   Specify the type of source provider. Allowed values are ovirt, vsphere, openstack, ova, and openshift.

   2

   Specify the API end point URL, for example, https://<vCenter_host>/sdk for vSphere, https://<engine_host>/ovirt-engine/api for RHV, or https://<identity_service>/v3 for OpenStack.

   3

   VMware only: Specify the VDDK image that you created.

   4

   Specify the name of provider Secret CR.

3. VMware only: Create a Host manifest:

   $ cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: Host
   metadata:
     name: <vmware_host>
     namespace: <namespace>
   spec:
     provider:
       namespace: <namespace>
       name: <source_provider> 1
     id: <source_host_mor> 2
     ipAddress: <source_network_ip> 3
   EOF

   1

   Specify the name of the VMware Provider CR.

   2

   Specify the managed object reference (moRef) of the VMware host. To retrieve the moRef, see Retrieving a VMware vSphere moRef.

   3

   Specify the IP address of the VMware migration network.

4. Create a NetworkMap manifest to map the source and destination networks:

   $  cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: NetworkMap
   metadata:
     name: <network_map>
     namespace: <namespace>
   spec:
     map:
       - destination:
           name: <network_name>
           type: pod 1
         source: 2
           id: <source_network_id> 3
           name: <source_network_name>
       - destination:
           name: <network_attachment_definition> 4
           namespace: <network_attachment_definition_namespace> 5
           type: multus
         source:
           name: <network_attachment_definition> 6
           namespace: <network_attachment_definition_namespace> 7
           type: multus 8
     provider:
       source:
         name: <source_provider>
         namespace: <namespace>
       destination:
         name: <destination_provider>
         namespace: <namespace>
   EOF

   1

   Allowed values are pod and multus.

   2

   You can use either the id or the name parameter to specify the source network.

   3

   Specify the VMware network moRef, the RHV network UUID, or the OpenStack network UUID. To retrieve the moRef, see Retrieving a VMware vSphere moRef.

   4

   Specify a network attachment definition for each additional OpenShift Virtualization network.

   5

   Required only when type is multus. Specify the namespace of the OpenShift Virtualization network attachment definition.

   6

   Specify a network attachment definition for each additional OpenShift Virtualization network.

   7

   Required only when type is multus. Here, namespace can either be specified using the namespace property or with a name built as follows: <network_namespace>/<network_name>.

   8

   OpenShift only.

5. Create a StorageMap manifest to map source and destination storage:

   $ cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: StorageMap
   metadata:
     name: <storage_map>
     namespace: <namespace>
   spec:
     map:
       - destination:
           storageClass: <storage_class>
           accessMode: <access_mode> 1
         source:
           id: <source_datastore> 2
       - destination:
           storageClass: <storage_class>
           accessMode: <access_mode>
         source:
           id: <source_datastore>
     provider:
       source:
         name: <source_provider>
         namespace: <namespace>
       destination:
         name: <destination_provider>
         namespace: <namespace>
   EOF

   1

   Allowed values are ReadWriteOnce and ReadWriteMany.

   2

   Specify the VMware datastore moRef, the RHV storage domain UUID, or the OpenStack volume_type UUID. For example, f2737930-b567-451a-9ceb-2887f6207009. To retrieve the moRef, see Retrieving a VMware vSphere moRef.

   Note

   For OVA, the StorageMap can map only a single storage, which all the disks from the OVA are associated with, to a storage class at the destination. For this reason, the storage is referred to in the UI as "Dummy storage for source provider <provider_name>".

6. Optional: Create a Hook manifest to run custom code on a VM during the phase specified in the Plan CR:

   $  cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: Hook
   metadata:
     name: <hook>
     namespace: <namespace>
   spec:
     image: quay.io/konveyor/hook-runner 1
     playbook: | 2
       LS0tCi0gbmFtZTogTWFpbgogIGhvc3RzOiBsb2NhbGhvc3QKICB0YXNrczoKICAtIG5hbWU6IExv
       YWQgUGxhbgogICAgaW5jbHVkZV92YXJzOgogICAgICBmaWxlOiAiL3RtcC9ob29rL3BsYW4ueW1s
       IgogICAgICBuYW1lOiBwbGFuCiAgLSBuYW1lOiBMb2FkIFdvcmtsb2FkCiAgICBpbmNsdWRlX3Zh
       cnM6CiAgICAgIGZpbGU6ICIvdG1wL2hvb2svd29ya2xvYWQueW1sIgogICAgICBuYW1lOiB3b3Jr
       bG9hZAoK
   EOF

   1

   You can use the default hook-runner image or specify a custom image. If you specify a custom image, you do not have to specify a playbook.

   2

   Optional: Base64-encoded Ansible Playbook. If you specify a playbook, the image must be hook-runner.

7. Create a Plan manifest for the migration:

   $ cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: Plan
   metadata:
     name: <plan> 1
     namespace: <namespace>
   spec:
     warm: true 2
     provider:
       source:
         name: <source_provider>
         namespace: <namespace>
       destination:
         name: <destination_provider>
         namespace: <namespace>
     map: 3
       network: 4
         name: <network_map> 5
         namespace: <namespace>
       storage: 6
         name: <storage_map> 7
         namespace: <namespace>
     targetNamespace: <target_namespace>
     vms: 8
       - id: <source_vm> 9
       - name: <source_vm>
         namespace: <namespace> 10
         hooks: 11
           - hook:
               namespace: <namespace>
               name: <hook> 12
             step: <step> 13
   EOF

   1

   Specify the name of the Plan CR.

   2

   Specify whether the migration is warm or cold. If you specify a warm migration without specifying a value for the cutover parameter in the Migration manifest, only the precopy stage will run.

   3

   Specify only one network map and one storage map per plan.

   4

   Specify a network mapping even if the VMs to be migrated are not assigned to a network. The mapping can be empty in this case.

   5

   Specify the name of the NetworkMap CR.

   6

   Specify a storage mapping even if the VMs to be migrated are not assigned with disk images. The mapping can be empty in this case.

   7

   Specify the name of the StorageMap CR.

   8

   For all source providers except for OpenShift Virtualization, you can use either the id or the name parameter to specify the source VMs.
   OpenShift Virtualization source provider only: You can use only the name parameter, not the id. parameter to specify the source VMs.

   9

   Specify the VMware VM moRef, RHV VM UUID or the OpenStack VM UUID. To retrieve the moRef, see Retrieving a VMware vSphere moRef.

   10

   OpenShift Virtualization source provider only.

   11

   Optional: You can specify up to two hooks for a VM. Each hook must run during a separate migration step.

   12

   Specify the name of the Hook CR.

   13

   Allowed values are PreHook, before the migration plan starts, or PostHook, after the migration is complete.

8. Create a Migration manifest to run the Plan CR:

   $ cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: Migration
   metadata:
     name: <migration> 1
     namespace: <namespace>
   spec:
     plan:
       name: <plan> 2
       namespace: <namespace>
     cutover: <cutover_time> 3
   EOF

   1

   Specify the name of the Migration CR.

   2

   Specify the name of the Plan CR that you are running. The Migration CR creates a VirtualMachine CR for each VM that is migrated.

   3

   Optional: Specify a cutover time according to the ISO 8601 format with the UTC time offset, for example, 2021-04-04T01:23:45.678+09:00.

   You can associate multiple Migration CRs with a single Plan CR. If a migration does not complete, you can create a new Migration CR, without changing the Plan CR, to migrate the remaining VMs.

9. Retrieve the Migration CR to monitor the progress of the migration:

   $ oc get migration/<migration> -n <namespace> -o yaml

Canceling the migration of individual VMs

1. Add the individual VMs to the spec.cancel block of the Migration manifest:

   $ cat << EOF | oc apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: Migration
   metadata:
     name: <migration>
     namespace: <namespace>
   ...
   spec:
     cancel:
     - id: vm-102 1
     - id: vm-203
     - name: rhel8-vm
   EOF

   1

   You can specify a VM by using the id key or the name key.

   The value of the id key is the managed object reference, for a VMware VM, or the VM UUID, for a RHV VM.

2. Retrieve the Migration CR to monitor the progress of the remaining VMs:

   $ oc get migration/<migration> -n <namespace> -o yaml

Procedure

1. Retrieve the routes for the project:

   oc get route -n openshift-mtv

2. Retrieve the Inventory service route:

   $ oc get route <inventory_service> -n openshift-mtv

3. Retrieve the access token:

   $ TOKEN=$(oc whoami -t)

4. Trigger an HTTP GET request (for example, using Curl):

   $ curl -H "Authorization: Bearer $TOKEN" https://<inventory_service_route>/providers -k

5. Retrieve the UUID of a provider:

   $ curl -H "Authorization: Bearer $TOKEN"  https://<inventory_service_route>/providers/<provider> -k 1

   1 1 1

   Allowed values for the provider are vsphere, ovirt, and openstack.

6. Retrieve the VMs of a provider:

   $ curl -H "Authorization: Bearer $TOKEN"  https://<inventory_service_route>/providers/<provider>/<UUID>/vms -k

7. Retrieve the details of a VM:

   $ curl -H "Authorization: Bearer $TOKEN"  https://<inventory_service_route>/providers/<provider>/<UUID>/workloads/<vm> -k

   Example output

   {
       "input": {
           "selfLink": "providers/vsphere/c872d364-d62b-46f0-bd42-16799f40324e/workloads/vm-431",
           "id": "vm-431",
           "parent": {
               "kind": "Folder",
               "id": "group-v22"
           },
           "revision": 1,
           "name": "iscsi-target",
           "revisionValidated": 1,
           "isTemplate": false,
           "networks": [
               {
                   "kind": "Network",
                   "id": "network-31"
               },
               {
                   "kind": "Network",
                   "id": "network-33"
               }
           ],
           "disks": [
               {
                   "key": 2000,
                   "file": "[iSCSI_Datastore] iscsi-target/iscsi-target-000001.vmdk",
                   "datastore": {
                       "kind": "Datastore",
                       "id": "datastore-63"
                   },
                   "capacity": 17179869184,
                   "shared": false,
                   "rdm": false
               },
               {
                   "key": 2001,
                   "file": "[iSCSI_Datastore] iscsi-target/iscsi-target_1-000001.vmdk",
                   "datastore": {
                       "kind": "Datastore",
                       "id": "datastore-63"
                   },
                   "capacity": 10737418240,
                   "shared": false,
                   "rdm": false
               }
           ],
           "concerns": [],
           "policyVersion": 5,
           "uuid": "42256329-8c3a-2a82-54fd-01d845a8bf49",
           "firmware": "bios",
           "powerState": "poweredOn",
           "connectionState": "connected",
           "snapshot": {
               "kind": "VirtualMachineSnapshot",
               "id": "snapshot-3034"
           },
           "changeTrackingEnabled": false,
           "cpuAffinity": [
               0,
               2
           ],
           "cpuHotAddEnabled": true,
           "cpuHotRemoveEnabled": false,
           "memoryHotAddEnabled": false,
           "faultToleranceEnabled": false,
           "cpuCount": 2,
           "coresPerSocket": 1,
           "memoryMB": 2048,
           "guestName": "Red Hat Enterprise Linux 7 (64-bit)",
           "balloonedMemory": 0,
           "ipAddress": "10.19.2.96",
           "storageUsed": 30436770129,
           "numaNodeAffinity": [
               "0",
               "1"
           ],
           "devices": [
               {
                   "kind": "RealUSBController"
               }
           ],
           "host": {
               "id": "host-29",
               "parent": {
                   "kind": "Cluster",
                   "id": "domain-c26"
               },
               "revision": 1,
               "name": "IP address or host name of the vCenter host or RHV Engine host",
               "selfLink": "providers/vsphere/c872d364-d62b-46f0-bd42-16799f40324e/hosts/host-29",
               "status": "green",
               "inMaintenance": false,
               "managementServerIp": "10.19.2.96",
               "thumbprint": <thumbprint>,
               "timezone": "UTC",
               "cpuSockets": 2,
               "cpuCores": 16,
               "productName": "VMware ESXi",
               "productVersion": "6.5.0",
               "networking": {
                   "pNICs": [
                       {
                           "key": "key-vim.host.PhysicalNic-vmnic0",
                           "linkSpeed": 10000
                       },
                       {
                           "key": "key-vim.host.PhysicalNic-vmnic1",
                           "linkSpeed": 10000
                       },
                       {
                           "key": "key-vim.host.PhysicalNic-vmnic2",
                           "linkSpeed": 10000
                       },
                       {
                           "key": "key-vim.host.PhysicalNic-vmnic3",
                           "linkSpeed": 10000
                       }
                   ],
                   "vNICs": [
                       {
                           "key": "key-vim.host.VirtualNic-vmk2",
                           "portGroup": "VM_Migration",
                           "dPortGroup": "",
                           "ipAddress": "192.168.79.13",
                           "subnetMask": "255.255.255.0",
                           "mtu": 9000
                       },
                       {
                           "key": "key-vim.host.VirtualNic-vmk0",
                           "portGroup": "Management Network",
                           "dPortGroup": "",
                           "ipAddress": "10.19.2.13",
                           "subnetMask": "255.255.255.128",
                           "mtu": 1500
                       },
                       {
                           "key": "key-vim.host.VirtualNic-vmk1",
                           "portGroup": "Storage Network",
                           "dPortGroup": "",
                           "ipAddress": "172.31.2.13",
                           "subnetMask": "255.255.0.0",
                           "mtu": 1500
                       },
                       {
                           "key": "key-vim.host.VirtualNic-vmk3",
                           "portGroup": "",
                           "dPortGroup": "dvportgroup-48",
                           "ipAddress": "192.168.61.13",
                           "subnetMask": "255.255.255.0",
                           "mtu": 1500
                       },
                       {
                           "key": "key-vim.host.VirtualNic-vmk4",
                           "portGroup": "VM_DHCP_Network",
                           "dPortGroup": "",
                           "ipAddress": "10.19.2.231",
                           "subnetMask": "255.255.255.128",
                           "mtu": 1500
                       }
                   ],
                   "portGroups": [
                       {
                           "key": "key-vim.host.PortGroup-VM Network",
                           "name": "VM Network",
                           "vSwitch": "key-vim.host.VirtualSwitch-vSwitch0"
                       },
                       {
                           "key": "key-vim.host.PortGroup-Management Network",
                           "name": "Management Network",
                           "vSwitch": "key-vim.host.VirtualSwitch-vSwitch0"
                       },
                       {
                           "key": "key-vim.host.PortGroup-VM_10G_Network",
                           "name": "VM_10G_Network",
                           "vSwitch": "key-vim.host.VirtualSwitch-vSwitch1"
                       },
                       {
                           "key": "key-vim.host.PortGroup-VM_Storage",
                           "name": "VM_Storage",
                           "vSwitch": "key-vim.host.VirtualSwitch-vSwitch1"
                       },
                       {
                           "key": "key-vim.host.PortGroup-VM_DHCP_Network",
                           "name": "VM_DHCP_Network",
                           "vSwitch": "key-vim.host.VirtualSwitch-vSwitch1"
                       },
                       {
                           "key": "key-vim.host.PortGroup-Storage Network",
                           "name": "Storage Network",
                           "vSwitch": "key-vim.host.VirtualSwitch-vSwitch1"
                       },
                       {
                           "key": "key-vim.host.PortGroup-VM_Isolated_67",
                           "name": "VM_Isolated_67",
                           "vSwitch": "key-vim.host.VirtualSwitch-vSwitch2"
                       },
                       {
                           "key": "key-vim.host.PortGroup-VM_Migration",
                           "name": "VM_Migration",
                           "vSwitch": "key-vim.host.VirtualSwitch-vSwitch2"
                       }
                   ],
                   "switches": [
                       {
                           "key": "key-vim.host.VirtualSwitch-vSwitch0",
                           "name": "vSwitch0",
                           "portGroups": [
                               "key-vim.host.PortGroup-VM Network",
                               "key-vim.host.PortGroup-Management Network"
                           ],
                           "pNICs": [
                               "key-vim.host.PhysicalNic-vmnic4"
                           ]
                       },
                       {
                           "key": "key-vim.host.VirtualSwitch-vSwitch1",
                           "name": "vSwitch1",
                           "portGroups": [
                               "key-vim.host.PortGroup-VM_10G_Network",
                               "key-vim.host.PortGroup-VM_Storage",
                               "key-vim.host.PortGroup-VM_DHCP_Network",
                               "key-vim.host.PortGroup-Storage Network"
                           ],
                           "pNICs": [
                               "key-vim.host.PhysicalNic-vmnic2",
                               "key-vim.host.PhysicalNic-vmnic0"
                           ]
                       },
                       {
                           "key": "key-vim.host.VirtualSwitch-vSwitch2",
                           "name": "vSwitch2",
                           "portGroups": [
                               "key-vim.host.PortGroup-VM_Isolated_67",
                               "key-vim.host.PortGroup-VM_Migration"
                           ],
                           "pNICs": [
                               "key-vim.host.PhysicalNic-vmnic3",
                               "key-vim.host.PhysicalNic-vmnic1"
                           ]
                       }
                   ]
               },
               "networks": [
                   {
                       "kind": "Network",
                       "id": "network-31"
                   },
                   {
                       "kind": "Network",
                       "id": "network-34"
                   },
                   {
                       "kind": "Network",
                       "id": "network-57"
                   },
                   {
                       "kind": "Network",
                       "id": "network-33"
                   },
                   {
                       "kind": "Network",
                       "id": "dvportgroup-47"
                   }
               ],
               "datastores": [
                   {
                       "kind": "Datastore",
                       "id": "datastore-35"
                   },
                   {
                       "kind": "Datastore",
                       "id": "datastore-63"
                   }
               ],
               "vms": null,
               "networkAdapters": [],
               "cluster": {
                   "id": "domain-c26",
                   "parent": {
                       "kind": "Folder",
                       "id": "group-h23"
                   },
                   "revision": 1,
                   "name": "mycluster",
                   "selfLink": "providers/vsphere/c872d364-d62b-46f0-bd42-16799f40324e/clusters/domain-c26",
                   "folder": "group-h23",
                   "networks": [
                       {
                           "kind": "Network",
                           "id": "network-31"
                       },
                       {
                           "kind": "Network",
                           "id": "network-34"
                       },
                       {
                           "kind": "Network",
                           "id": "network-57"
                       },
                       {
                           "kind": "Network",
                           "id": "network-33"
                       },
                       {
                           "kind": "Network",
                           "id": "dvportgroup-47"
                       }
                   ],
                   "datastores": [
                       {
                           "kind": "Datastore",
                           "id": "datastore-35"
                       },
                       {
                           "kind": "Datastore",
                           "id": "datastore-63"
                       }
                   ],
                   "hosts": [
                       {
                           "kind": "Host",
                           "id": "host-44"
                       },
                       {
                           "kind": "Host",
                           "id": "host-29"
                       }
                   ],
                   "dasEnabled": false,
                   "dasVms": [],
                   "drsEnabled": true,
                   "drsBehavior": "fullyAutomated",
                   "drsVms": [],
                   "datacenter": null
               }
           }
       }
   }

Procedure

1. Click Home → Projects.
2. Locate the openshift-mtv project.
3. On the right side of the project, select Delete Project from the Options menu .
4. In the Delete Project pane, enter the project name and click Delete.
5. Click Administration → CustomResourceDefinitions.
6. Enter forklift in the Search field to locate the CRDs in the forklift.konveyor.io group.
7. On the right side of each CRD, select Delete CustomResourceDefinition from the Options menu .

Procedure

1. Delete the project:

   $ oc delete project openshift-mtv

2. Delete the CRDs:

   $ oc get crd -o name | grep 'forklift' | xargs oc delete

3. Delete the OAuthClient:

   $ oc delete oauthclient/forklift-ui

Collecting logs and CR information

1. Navigate to the directory where you want to store the must-gather data.

2. Run the oc adm must-gather command:

   $ oc adm must-gather --image=registry.redhat.io/migration-toolkit-virtualization/mtv-must-gather-rhel8:2.5.7

   The data is saved as /must-gather/must-gather.tar.gz. You can upload this file to a support case on the Red Hat Customer Portal.

3. Optional: Run the oc adm must-gather command with the following options to gather filtered data:

   • Namespace:

     $ oc adm must-gather --image=registry.redhat.io/migration-toolkit-virtualization/mtv-must-gather-rhel8:2.5.7 \
       -- NS=<namespace> /usr/bin/targeted

   • Migration plan:

     $ oc adm must-gather --image=registry.redhat.io/migration-toolkit-virtualization/mtv-must-gather-rhel8:2.5.7 \
       -- PLAN=<migration_plan> /usr/bin/targeted

   • Virtual machine:

     $ oc adm must-gather --image=registry.redhat.io/migration-toolkit-virtualization/mtv-must-gather-rhel8:2.5.7 \
       -- VM=<vm_id> NS=<namespace> /usr/bin/targeted 1

     1

     Specify the VM ID as it appears in the Plan CR.