This post is the third of a series that started here.
From the previous of this series, we now have two working EC2 instances that are EBS based. The first instance is the monitor, usually an m1.small type instance and the second instance is hamysql, a large instance type. So far, we have configured Heartbeat for communication between the nodes. Now, it is time to configure the HA resources in Pacemaker. Here are the requirements for the HA resources:
On Monitor
On hamysql
From the above requirements, the resource we will create will need to have an “affinity” or preference to run on hamysql. This is accomplished by location directives. I chose to put a weight of 1000 to hamysql and 1 for monitor. Also the resource is obviously not doing the same thing on both hosts so I decided to use a resource of type anything which is just a script. Same script name and path on each host but different content. To configure Pacemaker, assuming both nodes are online, just performs these steps:
Place holders for the resources scripts
On each host:
|
1 2 |
root@monitor:~# touch /usr/local/bin/mysql root@monitor:~# chmod u+x /usr/local/bin/mysql |
We will come back in the next posts to these scripts. Then, on one of the host:
|
1 2 3 4 5 6 7 8 9 |
root@monitor:~# crm_attribute -t crm_config -n stonith-enabled -v false root@monitor:~# crm_attribute --attr-name symmetric-cluster --attr-value false root@monitor:~# crm configure crm(live)configure# primitive mysql ocf:heartbeat:anything params binfile="/usr/local/bin/mysql" pidfile="/var/run/heartbeat/mysql.pid" op start interval="0" timeout="300s" crm(live)configure# location loc-1 mysql 1000: hamysql crm(live)configure# location loc-2 mysql 1: monitor crm(live)configure# commit |
and that’s it. We know have a resource which is just a shell script that will preferably run on hamysql but, if hamysql is not available, will be able to run on monitor. That’s the basis we will expand on in the next posts.
