Pacemaker 1.1 Pacemaker Remote en US

Pacemaker Remote
Extending High Availablity into Virtual Nodes

David Vossel
Pacemaker Remote
Pacemaker Remote
Extending High Availablity into Virtual Nodes
Edition 1
Author David Vossel dvossel@redhat.com
Copyright 2009-2013 David Vossel.
The text of and illustrations in this document are licensed under a Creative Commons Attribution
Share Alike 3.0 Unported license ("CC-BY-SA")
1
.
In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide
the URL for the original version.
In addition to the requirements of this license, the following activities are looked upon favorably:
1. If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email
notification to the authors of your intent to redistribute at least thirty days before your manuscript
or media freeze, to give the authors time to provide updated documents. This notification should
describe modifications, if any, made to the document.
2. All substantive modifications (including deletions) be either clearly marked up in the document or
else described in an attachment to the document.
3. Finally, while it is not mandatory under this license, it is considered good form to offer a free copy
of any hardcopy or CD-ROM expression of the author(s) work.
The document exists as both a reference and deployment guide for the Pacemaker Remote service.
The KVM and Linux Container walk-through tutorials will use:
1. Fedora 18 as the host operating system
2. Pacemaker Remote to perform resource management within virtual nodes
3. libvirt to manage KVM and LXC virtual nodes
4. Corosync to provide messaging and membership services on the host nodes
5. Pacemaker to perform resource management on host nodes
1
An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/
iii
Table of Contents
1. Extending High Availability Cluster into Virtual Nodes 1
1.1. Overview ...................................................................................................................... 1
1.2. Terms ........................................................................................................................... 1
1.3. Version Info .................................................................................................................. 2
1.4. Virtual Machine Use Case ............................................................................................. 2
1.5. Baremetal remote-node Use Case ................................................................................. 3
1.6. Linux Container Use Case ............................................................................................ 3
1.7. Expanding the Cluster Stack ......................................................................................... 4
1.7.1. Traditional HA Stack .......................................................................................... 4
1.7.2. Remote-Node Enabled HA Stack Using Virtual guest nodes ................................. 4
2. KVM Remote-node Quick Example 5
2.1. Mile High View of Configuration Steps ........................................................................... 5
2.2. What those steps just did .............................................................................................. 6
2.3. Accessing Cluster from Remote-node ............................................................................ 6
3. Configuration Explained 7
3.1. Container remote-node Resource Options ...................................................................... 7
3.2. Baremetal remote-node Options .................................................................................... 7
3.3. Host and Guest Authentication ...................................................................................... 8
3.4. Pacemaker and pacemaker_remote Options .................................................................. 8
4. KVM Walk-through 9
4.1. Step 1: Setup the Host ................................................................................................. 9
4.1.1. SElinux and Firewall ........................................................................................... 9
4.1.2. Install Cluster Software ....................................................................................... 9
4.1.3. Setup Corosync ............................................................................................... 10
4.1.4. Verify Cluster Software ..................................................................................... 10
4.1.5. Install Virtualization Software ............................................................................ 11
4.2. Step2: Create the KVM guest ...................................................................................... 11
4.2.1. Setup Guest Network ....................................................................................... 11
4.2.2. Setup Pacemaker Remote ................................................................................ 12
4.2.3. Verify Host Connection to Guest ....................................................................... 12
4.3. Step3: Integrate KVM guest into Cluster. ...................................................................... 13
4.3.1. Start the Cluster ............................................................................................... 13
4.3.2. Integrate KVM Guest as remote-node ............................................................... 14
4.3.3. Starting Resources on KVM Guest .................................................................... 14
4.3.4. Testing Remote-node Recovery and Fencing ..................................................... 15
4.3.5. Accessing Cluster Tools from Remote-node ...................................................... 16
5. Baremetal Walk-through 17
5.1. Step 1: Setup ............................................................................................................. 17
5.1.1. SElinux and Firewall Considerations .................................................................. 17
5.1.2. Setup Pacemaker Remote on Baremetal remote-node ....................................... 17
5.1.3. Verify cluster-node Connection to baremetal-node .............................................. 18
5.1.4. Install cluster-node Software ............................................................................. 19
5.1.5. Setup Corosync on cluster-nodes ...................................................................... 19
5.1.6. Start Pacemaker on cluster-nodes ..................................................................... 19
5.1.7. Integrate Baremetal remote-node into Cluster .................................................... 20
5.1.8. Starting Resources on baremetal remote-node .................................................. 21
5.1.9. Fencing baremetal remote-nodes ...................................................................... 21
5.1.10. Accessing Cluster Tools from a Baremetal remote-node ................................... 21
6. Linux Container (LXC) Walk-through 23
Pacemaker Remote
iv
6.1. Step 1: Setup LXC Host .............................................................................................. 23
6.1.1. SElinux and Firewall Rules ............................................................................... 23
6.1.2. Install Cluster Software on Host ........................................................................ 24
6.1.3. Configure Corosync .......................................................................................... 24
6.1.4. Verify Cluster ................................................................................................... 24
6.2. Step 2: Setup LXC Environment .................................................................................. 25
6.2.1. Install Libvirt LXC software ............................................................................... 25
6.2.2. Generate Libvirt LXC domains .......................................................................... 25
6.2.3. Generate the Authkey ....................................................................................... 26
6.3. Step 3: Integrate LXC guests into Cluster. .................................................................... 26
6.3.1. Start Cluster ..................................................................................................... 26
6.3.2. Integrate LXC Guests as remote-nodes ............................................................. 27
6.3.3. Starting Resources on LXC Guests ................................................................... 27
6.3.4. Testing LXC Guest Failure ............................................................................... 28
7. Future Features 29
7.1. Libvirt Sandbox Support .............................................................................................. 29
7.2. Bare-metal Support ..................................................................................................... 29
7.3. KVM Migration Support ............................................................................................... 29
A. Revision History 31
Index 33
v
List of Tables
3.1. Metadata Options for configuring KVM/LXC resources as remote-nodes .................................. 7
vi
Chapter 1.
1
Extending High Availability Cluster into
Virtual Nodes
Table of Contents
1.1. Overview .............................................................................................................................. 1
1.2. Terms ................................................................................................................................... 1
1.3. Version Info .......................................................................................................................... 2
1.4. Virtual Machine Use Case ..................................................................................................... 2
1.5. Baremetal remote-node Use Case ......................................................................................... 3
1.6. Linux Container Use Case .................................................................................................... 3
1.7. Expanding the Cluster Stack ................................................................................................. 4
1.7.1. Traditional HA Stack .................................................................................................. 4
1.7.2. Remote-Node Enabled HA Stack Using Virtual guest nodes ......................................... 4
1.1. Overview
The recent addition of the pacemaker_remote service supported by Pacemaker version
1.1.10 and greater allows nodes not running the cluster stack (pacemaker+corosync) to
integrate into the cluster and have the cluster manage their resources just as if they were a real
cluster node. This means that pacemaker clusters are now capable of managing both launching
virtual environments (KVM/LXC) as well as launching the resources that live within those virtual
environments without requiring the virtual environments to run pacemaker or corosync.
1.2. Terms
cluster-node - A node running the High Availability stack (pacemaker + corosync)
remote-node - A node running pacemaker_remote without the rest of the High Availability stack.
There are two types of remote-nodes, container and baremetal.
container - A pacemaker resource that contains additional resources. For example, a KVM virtual
machine resource that contains a webserver resource.
container remote-node - A virtual guest remote-node running the pacemaker_remote service.
This describes a specific remote-node use case where a virtual guest resource managed by the
cluster is both started by the cluster and integrated into the cluster as a remote-node.
baremetal - Term used to describe an environment that is not virtualized.
baremetal remote-node - A baremetal hardware node running pacemaker_remote. This describes
a specific remote-node use case where a hardware node not running the High Availability stack is
integrated into the cluster as a remote-node through the use of pacemaker_remote.
pacemaker_remote - A service daemon capable of performing remote application management
within guest nodes (baremetal, kvm, and lxc) in both pacemaker cluster environments and standalone
(non-cluster) environments. This service is an enhanced version of pacemakers local resource
manage daemon (LRMD) that is capable of managing and monitoring LSB, OCF, upstart, and
systemd resources on a guest remotely. It also allows for most of pacemakers cli tools (crm_mon,
crm_resource, crm_master, crm_attribute, ect..) to work natively on remote-nodes.
Chapter 1. Extending High Availability Cluster into Virtual Nodes
2
LXC - A Linux Container defined by the libvirt-lxc Linux container driver. http://libvirt.org/drvlxc.html
1.3. Version Info
This feature is in ongoing development.
Pacemaker v1.1.10
Initial pacemaker_remote daemon and integration support.
Only supports pacemaker in KVM/LXC environments.
pacemaker_remote daemon unit test suite.
Known bugs include (These are likely resolved if you have received an 1.1.10.x point release):
Errors when setting remote-node attributes, Failures when stopping orphaned (deleted from cib
while running) remote-nodes, Fixes remote-node usage in asymmetric clusters.
Currently in Master github branch and scheduled for Pacemaker v1.1.11
Baremetal remote-node support.
Improvements to scaling remote-node integration. Performance testing here included 16
cluster nodes running 64 remote-nodes living in LXC containers. As part of this testing, several
performance enhancements were introduced into the integration code.
CTS tests. RemoteLXC and RemoteBaremetal. These two CTS tests allow us to perform automated
verification of pacemaker_remote integration.
Fixes for known bugs in 1.1.10 release.
1.4. Virtual Machine Use Case
The use of pacemaker_remote in virtual machines solves a deployment scenario that has traditionally
been difficult to solve.
"I want a pacemaker cluster to manage virtual machine resources, but I also
want pacemaker to be able to manage the resources that live within those
virtual machines."
In the past, users desiring this deployment had to make a decision. They would either have to sacrifice
the ability of monitoring resources residing within virtual guests by running the cluster stack on the
baremetal nodes, or run another cluster instance on the virtual guests where they potentially run into
corosync scalability issues. There is a third scenario where the virtual guests run the cluster stack and
join the same network as the baremetal nodes, but that can quickly hit issues with scalability as well.
With the pacemaker_remote service we have a new option.
The baremetal cluster-nodes run the cluster stack (paceamaker+corosync).
The virtual remote-nodes run the pacemaker_remote service (nearly zero configuration required on
the virtual machine side)
The cluster stack on the cluster-nodes launch the virtual machines and immediately connect to the
pacemaker_remote service, allowing the virtual machines to integrate into the cluster just as if they
were a real cluster-node.
Baremetal remote-node Use Case
3
The key difference here between the virtual machine remote-nodes and the cluster-nodes is that the
remote-nodes are not running the cluster stack. This means the remote nodes will never become
the DC, and they do not take place in quorum. On the other hand this also means that remote-
nodes are not bound to the scalability limits associated with the cluster stack either. No 16 node
corosync member limits to deal with. That isnt to say remote-nodes can scale indefinitely, but it
is known that remote-nodes scale horizontally much further than cluster-nodes. Other than the quorum
limitation, these remote-nodes behave just like cluster nodes in respects to resource management.
The cluster is fully capable of managing and monitoring resources on each remote-node. You can
build constraints against remote-nodes, put them in standby, or whatever else youd expect to be
able to do with normal cluster-nodes. They even show up in the crm_mon output as you would expect
cluster-nodes to.
To solidify the concept, below is an example deployment that is very similar to an actual deployment
we test in our developer environment to verify remote-node scalability.
16 cluster-nodes running corosync+pacemaker stack.
64 pacemaker managed virtual machine resources running pacemaker_remote configured as
remote-nodes.
64 pacemaker managed webserver and database resources configured to run on the 64 remote-
nodes.
With this deployment you would have 64 webservers and databases running on 64 virtual machines
on 16 hardware nodes all of which are managed and monitored by the same pacemaker deployment.
It is known that pacemaker_remote can scale to these lengths and possibly much further depending
on the specific scenario.
1.5. Baremetal remote-node Use Case
"I want my traditional High Availability cluster to scale beyond the limits
imposed by the corosync messaging layer."
Ultimately the primary advantage of baremetal remote-nodes over traditional nodes running
the Corosync+Pacemaker stack is scalability. There are likely some other use cases related to
geographically distributed HA clusters that baremetal remote-nodes may serve a purpose in, but those
use cases not well understood at this point. The only limitations baremetal remote-nodes have that
cluster-nodes do not is the ability to take place in cluster quorum, and the ability to execute fencing
agents via stonith. That is not to say however that fencing of a baremetal node works any differently
than that of a normal cluster-node. The Pacemaker policy engine understands how to fence baremetal
remote-nodes. As long as a fencing device exists, the cluster is capable of ensuring baremetal nodes
are fenced in the exact same way as normal cluster-nodes are fenced.
1.6. Linux Container Use Case
I want to isolate and limit the system resources (cpu, memory, filesystem)
a cluster resource can consume without using virtual machines.
Using pacemaker_remote with Linux containers (libvirt-lxc) opens up some interesting possibilities
for isolating resources in the cluster without the use of a hypervisor. We now have the ability to both
define a contained environment with cpu and memory utilization limits and then assign resources to
that contained environment all managed from within pacemaker. The LXC Walk-through section of this
document outlines how pacemaker_remote can be used to bring Linux containers into the cluster as
remote-nodes capable of executing resources.
Chapter 1. Extending High Availability Cluster into Virtual Nodes
4
1.7. Expanding the Cluster Stack
1.7.1. Traditional HA Stack
1.7.2. Remote-Node Enabled HA Stack Using Virtual guest nodes
Chapter 2.
5
KVM Remote-node Quick Example
Table of Contents
2.1. Mile High View of Configuration Steps ................................................................................... 5
2.2. What those steps just did ...................................................................................................... 6
2.3. Accessing Cluster from Remote-node .................................................................................... 6
If you already know how to use pacemaker, youll likely be able to grasp this new concept of remote-
nodes by reading through this quick example without having to sort through all the detailed walk-
through steps. Here are the key configuration ingredients that make this possible using libvirt and KVM
virtual guests. These steps strip everything down to the very basics.
2.1. Mile High View of Configuration Steps
Put an authkey with this path, /etc/pacemaker/authkey, on every cluster-
node and virtual machine. This secures remote communication and authentication.
Run this command if you want to make a somewhat random authkey.
dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1
Install pacemaker_remote packages on every virtual machine, enable
pacemaker_remote on startup, and poke hole in firewall for tcp port 3121.
yum install pacemaker-remote resource-agents
systemctl enable pacemaker_remote
# If you just want to see this work, disable iptables and ip6tables on most distros.
# You may have to put selinux in permissive mode as well for the time being.
firewall-cmd --add-port 3121/tcp --permanent
Give each virtual machine a static network address and unique hostname
Tell pacemaker to launch a virtual machine and that the virtual machine
is a remote-node capable of running resources by using the "remote-node"
meta-attribute.
with pcs
# pcs resource create vm-guest1 VirtualDomain hypervisor="qemu:///system" config="vm-
guest1.xml" meta +remote-node=guest1+
raw xml
<primitive class="ocf" id="vm-guest1" provider="heartbeat" type="VirtualDomain">
<instance_attributes id="vm-guest-instance_attributes">
<nvpair id="vm-guest1-instance_attributes-hypervisor" name="hypervisor"
value="qemu:///system"/>
<nvpair id="vm-guest1-instance_attributes-config" name="config" value="guest1.xml"/
>
</instance_attributes>
<operations>
<op id="vm-guest1-interval-30s" interval="30s" name="monitor"/>
</operations>
Chapter 2. KVM Remote-node Quick Example
6
<meta_attributes id="vm-guest1-meta_attributes">
<nvpair id="vm-guest1-meta_attributes-remote-node" name="remote-node"
value="guest1"/>
</meta_attributes>
</primitive>
In the example above the meta-attribute remote-node=guest1 tells pacemaker that this resource is a
remote-node with the hostname guest1 that is capable of being integrated into the cluster. The cluster
will attempt to contact the virtual machines pacemaker_remote service at the hostname guest1 after it
launches.
2.2. What those steps just did
Those steps just told pacemaker to launch a virtual machine called vm-guest1 and integrate that
virtual machine as a remote-node called guest1.
Example crm_mon output after guest1 is integrated into cluster.
Last updated: Wed Mar 13 13:52:39 2013
Last change: Wed Mar 13 13:25:17 2013 via crmd on node1
Stack: corosync
Current DC: node1 (24815808) - partition with quorum
Version: 1.1.10
2 Nodes configured, unknown expected votes
2 Resources configured.
Online: [ node1 guest1]
vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1
Now, you could place a resource, such as a webserver on guest1.
# pcs resource create webserver apache params configfile=/etc/httpd/conf/httpd.conf op
monitor interval=30s
# pcs constraint webserver prefers guest1
Now the crm_mon output would show a webserver launched on the guest1 remote-node.
Last updated: Wed Mar 13 13:52:39 2013
Last change: Wed Mar 13 13:25:17 2013 via crmd on node1
Stack: corosync
Version: 1.1.10
Online: [ node1 guest1]
vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1
webserver (ocf::heartbeat::apache): Started guest1
2.3. Accessing Cluster from Remote-node
It is worth noting that after guest1 is integrated into the cluster, all the pacemaker cli tools immediately
become available to the remote node. This means things like crm_mon, crm_resource, and
crm_attribute will work natively on the remote-node as long as the connection between the remote-
node and cluster-node exists. This is particularly important for any master/slave resources executing
on the remote-node that need access to crm_master to set the nodes transient attributes.
Chapter 3.
7
Configuration Explained
Table of Contents
3.1. Container remote-node Resource Options .............................................................................. 7
3.2. Baremetal remote-node Options ............................................................................................ 7
3.3. Host and Guest Authentication .............................................................................................. 8
3.4. Pacemaker and pacemaker_remote Options .......................................................................... 8
The walk-through examples use some of these options, but dont explain exactly what they mean or
do. This section is meant to be the go-to resource for all the options available for configuring remote-
nodes.
3.1. Container remote-node Resource Options
When configuring a virtual machine or lxc resource to act as a remote-node, these are the metadata
options available to both enable the resource as a remote-node and define the connection parameters.
Table 3.1. Metadata Options for configuring KVM/LXC resources as remote-nodes
Option Default Description
remote-
node
<none> The name of the remote-node this resource defines. This both
enables the resource as a remote-node and defines the unique
name used to identify the remote-node. If no other parameters
are set, this value will also be assumed as the hostname to
connect to at port 3121. WARNING This value cannot overlap
with any resource or node IDs.
remote-
port
3121 Configure a custom port to use for the guest connection to
pacemaker_remote.
remote-
addr
remote-
node value
used as
hostname
The ip address or hostname to connect to if remote-nodes
name is not the hostname of the guest.
remote-
connect-
timeout
60s How long before a pending guest connection will time out.
3.2. Baremetal remote-node Options
Baremetal remote-nodes are defined by a connection resource. That connection resource has the
following instance attributes that define where the baremetal remote-node is located on the network
and how to communicate with that remote-node. Descriptions of these options can be retrieved using
the following pcs command.
# pcs resource describe remote
Resource options for: ocf:pacemaker:remote
server: Server location to connect to. This can be an ip address or hostname.
port: tcp port to connect to.
When defining a baremetal remote-nodes connection resource, it is common and recommended
to name the connection resource the same name as the baremeatal remote-nodes hostname. By
Chapter 3. Configuration Explained
8
default, if no "server" option is provided, the cluster will attempt to contact the remote-node using the
resource name as the hostname.
Example, defining a baremetal remote-node with the hostname "remote1"
# pcs resource create remote1 remote
Example, defining a baremetal remote-node to connect to a specific ip and port.
# pcs resource create remote1 remote server=192.168.122.200 port=8938
3.3. Host and Guest Authentication
Authentication and encryption of the connection between cluster-nodes (pacemaker) to remote-nodes
(pacemaker_remote) is achieved using TLS with PSK encryption/authentication on tcp port 3121.
This means both the cluster-node and remote-node must share the same private key. By default this
key must be placed at "/etc/pacemaker/authkey" on both cluster-nodes and
remote-nodes.
3.4. Pacemaker and pacemaker_remote Options
If you need to change the default port or authkey location for either pacemaker or pacemaker_remote,
there are environment variables you can set that affect both of those daemons. These environment
variables can be enabled by placing them in the /etc/sysconfig/pacemaker file.
#==#==# Pacemaker Remote
# Use a custom directory for finding the authkey.
PCMK_authkey_location=/etc/pacemaker/authkey
#
# Specify a custom port for Pacemaker Remote connections
PCMK_remote_port=3121
Chapter 4.
9
KVM Walk-through
Table of Contents
4.1. Step 1: Setup the Host ......................................................................................................... 9
4.1.1. SElinux and Firewall ................................................................................................... 9
4.1.2. Install Cluster Software ............................................................................................... 9
4.1.3. Setup Corosync ....................................................................................................... 10
4.1.4. Verify Cluster Software ............................................................................................. 10
4.1.5. Install Virtualization Software .................................................................................... 11
4.2. Step2: Create the KVM guest .............................................................................................. 11
4.2.1. Setup Guest Network ............................................................................................... 11
4.2.2. Setup Pacemaker Remote ........................................................................................ 12
4.2.3. Verify Host Connection to Guest ............................................................................... 12
4.3. Step3: Integrate KVM guest into Cluster. .............................................................................. 13
4.3.1. Start the Cluster ....................................................................................................... 13
4.3.2. Integrate KVM Guest as remote-node ....................................................................... 14
4.3.3. Starting Resources on KVM Guest ............................................................................ 14
4.3.4. Testing Remote-node Recovery and Fencing ............................................................. 15
4.3.5. Accessing Cluster Tools from Remote-node .............................................................. 16
What this tutorial is: This tutorial is an in-depth walk-through of how to get pacemaker to
manage a KVM guest instance and integrate that guest into the cluster as a remote-node.
What this tutorial is not: This tutorial is not a realistic deployment scenario. The steps
shown here are meant to get users familiar with the concept of remote-nodes as quickly as possible.
4.1. Step 1: Setup the Host
This tutorial was created using Fedora 18 on the host and guest nodes. Anything that is capable of
running libvirt and pacemaker v1.1.10 or greater will do though. An installation guide for installing
Fedora 18 can be found here, http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/.
Fedora 18 (or similar distro) host preparation steps.
4.1.1. SElinux and Firewall
In order to simply this tutorial we will disable the selinux and the firewall on the host. WARNING: These
actions will open a significant security threat to machines exposed to the outside world.
# setenforce 0
# sed -i.bak "s/SELINUX=enforcing/SELINUX=permissive/g" /etc/selinux/config
# systemctl disable iptables.service
# systemctl disable ip6tables.service
# rm '/etc/systemd/system/basic.target.wants/iptables.service'
# rm '/etc/systemd/system/basic.target.wants/ip6tables.service'
# systemctl stop iptables.service
# systemctl stop ip6tables.service
4.1.2. Install Cluster Software
# yum install -y pacemaker corosync pcs resource-agents
Chapter 4. KVM Walk-through
10
4.1.3. Setup Corosync
Running the command below will attempt to detect the network address corosync should bind to.
# export corosync_addr=`ip addr | grep "inet " | tail -n 1 | awk '{print $4}' | sed s/255/0/
g`
Display and verify that address is correct
# echo $corosync_addr
In many cases the address will be 192.168.1.0 if you are behind a standard home router.
Now copy over the example corosync.conf. This code will inject your bindaddress and enable the vote
quorum api which is required by pacemaker.
# cp /etc/corosync/corosync.conf.example /etc/corosync/corosync.conf
# sed -i.bak "s/.*\tbindnetaddr:.*/bindnetaddr:\ $corosync_addr/g" /etc/corosync/
corosync.conf
# cat << END >> /etc/corosync/corosync.conf
quorum {
provider: corosync_votequorum
expected_votes: 2
}
END
4.1.4. Verify Cluster Software
Start the cluster
# pcs cluster start
Verify corosync membership
# pcs status corosync
Membership information
Nodeid Votes Name
1795270848 1 example-host (local)
Verify pacemaker status. At first the pcs cluster status output will look like this.
# pcs status
Last updated: Thu Mar 14 12:26:00 2013
Last change: Thu Mar 14 12:25:55 2013 via crmd on example-host
Stack: corosync
Current DC:
Version: 1.1.10
After about a minute you should see your host as a single node in the cluster.
# pcs status
Install Virtualization Software
11
Stack: corosync
Current DC: example-host (1795270848) - partition WITHOUT quorum
Version: 1.1.8-9b13ea1
Online: [ example-host ]
Go ahead and stop the cluster for now after verifying everything is in order.
# pcs cluster stop
4.1.5. Install Virtualization Software
# yum install -y kvm libvirt qemu-system qemu-kvm bridge-utils virt-manager
# systemctl enable libvirtd.service
reboot the host
4.2. Step2: Create the KVM guest
I am not going to outline the installation steps required to create a kvm guest. There are plenty of
tutorials available elsewhere that do that. I recommend using a Fedora 18 or greater distro as your
guest as that is what I am testing this tutorial with.
4.2.1. Setup Guest Network
Run the commands below to set up a static ip address (192.168.122.10) and hostname (guest1).
export remote_hostname=guest1
export remote_ip=192.168.122.10
export remote_gateway=192.168.122.1
yum remove -y NetworkManager
rm -f /etc/hostname
cat << END >> /etc/hostname
$remote_hostname
END
hostname $remote_hostname
cat << END >> /etc/sysconfig/network
HOSTNAME=$remote_hostname
GATEWAY=$remote_gateway
END
sed -i.bak "s/.*BOOTPROTO=.*/BOOTPROTO=none/g" /etc/sysconfig/network-scripts/ifcfg-eth0
cat << END >> /etc/sysconfig/network-scripts/ifcfg-eth0
IPADDR0=$remote_ip
PREFIX0=24
GATEWAY0=$remote_gateway
DNS1=$remote_gateway
END
systemctl restart network
systemctl enable network.service
systemctl enable sshd
systemctl start sshd
12
echo "checking connectivity"
ping www.google.com
To simplify the tutorial well go ahead and disable selinux on the guest. Well also need to poke a hole
through the firewall on port 3121 (the default port for pacemaker_remote) so the host can contact the
guest.
# setenforce 0
# firewall-cmd --add-port 3121/tcp --permanent
If you still encounter connection issues just disable iptables and ipv6tables on the guest like we did on
the host to guarantee youll be able to contact the guest from the host.
At this point you should be able to ssh into the guest from the host.
4.2.2. Setup Pacemaker Remote
On the HOST machine run these commands to generate an authkey and copy it to the /etc/pacemaker
folder on both the host and guest.
# mkdir /etc/pacemaker
# dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1
# scp -r /etc/pacemaker root@192.168.122.10:/etc/
Now on the GUEST install pacemaker-remote package and enable the daemon to run at startup. In
the commands below you will notice the pacemaker and pacemaker_remote packages are being
installed. The pacemaker package is not required. The only reason it is being installed for this tutorial
is because it contains the a Dummy resource agent we will be using later on to test the remote-node.
# yum install -y pacemaker paceamaker-remote resource-agents
# systemctl enable pacemaker_remote.service
Now start pacemaker_remote on the guest and verify the start was successful.
# systemctl start pacemaker_remote.service
# systemctl status pacemaker_remote
pacemaker_remote.service - Pacemaker Remote Service
Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled)
Active: active (running) since Thu 2013-03-14 18:24:04 EDT; 2min 8s ago
Main PID: 1233 (pacemaker_remot)
CGroup: name=systemd:/system/pacemaker_remote.service
1233 /usr/sbin/pacemaker_remoted
Mar 14 18:24:04 guest1 systemd[1]: Starting Pacemaker Remote Service...
Mar 14 18:24:04 guest1 systemd[1]: Started Pacemaker Remote Service.
Mar 14 18:24:04 guest1 pacemaker_remoted[1233]: notice: lrmd_init_remote_tls_server:
Starting a tls listener on port 3121.
4.2.3. Verify Host Connection to Guest
Before moving forward its worth going ahead and verifying the host can contact the guest on
port 3121. Heres a trick you can use. Connect using telnet from the host. The connection will get
destroyed, but how it is destroyed tells you whether it worked or not.
Step3: Integrate KVM guest into Cluster.
13
First add guest1 to the host machines /etc/hosts file if you havent already. This is required unless you
have dns setup in a way where guest1s address can be discovered.
# cat << END >> /etc/hosts
192.168.122.10 guest1
END
If running the telnet command on the host results in this output before disconnecting, the connection
works.
# telnet guest1 3121
Trying 192.168.122.10...
Connected to guest1.
Escape character is '^]'.
Connection closed by foreign host.
If you see this, the connection is not working.
# telnet guest1 3121
Trying 192.168.122.10...
telnet: connect to address 192.168.122.10: No route to host
Once you can successfully connect to the guest from the host, shutdown the guest. Pacemaker will be
managing the virtual machine from this point forward.
4.3. Step3: Integrate KVM guest into Cluster.
Now the fun part, integrating the virtual machine youve just created into the cluster. It is incredibly
simple.
4.3.1. Start the Cluster
On the host, start pacemaker.
# pcs cluster start
Wait for the host to become the DC. The output of pcs status should look similar to this after about a
minute.
Stack: corosync
Version: 1.1.10
Now enable the cluster to work without quorum or stonith. This is required just for the sake of getting
this tutorial to work with a single cluster-node.
# pcs property set stonith-enabled=false
# pcs property set no-quorum-policy=ignore
14
4.3.2. Integrate KVM Guest as remote-node
If you didnt already do this earlier in the verify host to guest connection section, add the KVM guests
ip to the hosts /etc/hosts file so we can connect by hostname. The command below will do that if you
used the same ip address I used earlier.
192.168.122.10 guest1
END
We will use the VirtualDomain resource agent for the management of the virtual machine. This
agent requires the virtual machines xml config to be dumped to a file on disk. To do this pick out the
name of the virtual machine you just created from the output of this list.
# virsh list --all
Id Name State
______________________________________________
- guest1 shut off
In my case I named it guest1. Dump the xml to a file somewhere on the host using the following
command.
# virsh dumpxml guest1 > /root/guest1.xml
Now just register the resource with pacemaker and youre set!
# pcs resource create vm-guest1 VirtualDomain hypervisor="qemu:///system" config="/root/
guest1.xml" meta remote-node=guest1
Once the vm-guest1 resource is started you will see guest1 appear in the pcs status output as a node.
The final pcs status output should look something like this.
Last updated: Fri Mar 15 09:30:30 2013
Last change: Thu Mar 14 17:21:35 2013 via cibadmin on example-host
Stack: corosync
Version: 1.1.10
Online: [ example-host guest1 ]
Full list of resources:
vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host
4.3.3. Starting Resources on KVM Guest
The commands below demonstrate how resources can be executed on both the remote-node and the
cluster-node.
Create a few Dummy resources. Dummy resources are real resource agents used just for testing
purposes. They actually execute on the host they are assigned to just like an apache server or
database would, except their execution just means a file was created. When the resource is stopped,
that the file it created is removed.
Testing Remote-node Recovery and Fencing
15
# pcs resource create FAKE1 ocf:pacemaker:Dummy
Now check your pcs status output. In the resource section you should see something like the
following, where some of the resources got started on the cluster-node, and some started on the
remote-node.
FAKE1 (ocf::pacemaker:Dummy): Started guest1
FAKE3 (ocf::pacemaker:Dummy): Started example-host
The remote-node, guest1, reacts just like any other node in the cluster. For example, pick out a
resource that is running on your cluster-node. For my purposes I am picking FAKE3 from the output
above. We can force FAKE3 to run on guest1 in the exact same way we would any other node.
# pcs constraint FAKE3 prefers guest1
Now looking at the bottom of the pcs status output youll see FAKE3 is on guest1.
4.3.4. Testing Remote-node Recovery and Fencing
Pacemakers policy engine is smart enough to know fencing remote-nodes associated with a virtual
machine means shutting off/rebooting the virtual machine. No special configuration is necessary to
make this happen. If you are interested in testing this functionality out, trying stopping the guests
pacemaker_remote daemon. This would be equivalent of abruptly terminating a cluster-nodes
corosync membership without properly shutting it down.
ssh into the guest and run this command.
# kill -9 `pidof pacemaker_remoted`
After a few seconds or so youll see this in your pcs status output. The guest1 node will be show as
offline as it is being recovered.
Last change: Fri Mar 15 09:54:16 2013 via cibadmin on example-host
Stack: corosync
Version: 1.1.10
16
OFFLINE: [ guest1 ]
FAKE1 (ocf::pacemaker:Dummy): Stopped
Failed actions:
guest1_monitor_30000 (node=example-host, call=3, rc=7, status=complete): not running
Once recovery of the guest is complete, youll see it automatically get re-integrated into the cluster.
The final pcs status output should look something like this.
Last change: Fri Mar 15 09:54:16 2013 via cibadmin on example-host
Stack: corosync
Version: 1.1.10
Online: [ example-host guest1 ]
Failed actions:
guest1_monitor_30000 (node=example-host, call=3, rc=7, status=complete): not running
4.3.5. Accessing Cluster Tools from Remote-node
Besides just allowing the cluster to manage resources on a remote-node, pacemaker_remote has one
other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools
(crm_resource, crm_mon, crm_attribute, crm_master) to work on remote nodes
natively.
Try it, run crm_mon or pcs status on the guest after pacemaker has integrated the remote-node
into the cluster. These tools just work. These means resource agents such as master/slave resources
which need access to tools like crm_master work seamlessly on the remote-nodes.
Chapter 5.
17
Baremetal Walk-through
Table of Contents
5.1. Step 1: Setup ..................................................................................................................... 17
5.1.1. SElinux and Firewall Considerations .......................................................................... 17
5.1.2. Setup Pacemaker Remote on Baremetal remote-node ............................................... 17
5.1.3. Verify cluster-node Connection to baremetal-node ..................................................... 18
5.1.4. Install cluster-node Software ..................................................................................... 19
5.1.5. Setup Corosync on cluster-nodes .............................................................................. 19
5.1.6. Start Pacemaker on cluster-nodes ............................................................................ 19
5.1.7. Integrate Baremetal remote-node into Cluster ............................................................ 20
5.1.8. Starting Resources on baremetal remote-node .......................................................... 21
5.1.9. Fencing baremetal remote-nodes .............................................................................. 21
5.1.10. Accessing Cluster Tools from a Baremetal remote-node ........................................... 21
What this tutorial is: This tutorial is an in-depth walk-through of how to get pacemaker to
integrate a baremetal remote-node into the cluster as a node capable of running cluster resources.
shown here are meant to get users familiar with the concept of remote-nodes as quickly as possible.
5.1. Step 1: Setup
This tutorial requires three machines. Two machines to act as cluster-nodes and a third to act as the
baremetal remote-node.
This tutorial was tested using Fedora 18 on both the cluster-nodes and baremetal remote-node.
Anything that is capable of running pacemaker v1.1.11 or greater will do though. An installation
guide for installing Fedora 18 can be found here, http://docs.fedoraproject.org/en-US/Fedora/18/html/
Installation_Guide/.
5.1.1. SElinux and Firewall Considerations
In order to simply this tutorial we will disable selinux and the firewall on all the nodes. WARNING:
These actions will open a significant security threat to machines exposed to the outside world.
# setenforce 0
5.1.2. Setup Pacemaker Remote on Baremetal remote-node
On the baremetal remote-node machine run these commands to generate an authkey and copy it to
the /etc/pacemaker folder.
Chapter 5. Baremetal Walk-through
18
# mkdir /etc/pacemaker
Make sure to distribute this key to both of the cluster-nodes as well. All the nodes must have the
same /etc/pacemaker/authkey installed for the communication to work correctly.
Now install and start the pacemaker_remote daemon on the baremetal remote-node.
# yum install -y paceamaker-remote resource-agents pcs
# systemctl enable pacemaker_remote.service
# systemctl start pacemaker_remote.service
Verify the start is successful.
# systemctl status pacemaker_remote
pacemaker_remote.service - Pacemaker Remote Service
Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled)
Active: active (running) since Thu 2013-03-14 18:24:04 EDT; 2min 8s ago
Main PID: 1233 (pacemaker_remot)
CGroup: name=systemd:/system/pacemaker_remote.service
1233 /usr/sbin/pacemaker_remoted
Mar 14 18:24:04 remote1 systemd[1]: Starting Pacemaker Remote Service...
Mar 14 18:24:04 remote1 systemd[1]: Started Pacemaker Remote Service.
Mar 14 18:24:04 remote1 pacemaker_remoted[1233]: notice: lrmd_init_remote_tls_server:
Starting a tls listener on port 3121.
5.1.3. Verify cluster-node Connection to baremetal-node
Before moving forward its worth going ahead and verifying the cluster-nodes can contact the
baremetal node on port 3121. Heres a trick you can use. Connect using telnet from each of the
cluster-nodes. The connection will get destroyed, but how it is destroyed tells you whether it worked or
not.
First add the baremetal remote-nodes hostname (were using remote1 in this tutorial) to the cluster-
nodes' /etc/hosts files if you havent already. This is required unless you have dns setup in a way
where remote1s address can be discovered.
Execute the following on each cluster-node, replacing the ip address with the actual ip address of the
baremetal remote-node.
192.168.122.10 remote1
END
If running the telnet command on one of the cluster-nodes results in this output before disconnecting,
the connection works.
# telnet remote1 3121
Trying 192.168.122.10...
Connected to remote1.
Escape character is '^]'.
Connection closed by foreign host.
If you see this, the connection is not working.
# telnet remote1 3121
Install cluster-node Software
19
Trying 192.168.122.10...
telnet: connect to address 192.168.122.10: No route to host
Once you can successfully connect to the baremetal remote-node from the both cluster-nodes, move
on to setting up pacemaker on the cluster-nodes.
5.1.4. Install cluster-node Software
On the two cluster-nodes install the following packages.
# yum install -y pacemaker corosync pcs resource-agents
5.1.5. Setup Corosync on cluster-nodes
On one of the cluster nodes, execute the following.
g`
Display and verify that address is correct
In many cases the address will be 192.168.1.0 if you are behind a standard home router.
corosync.conf
quorum {
expected_votes: 2
two_node: 1
}
END
Make sure to copy the newly created /etc/corosync/corosync.conf file to the second cluster-node
before continuing.
5.1.6. Start Pacemaker on cluster-nodes
Start the cluster stack on both cluster nodes using the following command.
# pcs cluster start
Nodeid Votes Name
1795270848 1 node1 (local)
Chapter 5. Baremetal Walk-through
20
# pcs status
Stack: corosync
Current DC:
Version: 1.1.11
After about a minute you should see your two cluster-nodes come online.
# pcs status
Last change: Thu Mar 14 12:25:55 2013 via crmd on node1
Stack: corosync
Version: 1.1.11
Online: [ node1 node2 ]
For the sake of this tutorial, we are going to disable stonith to avoid having to cover fencing device
configuration.
5.1.7. Integrate Baremetal remote-node into Cluster
Integrating a baremetal remote-node into the cluster is achieved through the creation of a remote-
node connection resource. The remote-node connection resource both establishes the connection to
the remote-node and defines that the remote-node exists. Note that this resource is actually internal
to Pacemakers crmd component. A metadata file for this resource can be found in the /usr/lib/ocf/
resource.d/pacemaker/remote file that describes what options are available, but there is no actual
ocf:pacemaker:remote resource agent script that performs any work.
Define the remote-node connection resource to our baremetal remote-node, remote1, using the
following command.
# pcs resource create remote1 ocf:pacemaker:remote
Thats it. After a moment you should see the remote-node come online.
Last updated: Fri Oct 18 18:47:21 2013
Last change: Fri Oct 18 18:46:14 2013 via cibadmin on node1
Stack: corosync
Version: 1.1.11
3 Nodes configured
1 Resources configured
Online: [ node1 node2 ]
RemoteOnline: [ remote1 ]
Starting Resources on baremetal remote-node
21
remote1 (ocf::pacemaker:remote): Started node1
5.1.8. Starting Resources on baremetal remote-node
"Warning: Never involve a remote-node connection resource in a resource
group, colocation, or order constraint"
Once the baremetal remote-node is integrated into the cluster, starting resources on a baremetal
remote-node is the exact same as the cluster nodes. Refer to the Clusters from Scratch document for
examples on resource creation. http://clusterlabs.org/doc/
5.1.9. Fencing baremetal remote-nodes
The cluster understands how to fence baremetal remote-nodes and can use standard fencing devices
to do so. No special considerations are required. Note however that remote-nodes can never initiate a
fencing action. Only cluster-nodes are capable of actually executing the fencing operation on another
node.
5.1.10. Accessing Cluster Tools from a Baremetal remote-node
Besides allowing the cluster to manage resources on a remote-node, pacemaker_remote has one
other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools
(crm_resource, crm_mon, crm_attribute, crm_master) to work on remote nodes
natively.
Try it, run crm_mon or pcs status on the baremetal node after pacemaker has integrated the
remote-node into the cluster. These tools just work. These means resource agents such as master/
slave resources which need access to tools like crm_master work seamlessly on the remote-nodes.
22
Chapter 6.
23
Linux Container (LXC) Walk-through
Table of Contents
6.1. Step 1: Setup LXC Host ...................................................................................................... 23
6.1.1. SElinux and Firewall Rules ....................................................................................... 23
6.1.2. Install Cluster Software on Host ................................................................................ 24
6.1.3. Configure Corosync .................................................................................................. 24
6.1.4. Verify Cluster ........................................................................................................... 24
6.2. Step 2: Setup LXC Environment .......................................................................................... 25
6.2.1. Install Libvirt LXC software ....................................................................................... 25
6.2.2. Generate Libvirt LXC domains .................................................................................. 25
6.2.3. Generate the Authkey ............................................................................................... 26
6.3. Step 3: Integrate LXC guests into Cluster. ............................................................................ 26
6.3.1. Start Cluster ............................................................................................................. 26
6.3.2. Integrate LXC Guests as remote-nodes ..................................................................... 27
6.3.3. Starting Resources on LXC Guests ........................................................................... 27
6.3.4. Testing LXC Guest Failure ....................................................................................... 28
Warning: Continued development in the VirtualDomain agent, libvirt, and
the lxc_autogen script have rendered this tutorial (in its current form)
obsolete. The high level approach of this tutorial remains accurate, but many of the specifics
related to configuring the lxc environment have changed. This walk-through needs to be updated to
reflect the current tested methodology.
What this tutorial is: This tutorial demonstrates how pacemaker_remote can be used with
Linux containers (managed by libvirt-lxc) to run cluster resources in an isolated environment.
shown here are meant to introduce users to the concept of managing Linux container environments
with Pacemaker.
6.1. Step 1: Setup LXC Host
This tutorial was tested with Fedora 18. Anything that is capable of running libvirt and pacemaker
v1.1.10 or greater will do though. An installation guide for installing Fedora 18 can be found here,
http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/.
6.1.1. SElinux and Firewall Rules
In order to simply this tutorial we will disable the selinux and the firewall on the host. WARNING:
These actions pose a significant security issues to machines exposed to the outside world. Basically,
just dont do this on your production system.
# setenforce 0
Chapter 6. Linux Container (LXC) Walk-through
24
6.1.2. Install Cluster Software on Host
# yum install -y pacemaker pacemaker-remote corosync pcs resource-agents
6.1.3. Configure Corosync
Running the command below will attempt to detect the network address corosync should bind to.
g`
Display and verify the address is correct
In most cases the address will be 192.168.1.0 if you are behind a standard home router.
corosync.conf
quorum {
expected_votes: 2
}
END
6.1.4. Verify Cluster
Start the cluster
# pcs cluster start
Nodeid Votes Name
1795270848 1 example-host (local)
# pcs status
Step 2: Setup LXC Environment
25
Stack: corosync
Current DC:
Version: 1.1.10
After about a minute you should see your host as a single node in the cluster.
# pcs status
Stack: corosync
Version: 1.1.8-9b13ea1
Go ahead and stop the cluster for now after verifying everything is in order.
# pcs cluster stop
6.2. Step 2: Setup LXC Environment
6.2.1. Install Libvirt LXC software
# yum install -y libvirt libvirt-daemon-lxc wget
# systemctl enable libvirtd
At this point, restart the host.
6.2.2. Generate Libvirt LXC domains
Ive attempted to simply this tutorial by creating a script to auto generate the libvirt-lxc xml domain
definitions.
Download the script to whatever directory you want the containers to live in. In this example I am using
the /root/lxc/ directory.
# mkdir /root/lxc/
# cd /root/lxc/
# wget https://raw.github.com/davidvossel/pcmk-lxc-autogen/master/lxc-autogen
# chmod 755 lxc-autogen
Now execute the script.
# ./lxc-autogen
After executing the script you will see a bunch of directories and xml files are generated. Those xml
files are the libvirt-lxc domain definitions, and the directories are used as some special mount points
for each container. If you open up one of the xml files youll be able to see how the cpu, memory, and
26
filesystem resources for the container are defined. You can use the libvirt-lxc drivers documentation
found here, http://libvirt.org/drvlxc.html, as a reference to help understand all the parts of the xml file.
The lxc-autogen script is not complicated and is worth exploring in order to grasp how the environment
is generated.
It is worth noting that this environment is dependent on use of libvirts default network interface. Verify
the commands below look the same as your environment. The default network address 192.168.122.1
should have been generated by automatically when you installed the virtualization software.
# virsh net-list
Name State Autostart Persistent
________________________________________________________
default active yes yes
# virsh net-dumpxml default | grep -e "ip address="
<ip address='192.168.122.1' netmask='255.255.255.0'>
6.2.3. Generate the Authkey
Generate the authkey used to secure connections between the host and the lxc guest
pacemaker_remote instances. This is sort of a funny case because the lxc guests and the host will
share the same key file in the /etc/pacemaker/ directory. If in a different deployment where the lxc
guests do not share the hosts /etc/pacemaker directory, this key will have to be copied into each lxc
guest.
6.3. Step 3: Integrate LXC guests into Cluster.
6.3.1. Start Cluster
On the host, start pacemaker.
# pcs cluster start
Wait for the host to become the DC. The output of pcs status should look similar to this after about a
minute.
Stack: corosync
Version: 1.1.10
Now enable the cluster to work without quorum or stonith. This is required just for the sake of getting
this tutorial to work with a single cluster-node.
# pcs property set no-quorum-policy=ignore
Integrate LXC Guests as remote-nodes
27
6.3.2. Integrate LXC Guests as remote-nodes
If you ran the lxc-autogen script with default parameters, 3 lxc domain definitions were created as .xml
files. If you used the same directory I used for the lxc environment, the config files will be located in /
root/lxc. Replace the config parameters in the following pcs commands if yours should be different.
The pcs commands below each configure a lxc guest as a remote-node in pacemaker. Behind the
scenes each lxc guest is launching an instance of pacemaker_remote allowing pacemaker to integrate
the lxc guests as remote-nodes. The meta-attribute remote-node=<node-name> used in each
command is what tells pacemaker that the lxc guest is both a resource and a remote-node capable
of running resources. In this case, the remote-node attribute also indicates to pacemaker that it can
contact each lxcs pacemaker_remote service by using the remote-node name as the hostname. If you
look in the /etc/hosts/ file you will see entries for each lxc guest. These entries were auto-generated
earlier by the lxc-autogen script.
# pcs resource create container1 VirtualDomain force_stop="true" hypervisor="lxc:///"
config="/root/lxc/lxc1.xml" meta remote-node=lxc1
After creating the container resources you pcs status should look like this.
Last updated: Mon Mar 18 17:15:46 2013
Last change: Mon Mar 18 17:15:26 2013 via cibadmin on guest1
Stack: corosync
Version: 1.1.10
Online: [ example-host lxc1 lxc2 lxc3 ]
container3 (ocf::heartbeat:VirtualDomain): Started example-host
6.3.3. Starting Resources on LXC Guests
Now that the lxc guests are integrated into the cluster, lets generate some Dummy resources to run on
them.
Dummy resources are real resource agents used just for testing purposes. They actually execute on
the node they are assigned to just like an apache server or database would, except their execution just
means a file was created. When the resource is stopped, that the file it created is removed.
After creating the Dummy resources you will see that the resource got distributed among all the nodes.
The pcs status output should look similar to this.
Last updated: Mon Mar 18 17:31:54 2013
28
Last change: Mon Mar 18 17:31:05 2013 via cibadmin on example-host
Stack: corosync
Current DC: example=host (175810752) - partition WITHOUT quorum
Version: 1.1.10
Online: [ example-host lxc1 lxc2 lxc3 ]
FAKE1 (ocf::pacemaker:Dummy): Started lxc1
To witness that Dummy agents are running within the lxc guests browse one of the lxc domains
filesystem folders. Each lxc guest has a custom mount point for the '/var/run/'directory, which is the
location the Dummy resources write their state files to.
# ls lxc1-filesystem/var/run/
Dummy-FAKE4.state Dummy-FAKE.state
If you are curious, take a look at lxc1.xml to see how the filesystem is mounted.
6.3.4. Testing LXC Guest Failure
You will be able to see each pacemaker_remoted process running in each lxc guest from the host
machine.
# ps -A | grep -e pacemaker_remote*
9142 pts/2 00:00:00 pacemaker_remot
In order to see how the cluster reacts to a failed lxc guest. Try killing one of the pacemaker_remote
instances.
# kill -9 9142
After a few moments the lxc guest that was running that instance of pacemaker_remote will be
recovered along with all the resources running within that container.
Chapter 7.
29
Future Features
Table of Contents
7.1. Libvirt Sandbox Support ...................................................................................................... 29
7.2. Bare-metal Support ............................................................................................................. 29
7.3. KVM Migration Support ....................................................................................................... 29
Basic KVM and Linux container integration was the first phase of development for pacemaker_remote
and was completed for Pacemaker v1.1.10. Here are some planned features that expand upon this
initial functionality.
7.1. Libvirt Sandbox Support
Once the libvirt-sandbox project is integrated with pacemaker_remote, we will gain the ability to
preform per-resource linux container isolation with very little performance impact. This functionality will
allow resources living on a single node to be isolated from one another. At that point CPU and memory
limits could be set per-resource dynamically just using the cluster config.
7.2. Bare-metal Support
"This feature has already been introduced into Pacemakers master github
branch and is scheduled for Pacemaker v1.1.11"
The pacemaker_remote daemon already has the ability to run on bare-metal hardware nodes, but the
policy engine logic for integrating bare-metal nodes is not complete. There are some complications
involved with understanding a bare-metal nodes state that virtual nodes dont have. Once this logic is
complete, pacemaker will be able to integrate bare-metal nodes in the same way virtual remote-nodes
currently are. Some special considerations for fencing will need to be addressed.
7.3. KVM Migration Support
Pacemakers policy engine is limited in its ability to perform live migrations of KVM resources when
resource dependencies are involved. This limitation affects how resources living within a KVM remote-
node are handled when a live migration takes place. Currently when a live migration is performed on a
KVM remote-node, all the resources within that remote-node have to be stopped before the migration
takes place and started once again after migration has finished. This policy engine limitation is fully
explained in this bug report, http://bugs.clusterlabs.org/show_bug.cgi?id=5055#c3
30
31
Appendix A. Revision History
Revision 1-0 Tue Mar 19 2013 David Vossel dvossel@redhat.com
Import from Pages.app
Revision 2-0 Tue May 13 2013 David Vossel dvossel@redhat.com
Added Future Features Section
Revision 3-0 Fri Oct 18 2013 David Vossel dvossel@redhat.com
Added Baremetal remote-node feature documentation
32
33
Index
34

Pacemaker 1.1 Pacemaker Remote en US

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pacemaker 1.1 Pacemaker Remote en US

Uploaded by

Copyright:

Available Formats

Pacemaker Remote

Extending High Availablity into Virtual Nodes

You might also like