IBM Cloud Orchestrator, Version 2.5.0.1

Migrating KVM compute nodes

When migrating a KVM region, you must also migrate all the KVM compute nodes in the region.

Procedure

From the discovery report, identify the KVM compute node that you want to migrate, and identify what the destination compute node in the IBM® Cloud Orchestrator V2.5.0.1 is.
Copy the KVM compute node migration script from the IBM Cloud Orchestrator V2.5.0.1 server to the selected destination compute node:
```
scp /opt/ico_install/V2501/installer/upgrade/kvm_compute_migrate.py \
    root@<destination_compute_node>:/tmp
```
Check if the /var/lib/nova/instances directory is mounted from shared storage. If so, mount this storage on the destination compute node and use the --skip-clone flag when running the migration script in te next step.
Log in to the selected destination compute node as user root and run the KVM compute node migration script by running the following command:
```
./kvm_compute_migrate.py [--skip-clone] <sourcecomputenode> <region>
```
where
[--skip-clone]

Should be specified if the /var/lib/nova/instances directory is mounted from shared storage and no virtual machine cloning is needed.

<sourcecomputenode>

Is the IP address of the KVM compute node in the IBM Cloud Orchestrator V2.4.0.2 region.

<region>

Is the IBM Cloud Manager with OpenStack controller which manages this compute node.

The migration script copies, clones (unless the --skip-clone flag is specified) and processes the managed instances from the source KVM compute node in the IBM Cloud Orchestrator V2.4.0.2 region to the destination compute node in the IBM Cloud Orchestrator V2.5.0.1 region so that the destination compute node is able to manage these instances when they are re-enabled.
Note: When all the instances on the compute node are migrated and the migration of the region is successfully completed, this compute node can be reinstalled with Red Hat Enterprise Linux 7.1 and redeployed as a new compute node if needed.
Repeat this procedure for each KVM compute node managed by the IBM Cloud Orchestrator V2.4.0.2 region that you are migrating. Ensure that all the KVM compute nodes in the region are migrated.