Chapter 12. Live migration

Procedure

1. Edit the VM object to which you want to apply a live migration policy, and add the corresponding VM labels.

   1. Open the YAML configuration of the resource:

      $ oc edit vm <vm_name>

      Copy to Clipboard Toggle word wrap

   2. Adjust the required label values in the .spec.template.metadata.labels section of the configuration. For example, to mark the VM as a production VM for the purposes of migration policies, add the kubevirt.io/environment: production line:

      apiVersion: migrations.kubevirt.io/v1alpha1
      kind: VirtualMachine
      metadata:
        name: <vm_name>
        namespace: default
        labels:
          app: my-app
          environment: production
      spec:
        template:
          metadata:
            labels:
              kubevirt.io/domain: <vm_name>
              kubevirt.io/size: large
              kubevirt.io/environment: production
      # ...

      Copy to Clipboard Toggle word wrap
   3. Save and exit the configuration.

2. Configure a MigrationPolicy object with the corresponding labels. The following example configures a policy that applies to all VMs that are labeled as production:

   apiVersion: migrations.kubevirt.io/v1alpha1
   kind: MigrationPolicy
   metadata:
     name: <migration_policy>
   spec:
     selectors:
       namespaceSelector: 

   1

   
         hpc-workloads: "True"
         xyz-workloads-type: ""
       virtualMachineInstanceSelector: 

   2

   
         kubevirt.io/environment: "production"

   Copy to Clipboard Toggle word wrap

   1

   Specify project labels.

   2

   Specify VM labels.

3. Create the migration policy by running the following command:

   $ oc create -f <migration_policy>.yaml

   Copy to Clipboard Toggle word wrap

Procedure

1. Navigate to Virtualization VirtualMachines in the web console.

2. Take either of the following steps:

   • Click the Options menu beside the VM you want to migrate, hover over the Migrate option, and select Compute.
   • Open the VM details page of the VM you want to migrate, click the Actions menu, hover over the Migrate option, and select Compute.

3. In the Migrate Virtual Machine to a different Node dialog box, select either Automatically Selected Node or Specific Node.

   1. If you selected the Specific Node option, choose a node from the list.
4. Click Migrate Virtual Machine.

Procedure

1. Create a VirtualMachineInstanceMigration manifest for the VM that you want to migrate:

   apiVersion: kubevirt.io/v1
   kind: VirtualMachineInstanceMigration
   metadata:
     name: <migration_name>
   spec:
     vmiName: <vm_name>

   Copy to Clipboard Toggle word wrap

2. Create the object by running the following command:

   $ oc create -f <migration_name>.yaml

   Copy to Clipboard Toggle word wrap

   The VirtualMachineInstanceMigration object triggers a live migration of the VM. This object exists in the cluster for as long as the virtual machine instance is running, unless manually deleted.

Procedure

1. Navigate to Virtualization VirtualMachines in the web console.
2. Select Cancel Migration on the Options menu beside a VM.

Procedure

1. Create the cluster role as shown in the following example:

   apiVersion: rbac.authorization.k8s.io/v1
   kind: ClusterRole
   metadata:
     name: live-migration-role
   rules:
     - apiGroups:
         - forklift.konveyor.io
       resources:
         - '*'
       verbs:
         - get
         - list
         - watch
     - apiGroups:
         - ""
       resources:
         - secrets
         - namespaces
         - configmaps
         - persistentvolumes
         - persistentvolumeclaims
       verbs:
         - get
         - list
         - watch
         - create
         - update
         - patch
         - delete
     - apiGroups:
         - k8s.cni.cncf.io
       resources:
         - network-attachment-definitions
       verbs:
         - get
         - list
         - watch
     - apiGroups:
         - storage.k8s.io
       resources:
         - storageclasses
       verbs:
         - get
         - list
         - watch
     - apiGroups:
         - kubevirt.io
       resources:
         - virtualmachines
         - virtualmachines/finalizers
         - virtualmachineinstancemigrations
       verbs:
         - get
         - list
         - watch
         - create
         - update
         - patch
         - delete
     - apiGroups:
         - kubevirt.io
       resources:
         - kubevirts
         - virtualmachineinstances
       verbs:
         - get
         - list
         - watch
     - apiGroups:
         - cdi.kubevirt.io
       resources:
         - datavolumes
         - datavolumes/finalizers
       verbs:
         - get
         - list
         - watch
         - create
         - update
         - patch
         - delete
     - apiGroups:
         - apps
       resources:
         - deployments
       verbs:
         - get
         - list
         - watch
         - create
         - update
         - patch
         - delete
     - apiGroups:
         - instancetype.kubevirt.io
       resources:
         - virtualmachineclusterpreferences
         - virtualmachineclusterinstancetypes
       verbs:
         - get
         - list
         - watch
     - apiGroups:
         - instancetype.kubevirt.io
       resources:
         - virtualmachinepreferences
         - virtualmachineinstancetypes
       verbs:
         - get
         - list
         - watch
         - create
         - update
         - patch
         - delete

   Copy to Clipboard Toggle word wrap

2. Create the cluster role by running the following command:

   $ oc create -f <filename>.yaml

   Copy to Clipboard Toggle word wrap

3. Create a service account by running the following command:

   $ oc create serviceaccount <service_account_name> -n <service_account_namespace>

   Copy to Clipboard Toggle word wrap

4. Create a cluster role binding that links the service account to the cluster role, by running the following command:

   $ oc create clusterrolebinding <service_account_name> --clusterrole=<cluster_role_name> --serviceaccount=<service_account_namespace>:<service_account_name>

   Copy to Clipboard Toggle word wrap

5. Create a secret to hold the token by saving the following manifest as a YAML file:

   apiVersion: v1
   kind: Secret
   metadata:
     name: <name_of_secret>
     namespace: <namespace_for_service_account>
     annotations:
       kubernetes.io/service-account.name: <service_account_name>
   type: kubernetes.io/service-account-token

   Copy to Clipboard Toggle word wrap

6. Apply the manifest by running the following command:

   $ oc apply -f <filename>.yaml

   Copy to Clipboard Toggle word wrap

7. After the secret is populated, run the following command to get the service account bearer token:

   $ TOKEN_BASE64=$(oc get secret "<name_of_secret>" -n "<namespace_bound_to_service_account>" -o jsonpath='{.data.token}')
     TOKEN=$(echo "$TOKEN_BASE64" | base64 --decode)
     echo "$TOKEN"

   Copy to Clipboard Toggle word wrap
8. Copy the printed token.
9. In the Migration Toolkit for Virtualization (MTV) web console, when you create a provider and select OpenShift Virtualization, paste the token into the Service account bearer token field.