Download IBM Cloud Manager with OpenStack: Administrator Guide, version 4.1

Migrating the KVM Agent and CLI client
If you had the KVM Agent and CLI client installed on endpoints in your IBM SmartCloud Entry 3.2
environment, use the following information to migrate to the IBM Cloud Manager with OpenStack 4.1
compute nodes. You must complete the preparing to migrate steps, the upgrade steps, and the
completion steps.
Preparing to migrate the KVM Agent and CLI client
If you had the KVM Agent and CLI client installed on endpoints in your IBM SmartCloud Entry 3.2
environment, prepare to migrate the KVM nodes to IBM Cloud Manager with OpenStack 4.1.
About this task
Complete the pre-migration setup steps for the KVM compute nodes:
Procedure
1. Log in to the deployment system as the root user. This is the system where you installed IBM Cloud
Manager with OpenStack.
2. Change to the directory where you stored the files for the deployment of the OpenStack controller
node topology. In the following example, your-deployment-name is the name of your deployment.
$ cd your-deployment-name
3. Download the current environment for the topology. The name of the environment can be found in
the topology file.
$ knife environment show your-environment-name -d -F json > your-environment-name.json
4. Optional: If live migration was enabled on any of the KVM Agent nodes, update the environment by
using the following steps.
a. Change the openstack.compute.misc_nova JSON attribute in your environment file to add the
following item to the run list:
live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE
b. Upload the updated environment.
$ knife environment from file your-environment-name.json
5. Optional: Create node-specific attribute files.
Important: This step is only required when one or more of the KVM Agent nodes require different
attribute values from those that are defined in your environment file.
A separate node-specific attribute file must be created for each node that requires different attribute
values. Use the information recorded in the prerequisite steps to determine if any node-specific
attribute files are required. For example, a node might not use the default values for the
openstack.compute.state_path, openstack.compute.lock_path, and
openstack.compute.instances_path. The default values for these attributes, if they are not defined in
the environment file, are as follows:
v openstack.compute.state_path: /var/lib/nova
v openstack.compute.lock_path: /var/lib/nova/lock
v openstack.compute.instances_path: /var/lib/nova/instances
Also, a node may not use eth0 as the management network, eth1 as the virtual machine data
network, or br-eth1:eth1 as the data network bridge. These values are the default values for some of
the attributes in the environment file.
The following example node attribute file illustrates different paths, management network interface,
and data network bridge for a KVM Agent node:
Chapter 4. Migrating
65