Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 5. Migrating virtual machines from the command line

You can migrate virtual machines to OpenShift Virtualization from the command line.

Important

5.1. Migrating virtual machines
Copiar enlace

You migrate virtual machines (VMs) from the command line (CLI) by creating MTV custom resources (CRs).

Important

You must specify a name for cluster-scoped CRs.

You must specify both a name and a namespace for namespace-scoped CRs.

As a Technology Preview, MTV supports migrations using OpenStack source providers.

Important

Migration using OpenStack source providers is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.

Note

Migration using OpenStack source providers only supports VMs that use only Cinder volumes.

Prerequisites

  • VMware only: You must have a VMware Virtual Disk Development Kit (VDDK) image in a secure registry that is accessible to all clusters.

Procedure

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

    $ cat << EOF | oc apply -f -
apiVersion: v1
kind: Secret
metadata:
  name: <secret>
  namespace: openshift-mtv
  ownerReferences:
    1 
    
    - apiVersion: forklift.konveyor.io/v1beta1
      kind: Provider
      name: <provider_name>
      uid: <provider_uid>
  labels:
    createdForProviderType: <provider_type>
    2 
    
type: Opaque
stringData:
  user: <user>
    3 
    
  password: <password>
    4 
    
  insecureSkipVerify: <true/false>
    5 
    
  domainName: <domain_name>
    6 
    
  projectName: <project_name>
    7 
    
  regionName: <region name>
    8 
    
  cacert: |
    9 
    
    <ca_certificate>
  url: <api_end_point>
    10 
    
  thumbprint: <vcenter_fingerprint>
    11 
    
EOF
    Copy to Clipboard Toggle word wrap
    1
    The ownerReferences section is optional.
    2
    Specify the type of source provider. Allowed values are ovirt, vsphere, and openstack. 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
    Specify the vCenter user, the RHV Manager user, or the OpenStack user.
    4
    Specify the user password.
    5
    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.
    6
    OpenStack only: Specify the domain name.
    7
    OpenStack only: Specify the project name.
    8
    OpenStack only: Specify the name of the OpenStack region.
    9
    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>.
    10
    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.
    11
    VMware only: Specify the vCenter SHA-1 fingerprint.

  2. Create a Provider manifest for the source provider: 

    $ cat << EOF | oc apply -f -
apiVersion: forklift.konveyor.io/v1beta1
kind: Provider
metadata:
  name: <provider>
  namespace: openshift-mtv
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: openshift-mtv
EOF
    Copy to Clipboard Toggle word wrap
    1
    Allowed values are ovirt, vsphere, and openstack.
    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: openshift-mtv
spec:
  provider:
    namespace: openshift-mtv
    name: <source_provider>
    1 
    
  id: <source_host_mor>
    2 
    
  ipAddress: <source_network_ip>
    3 
    
EOF
    Copy to Clipboard Toggle word wrap
    1
    Specify the name of the VMware Provider CR.
    2
    Specify the managed object reference (MOR) of the VMware host.
    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: openshift-mtv
spec:
  map:
    - destination:
        name: <pod>
        namespace: openshift-mtv
        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:
        id: <source_network_id>
        name: <source_network_name>
  provider:
    source:
      name: <source_provider>
      namespace: openshift-mtv
    destination:
      name: <destination_cluster>
      namespace: openshift-mtv
EOF
    Copy to Clipboard Toggle word wrap
    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 MOR, the RHV network UUID, or the OpenStack network UUID.
    4
    Specify a network attachment definition for each additional OpenShift Virtualization network.
    5
    Specify the namespace of the OpenShift Virtualization network attachment definition.

  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: openshift-mtv
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: openshift-mtv
    destination:
      name: <destination_cluster>
      namespace: openshift-mtv
EOF
    Copy to Clipboard Toggle word wrap
    1
    Allowed values are ReadWriteOnce and ReadWriteMany.
    2
    Specify the VMware data storage MOR, the RHV storage domain UUID, or the OpenStack volume_type UUID. For example, f2737930-b567-451a-9ceb-2887f6207009.

  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: openshift-mtv
spec:
  image: quay.io/konveyor/hook-runner
    1 
    
  playbook: |
    2 
    
    LS0tCi0gbmFtZTogTWFpbgogIGhvc3RzOiBsb2NhbGhvc3QKICB0YXNrczoKICAtIG5hbWU6IExv
    YWQgUGxhbgogICAgaW5jbHVkZV92YXJzOgogICAgICBmaWxlOiAiL3RtcC9ob29rL3BsYW4ueW1s
    IgogICAgICBuYW1lOiBwbGFuCiAgLSBuYW1lOiBMb2FkIFdvcmtsb2FkCiAgICBpbmNsdWRlX3Zh
    cnM6CiAgICAgIGZpbGU6ICIvdG1wL2hvb2svd29ya2xvYWQueW1sIgogICAgICBuYW1lOiB3b3Jr
    bG9hZAoK
EOF
    Copy to Clipboard Toggle word wrap
    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: openshift-mtv
spec:
  warm: true
    2 
    
  provider:
    source:
      name: <source_provider>
      namespace: openshift-mtv
    destination:
      name: <destination_cluster>
      namespace: openshift-mtv
  map:
    network:
    3 
    
      name: <network_map>
    4 
    
      namespace: openshift-mtv
    storage:
      name: <storage_map>
    5 
    
      namespace: openshift-mtv
  targetNamespace: openshift-mtv
  vms:
    6 
    
    - id: <source_vm>
    7 
    
    - name: <source_vm>
      hooks:
    8 
    
        - hook:
            namespace: openshift-mtv
            name: <hook>
    9 
    
          step: <step>
    10 
    
EOF
    Copy to Clipboard Toggle word wrap
    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
    You can add multiple network mappings.
    4
    Specify the name of the NetworkMap CR.
    5
    Specify the name of the StorageMap CR.
    6
    You can use either the id or the name parameter to specify the source VMs.
    7
    Specify the VMware VM MOR, RHV VM UUID or the OpenStack VM UUID.
    8
    Optional: You can specify up to two hooks for a VM. Each hook must run during a separate migration step.
    9
    Specify the name of the Hook CR.
    10
    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: openshift-mtv
spec:
  plan:
    name: <plan>
    2 
    
    namespace: openshift-mtv
  cutover: <cutover_time>
    3 
    
EOF
    Copy to Clipboard Toggle word wrap
    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 openshift-mtv -o yaml
    Copy to Clipboard Toggle word wrap

5.2. Obtaining the SHA-1 fingerprint of a vCenter host
Copiar enlace

You must obtain the SHA-1 fingerprint of a vCenter host in order to create a Secret CR.

Procedure

  • Run the following command: 

    $ openssl s_client \
    -connect <vcenter_host>:443 \
    1 
    
    < /dev/null 2>/dev/null \
    | openssl x509 -fingerprint -noout -in /dev/stdin \
    | cut -d '=' -f 2
    Copy to Clipboard Toggle word wrap
    1
    Specify the IP address or FQDN of the vCenter host.

    Example output

    01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF:01:23:45:67
    Copy to Clipboard Toggle word wrap

5.3. Canceling a migration
Copiar enlace

You can cancel an entire migration or individual virtual machines (VMs) while a migration is in progress from the command line interface (CLI).

Canceling an entire migration

  • Delete the Migration CR: 

    $ oc delete migration <migration> -n openshift-mtv
    1
    Copy to Clipboard Toggle word wrap
    1
    Specify the name of the Migration CR.

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: openshift-mtv
...
spec:
  cancel:
  - id: vm-102
    1 
    
  - id: vm-203
  - name: rhel8-vm
EOF
    Copy to Clipboard Toggle word wrap
    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 openshift-mtv -o yaml
    Copy to Clipboard Toggle word wrap
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat