HP Matrix 7.2 KVM Private Cloud Getting Started Guide
4 Expand an existing cloud
This chapter describes how to configure a new VM host to make it ready for activation.
Checklist: Expanding the KVM Private Cloud
The following procedures describe how to add hosts to the Matrix KVM Private Cloud.
ProcedureTask
“Install RHEL 6.3 with KVM on the host before activation”
(page 23)
Install and configure prerequisite software on
the host.
“Bring up the host’s network on the Host management subnet”
(page 24)
“Activate a host” (page 24)Activate the host.
“Verify host activation” (page 24)Verify that the host was successfully activated.
“Deploy a virtual machine to the cloud” (page 26)Deploy additional virtual machines to the
cloud.
Install RHEL 6.3 with KVM on the host before activation
Before you can activate a host, you must install Red Hat Enterprise Linux 6.3 with KVM on the host.
The following sections describe special installation and configuration requirements required for
host activation to succeed.
Software
Install RHEL 6.3 with KVM with the following package prerequisites required for activation:
• python-netaddr• openssh-clients• avahi• compat-openldap
• •••fuse python-paramikoopenssl098ebind-utils
•• ••net-toolsntp python-pasteMySQL-python
••• •python-cheetahgreplibguestfs-mount python-qpid
•••• python-tempitapython-decoratorgawklibvirt
• •••libvirt-python python-sqlalchemypython-ldapsed
•• ••kpartxtunctl python-twisted-corepython-lxml
••• •python-memcachedrsync scsi-target-utilsvconfig python-twisted-web
Networking
Configure networking as follows:
1. Connect the eth0 or bond0 device to the Cloud connectivity subnet (Production network).
The IP address for the interface will be assigned when the host is activated.
2. Connect the eth1 or bond1 device to the Host management subnet (Management network).
The boot protocol for this network is DHCP. When this network interface starts, it acquires an
IP address from the Matrix KVM Admin Console appliance DHCP server. When the DHCP
server assigns an IP address, the host is available for activation.
3. Connect the eth2 or bond2 device to the Matrix OE access network (sometimes called the
Matrix management network). The boot protocol for this network is Static. This network interface
is used for the Matrix CMS to discover the KVM host for event monitoring in HP Systems Insight
Manager.
4. Include the following additional flags in the eth1 or bond1 configuration file:
Checklist: Expanding the KVM Private Cloud 23