hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Documentation Update

Browse Source 
Documentation Update
This commit is contained in:
MassimilianoPinto 2015-09-08 09:45:59 +02:00
parent 50bae69605
commit c145fe5cb9
1 changed files with 96 additions and 219 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

315
Reference/MaxScale-HA-with-Corosync-Pacemaker.md
View File

@ -1,32 +1,4 @@
How to make MaxScale High Available # How to make MaxScale High Available
Corosync/Pacemaker setup
& MaxScale init script
Massimiliano Pinto
Last Updated: 4th August 2014
# Contents
[Contents](#heading=h.myvf4p2ngdc5)
[Overview](#heading=h.92d1rpk8nyx4)
[Clustering Software installation](#heading=h.c1l0xy6aynl7)
[MaxScale init script](#heading=h.cfb6xvv8fu1n)
[Configure MaxScale for HA](#heading=h.qk4cgmtiugm0)
[Use case: failed resource is restarted](#heading=h.3fszf28iz3m5)
[Use case: failed resource migration on a node is started in another one](#heading=h.erqw535ttk7l)
[Add a Virtual IP (VIP) to the cluster](#heading=h.vzslsgvxjyug)
# Overview
The document shows an example of a Pacemaker / Corosync setup with MaxScale based on Linux Centos 6.5, using three virtual servers and unicast heartbeat mode with the following minimum requirements: The document shows an example of a Pacemaker / Corosync setup with MaxScale based on Linux Centos 6.5, using three virtual servers and unicast heartbeat mode with the following minimum requirements:
@ -44,19 +16,19 @@ On each node in the cluster do the following steps:
(1) Add clustering repos to yum (1) Add clustering repos to yum
```
# vi /etc/yum.repos.d/ha-clustering.repo # vi /etc/yum.repos.d/ha-clustering.repo
```
Add the following to the file Add the following to the file
```
[haclustering] [haclustering]
name=HA Clustering name=HA Clustering
baseurl=http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/CentOS_CentOS-6/ baseurl=http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/CentOS_CentOS-6/
enabled=1 enabled=1
gpgcheck=0 gpgcheck=0
```
(2) Install the software (2) Install the software
@ -64,45 +36,37 @@ gpgcheck=0
Package versions used Package versions used
Package** pacemake**r-1.1.10-14.el6_5.3.x86_64 ```
Package pacemaker-1.1.10-14.el6_5.3.x86_64
Package **corosync**-1.4.5-2.4.x86_64 Package corosync-1.4.5-2.4.x86_64
Package crmsh-2.0+git46-1.1.x86_64
Package **crmsh**-2.0+git46-1.1.x86_64 ```
(3) Assign hostname on each node (3) Assign hostname on each node
In this example the three names used for the nodes are: node1,node,node3
```
In this example the three names used for the nodes are: [root@server1 ~]# hostname node1
**node1,node,node3**
# hostname **node1**
... ...
[root@server2 ~]# hostname node2
# hostname nodeN ...
[root@server3 ~]# hostname node3
```
(4) For each node add server names in /etc/hosts (4) For each node add server names in /etc/hosts
```
[root@node3 ~]# vi /etc/hosts [root@node3 ~]# vi /etc/hosts
10.74.14.39 node1 10.74.14.39 node1
10.228.103.72 node2 10.228.103.72 node2
10.35.15.26 node3 current-node 10.35.15.26 node3 current-node
[root@node1 ~]# vi /etc/hosts
10.74.14.39 node1 current-node
10.228.103.72 node2
10.35.15.26 node3
... ...
[root@node1 ~]# vi /etc/hosts
10.74.14.39 node1 current-node
10.228.103.72 node2
10.35.15.26 node3
```
**Please note**: add **current-node** as an alias for the current node in each of the /etc/hosts files. **Please note**: add **current-node** as an alias for the current node in each of the /etc/hosts files.
@ -110,97 +74,70 @@ In this example the three names used for the nodes are:
On one of the nodes, say node2 run the corosync-keygen utility and follow On one of the nodes, say node2 run the corosync-keygen utility and follow
```
[root@node2 ~]# corosync-keygen [root@node2 ~]# corosync-keygen
Corosync Cluster Engine Authentication key generator. Gathering 1024 bits for key from /dev/random. Press keys on your keyboard to generate entropy. Corosync Cluster Engine Authentication key generator. Gathering 1024 bits for key from /dev/random. Press keys on your keyboard to generate entropy.
After completion the key will be found in /etc/corosync/authkey. After completion the key will be found in /etc/corosync/authkey.
```
(6) Prepare the corosync configuration file (6) Prepare the corosync configuration file
Using node2 as an example: Using node2 as an example:
```
[root@node2 ~]# vi /etc/corosync/corosync.conf [root@node2 ~]# vi /etc/corosync/corosync.conf
```
Add the following to the file: Add the following to the file:
```
# Please read the corosync.conf.5 manual page # Please read the corosync.conf.5 manual page
compatibility: whitetank compatibility: whitetank
totem { totem {
version: 2 version: 2
secauth: off secauth: off
interface { interface {
member { member {
memberaddr: node1 memberaddr: node1
} }
member { member {
memberaddr: node2 memberaddr: node2
} }
member { member {
memberaddr: node3 memberaddr: node3
} }
ringnumber: 0 ringnumber: 0
bindnetaddr: current-node bindnetaddr: current-node
mcastport: 5405 mcastport: 5405
ttl: 1 ttl: 1
} }
transport: udpu transport: udpu
} }
logging { logging {
fileline: off fileline: off
to_logfile: yes to_logfile: yes
to_syslog: yes to_syslog: yes
logfile: /var/log/cluster/corosync.log logfile: /var/log/cluster/corosync.log
debug: off debug: off
timestamp: on timestamp: on
logger_subsys { logger_subsys {
subsys: AMF subsys: AMF
debug: off debug: off
} }
} }
# this will start Pacemaker processes # this will start Pacemaker processes
service { service {
ver: 0 ver: 0
name: pacemaker name: pacemaker
} }
```
**Please note **in this example: **Please note **in this example:
@ -212,11 +149,11 @@ name: pacemaker
(7) copy configuration files and auth key on each of the other nodes (7) copy configuration files and auth key on each of the other nodes
```
[root@node2 ~]# scp /etc/corosync/* root@node1:/etc/corosync/ [root@node2 ~]# scp /etc/corosync/* root@node1:/etc/corosync/
[root@node2 ~]# scp /etc/corosync/* root@nodeN:/etc/corosync/
... ...
[root@node2 ~]# scp /etc/corosync/* root@nodeN:/etc/corosync/
```
(8) Corosync needs port *5*405 to be opened: (8) Corosync needs port *5*405 to be opened:
@ -224,39 +161,36 @@ name: pacemaker
For a quick start just disable iptables on each nodes: For a quick start just disable iptables on each nodes:
```
[root@node2 ~]# service iptables stop [root@node2 ~]# service iptables stop
...
…
[root@nodeN ~]# service iptables stop [root@nodeN ~]# service iptables stop
```
(9) Start Corosyn on each node: (9) Start Corosyn on each node:
```
[root@node2 ~] #/etc/init.d/corosync start [root@node2 ~] #/etc/init.d/corosync start
...
…
[root@nodeN ~] #/etc/init.d/corosync start [root@nodeN ~] #/etc/init.d/corosync start
```
and check the corosync daemon is successfully bound to port 5405: and check the corosync daemon is successfully bound to port 5405:
```
[root@node2 ~] #netstat -na | grep 5405 [root@node2 ~] #netstat -na | grep 5405
udp 0 0 10.228.103.72:5405 0.0.0.0:* udp 0 0 10.228.103.72:5405 0.0.0.0:*
```
Check if other nodes are reachable with nc utility and option UDP (-u): Check if other nodes are reachable with nc utility and option UDP (-u):
```
[root@node2 ~] #echo "check ..." | nc -u node1 5405 [root@node2 ~] #echo "check ..." | nc -u node1 5405
[root@node2 ~] #echo "check ..." | nc -u node3 5405 [root@node2 ~] #echo "check ..." | nc -u node3 5405
... ...
[root@node1 ~] #echo "check ..." | nc -u node2 5405 [root@node1 ~] #echo "check ..." | nc -u node2 5405
[root@node1 ~] #echo "check ..." | nc -u node3 5405 [root@node1 ~] #echo "check ..." | nc -u node3 5405
```
…
If the following message is displayed If the following message is displayed
@ -266,27 +200,25 @@ There is an issue with communication between the nodes, this is most likely to b
(10) Check the cluster status, from any node (10) Check the cluster status, from any node
```
[root@node3 ~]# crm status [root@node3 ~]# crm status
```
After a while this will be the output: After a while this will be the output:
```
[root@node3 ~]# crm status [root@node3 ~]# crm status
Last updated: Mon Jun 30 12:47:53 2014 Last updated: Mon Jun 30 12:47:53 2014
Last change: Mon Jun 30 12:47:39 2014 via crmd on node2 Last change: Mon Jun 30 12:47:39 2014 via crmd on node2
Stack: classic openais (with plugin) Stack: classic openais (with plugin)
Current DC: node2 - partition with quorum Current DC: node2 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726 Version: 1.1.10-14.el6_5.3-368c726
3 Nodes configured, 3 expected votes 3 Nodes configured, 3 expected votes
0 Resources configured 0 Resources configured
Online: [ node1 node2 node3 ] Online: [ node1 node2 node3 ]
```
For the basic setup disable the following properties: For the basic setup disable the following properties:
@ -294,11 +226,12 @@ For the basic setup disable the following properties:
- quorum policy - quorum policy
```
[root@node3 ~]# crm configure property 'stonith-enabled'='false' [root@node3 ~]# crm configure property 'stonith-enabled'='false'
[root@node3 ~]# crm configure property 'no-quorum-policy'='ignore' [root@node3 ~]# crm configure property 'no-quorum-policy'='ignore'
```
For more information see: For additional information see:
[http://www.clusterlabs.org/doc/crm_fencing.html](http://www.clusterlabs.org/doc/crm_fencing.html) [http://www.clusterlabs.org/doc/crm_fencing.html](http://www.clusterlabs.org/doc/crm_fencing.html)
@ -308,29 +241,20 @@ The configuration is automatically updated on every node:
Check it from another node, say node1 Check it from another node, say node1
```
[root@node1 ~]# crm configure show [root@node1 ~]# crm configure show
node node1 node node1
node node2 node node2
node node3 node node3
property cib-bootstrap-options: \ property cib-bootstrap-options: \
dc-version=1.1.10-14.el6_5.3-368c726 \ dc-version=1.1.10-14.el6_5.3-368c726 \
cluster-infrastructure="classic openais (with plugin)" \ cluster-infrastructure="classic openais (with plugin)" \
expected-quorum-votes=3 \ expected-quorum-votes=3 \
stonith-enabled=false \ stonith-enabled=false \
no-quorum-policy=ignore \ no-quorum-policy=ignore \
placement-strategy=balanced \ placement-strategy=balanced \
default-resource-stickiness=infinity default-resource-stickiness=infinity
```
The Corosync / Pacemaker cluster is ready to be configured to manage resources. The Corosync / Pacemaker cluster is ready to be configured to manage resources.
@ -338,126 +262,110 @@ The Corosync / Pacemaker cluster is ready to be configured to manage resources.
The MaxScale /etc/init.d./maxscale script allows to start/stop/restart and monitor MaxScale process running in the system. The MaxScale /etc/init.d./maxscale script allows to start/stop/restart and monitor MaxScale process running in the system.
Edit it and modify the **MAXSCALE_BASEDIR** to match the installation directory you choose when you installed MaxScale. ```
**Note**:
It could be necessary to modify other variables, such as
MAXSCALE_BIN, MAXSCALE_HOME, MAXSCALE_PIDFILE and LD_LIBRARY_PATH for a non standard setup.
[root@node1 ~]# /etc/init.d/maxscale [root@node1 ~]# /etc/init.d/maxscale
Usage: /etc/init.d/maxscale {start|stop|status|restart|condrestart|reload} Usage: /etc/init.d/maxscale {start|stop|status|restart|condrestart|reload}
```
- Start - Start
```
[root@node1 ~]# /etc/init.d/maxscale start [root@node1 ~]# /etc/init.d/maxscale start
Starting MaxScale: maxscale (pid 25892) is running... [ OK ] Starting MaxScale: maxscale (pid 25892) is running... [ OK ]
```
- Start again - Start again
```
[root@node1 ~]# /etc/init.d/maxscale start [root@node1 ~]# /etc/init.d/maxscale start
Starting MaxScale: found maxscale (pid 25892) is running.[ OK ] Starting MaxScale: found maxscale (pid 25892) is running.[ OK ]
```
- Stop - Stop
```
[root@node1 ~]# /etc/init.d/maxscale stop [root@node1 ~]# /etc/init.d/maxscale stop
Stopping MaxScale: [ OK ] Stopping MaxScale: [ OK ]
```
- Stop again - Stop again
```
[root@node1 ~]# /etc/init.d/maxscale stop [root@node1 ~]# /etc/init.d/maxscale stop
Stopping MaxScale: [FAILED] Stopping MaxScale: [FAILED]
```
- Status (MaxScale not running) - Status (MaxScale not running)
```
[root@node1 ~]# /etc/init.d/maxscale status [root@node1 ~]# /etc/init.d/maxscale status
MaxScale is stopped [FAILED] MaxScale is stopped [FAILED]
```
The script exit code for "status" is 3 The script exit code for "status" is 3
- Status (MaxScale is running) - Status (MaxScale is running)
```
[root@node1 ~]# /etc/init.d/maxscale status [root@node1 ~]# /etc/init.d/maxscale status
Checking MaxScale status: MaxScale (pid 25953) is running.[ OK ] Checking MaxScale status: MaxScale (pid 25953) is running.[ OK ]
```
The script exit code for "status" is 0 The script exit code for "status" is 0
Note: the MaxScale script is LSB compatible and returns the proper exit code for each action: Note: the MaxScale script is LSB compatible and returns the proper exit code for each action:
For more informations; For additional informations;
[http://www.linux-ha.org/wiki/LSB_Resource_Agents](http://www.linux-ha.org/wiki/LSB_Resource_Agents) [http://www.linux-ha.org/wiki/LSB_Resource_Agents](http://www.linux-ha.org/wiki/LSB_Resource_Agents)
After checking MaxScale is well managed by the /etc/init.d/script is possible to configure the MaxScale HA via Pacemaker. After checking MaxScale is well managed by the /etc/init.d/script is possible to configure the MaxScale HA via Pacemaker.
# Configure MaxScale for HA with Pacemaker # Configure MaxScale for HA with Pacemaker
```
[root@node2 ~]# crm configure primitive MaxScale lsb:maxscale \ [root@node2 ~]# crm configure primitive MaxScale lsb:maxscale \
op monitor interval="10s” timeout=”15s” \ op monitor interval="10s” timeout=”15s” \
op start interval="0” timeout=”15s” \ op start interval="0” timeout=”15s” \
op stop interval="0” timeout=”30s” op stop interval="0” timeout=”30s”
```
MaxScale resource will be started: MaxScale resource will be started:
```
[root@node2 ~]# crm status [root@node2 ~]# crm status
Last updated: Mon Jun 30 13:15:34 2014 Last updated: Mon Jun 30 13:15:34 2014
Last change: Mon Jun 30 13:15:28 2014 via cibadmin on node2 Last change: Mon Jun 30 13:15:28 2014 via cibadmin on node2
Stack: classic openais (with plugin) Stack: classic openais (with plugin)
Current DC: node2 - partition with quorum Current DC: node2 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726 Version: 1.1.10-14.el6_5.3-368c726
3 Nodes configured, 3 expected votes 3 Nodes configured, 3 expected votes
1 Resources configured 1 Resources configured
Online: [ node1 node2 node3 ] Online: [ node1 node2 node3 ]
MaxScale (lsb:maxscale): Started node1 MaxScale (lsb:maxscale): Started node1
```
Basic use cases: #Basic use cases:
# 1. Resource restarted after a failure: ## 1. Resource restarted after a failure:
MaxScale Pid is, $MAXSCALE_PIDFILE=$MAXSCALE_HOME/log/maxscale.pid In the example MaxScale PID is 26114, kill the process immediately:
In the example is 26114, kill the process immediately:
```
[root@node2 ~]# kill -9 26114 [root@node2 ~]# kill -9 26114
...
[root@node2 ~]# crm status [root@node2 ~]# crm status
Last updated: Mon Jun 30 13:16:11 2014 Last updated: Mon Jun 30 13:16:11 2014
Last change: Mon Jun 30 13:15:28 2014 via cibadmin on node2 Last change: Mon Jun 30 13:15:28 2014 via cibadmin on node2
Stack: classic openais (with plugin) Stack: classic openais (with plugin)
Current DC: node2 - partition with quorum Current DC: node2 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726 Version: 1.1.10-14.el6_5.3-368c726
3 Nodes configured, 3 expected votes 3 Nodes configured, 3 expected votes
1 Resources configured 1 Resources configured
Online: [ node1 node2 node3 ] Online: [ node1 node2 node3 ]
@ -465,37 +373,34 @@ Online: [ node1 node2 node3 ]
Failed actions: Failed actions:
MaxScale_monitor_15000 on node1 'not running' (7): call=19, status=complete, last-rc-change='Mon Jun 30 13:16:14 2014', queued=0ms, exec=0ms MaxScale_monitor_15000 on node1 'not running' (7): call=19, status=complete, last-rc-change='Mon Jun 30 13:16:14 2014', queued=0ms, exec=0ms
```
**Note** the **MaxScale_monitor** failed action **Note** the **MaxScale_monitor** failed action
After a few seconds it will be started again: After a few seconds it will be started again:
```
[root@node2 ~]# crm status [root@node2 ~]# crm status
Last updated: Mon Jun 30 13:21:12 2014 Last updated: Mon Jun 30 13:21:12 2014
Last change: Mon Jun 30 13:15:28 2014 via cibadmin on node1 Last change: Mon Jun 30 13:15:28 2014 via cibadmin on node1
Stack: classic openais (with plugin) Stack: classic openais (with plugin)
Current DC: node2 - partition with quorum Current DC: node2 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726 Version: 1.1.10-14.el6_5.3-368c726
3 Nodes configured, 3 expected votes 3 Nodes configured, 3 expected votes
1 Resources configured 1 Resources configured
Online: [ node1 node2 node3 ] Online: [ node1 node2 node3 ]
MaxScale (lsb:maxscale): Started node1 MaxScale (lsb:maxscale): Started node1
```
# 2. The resource cannot be migrated to node1 for a failure: ## 2. The resource cannot be migrated to node1 for a failure:
First, migrate the the resource to another node, say node3 First, migrate the the resource to another node, say node3
```
[root@node1 ~]# crm resource migrate MaxScale node3 [root@node1 ~]# crm resource migrate MaxScale node3
... ...
Online: [ node1 node2 node3 ] Online: [ node1 node2 node3 ]
@ -503,23 +408,19 @@ Online: [ node1 node2 node3 ]
Failed actions: Failed actions:
MaxScale_start_0 on node1 'not running' (7): call=76, status=complete, last-rc-change='Mon Jun 30 13:31:17 2014', queued=2015ms, exec=0ms MaxScale_start_0 on node1 'not running' (7): call=76, status=complete, last-rc-change='Mon Jun 30 13:31:17 2014', queued=2015ms, exec=0ms
```
Note the **MaxScale_start** failed action on node1, and after a few seconds Note the **MaxScale_start** failed action on node1, and after a few seconds
```
[root@node3 ~]# crm status [root@node3 ~]# crm status
Last updated: Mon Jun 30 13:35:00 2014 Last updated: Mon Jun 30 13:35:00 2014
Last change: Mon Jun 30 13:31:13 2014 via crm_resource on node3 Last change: Mon Jun 30 13:31:13 2014 via crm_resource on node3
Stack: classic openais (with plugin) Stack: classic openais (with plugin)
Current DC: node2 - partition with quorum Current DC: node2 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726 Version: 1.1.10-14.el6_5.3-368c726
3 Nodes configured, 3 expected votes 3 Nodes configured, 3 expected votes
1 Resources configured 1 Resources configured
Online: [ node1 node2 node3 ] Online: [ node1 node2 node3 ]
@ -529,6 +430,7 @@ Online: [ node1 node2 node3 ]
Failed actions: Failed actions:
MaxScale_start_0 on node1 'not running' (7): call=76, status=complete, last-rc-change='Mon Jun 30 13:31:17 2014', queued=2015ms, exec=0ms MaxScale_start_0 on node1 'not running' (7): call=76, status=complete, last-rc-change='Mon Jun 30 13:31:17 2014', queued=2015ms, exec=0ms
```
Successfully, MaxScale has been started on a new node: node2. Successfully, MaxScale has been started on a new node: node2.
@ -536,35 +438,30 @@ Successfully, MaxScale has been started on a new node: node2.
With "crm resource cleanup MaxScale" is possible to cleanup the messages: With "crm resource cleanup MaxScale" is possible to cleanup the messages:
```
[root@node1 ~]# crm resource cleanup MaxScale [root@node1 ~]# crm resource cleanup MaxScale
Cleaning up MaxScale on node1 Cleaning up MaxScale on node1
Cleaning up MaxScale on node2 Cleaning up MaxScale on node2
Cleaning up MaxScale on node3 Cleaning up MaxScale on node3
```
The cleaned status is visible from other nodes as well: The cleaned status is visible from other nodes as well:
```
[root@node2 ~]# crm status [root@node2 ~]# crm status
Last updated: Mon Jun 30 13:38:18 2014 Last updated: Mon Jun 30 13:38:18 2014
Last change: Mon Jun 30 13:38:17 2014 via crmd on node3 Last change: Mon Jun 30 13:38:17 2014 via crmd on node3
Stack: classic openais (with plugin) Stack: classic openais (with plugin)
Current DC: node2 - partition with quorum Current DC: node2 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726 Version: 1.1.10-14.el6_5.3-368c726
3 Nodes configured, 3 expected votes 3 Nodes configured, 3 expected votes
1 Resources configured 1 Resources configured
Online: [ node1 node2 node3 ] Online: [ node1 node2 node3 ]
MaxScale (lsb:maxscale): Started node2 MaxScale (lsb:maxscale): Started node2
```
# Add a Virtual IP (VIP) to the cluster # Add a Virtual IP (VIP) to the cluster
@ -576,74 +473,53 @@ Setup is very easy:
assuming an addition IP address is available and can be added to one of the nodes, this i the new configuration to add: assuming an addition IP address is available and can be added to one of the nodes, this i the new configuration to add:
```
[root@node2 ~]# crm configure primitive maxscale_vip ocf:heartbeat:IPaddr2 params ip=192.168.122.125 op monitor interval=10s [root@node2 ~]# crm configure primitive maxscale_vip ocf:heartbeat:IPaddr2 params ip=192.168.122.125 op monitor interval=10s
```
MaxScale process and the VIP must be run in the same node, so it’s mandatory to add to the configuration the group ‘maxscale_service’. MaxScale process and the VIP must be run in the same node, so it’s mandatory to add to the configuration the group ‘maxscale_service’.
```
[root@node2 ~]# crm configure group maxscale_service maxscale_vip MaxScale [root@node2 ~]# crm configure group maxscale_service maxscale_vip MaxScale
```
The final configuration is, from another node: The final configuration is, from another node:
```
[root@node3 ~]# crm configure show [root@node3 ~]# crm configure show
node node1 node node1
node node2 node node2
node node3 node node3
primitive MaxScale lsb:maxscale \ primitive MaxScale lsb:maxscale \
op monitor interval=15s timeout=10s \ op monitor interval=15s timeout=10s \
op start interval=0 timeout=15s \ op start interval=0 timeout=15s \
op stop interval=0 timeout=30s op stop interval=0 timeout=30s
primitive maxscale_vip IPaddr2 \ primitive maxscale_vip IPaddr2 \
params ip=192.168.122.125 \ params ip=192.168.122.125 \
op monitor interval=10s op monitor interval=10s
group maxscale_service maxscale_vip MaxScale \ group maxscale_service maxscale_vip MaxScale \
meta target-role=Started meta target-role=Started
property cib-bootstrap-options: \ property cib-bootstrap-options: \
dc-version=1.1.10-14.el6_5.3-368c726 \ dc-version=1.1.10-14.el6_5.3-368c726 \
cluster-infrastructure="classic openais (with plugin)" \ cluster-infrastructure="classic openais (with plugin)" \
expected-quorum-votes=3 \ expected-quorum-votes=3 \
stonith-enabled=false \ stonith-enabled=false \
no-quorum-policy=ignore \ no-quorum-policy=ignore \
placement-strategy=balanced \ placement-strategy=balanced \
last-lrm-refresh=1404125486 last-lrm-refresh=1404125486
```
Check the resource status: Check the resource status:
```
[root@node1 ~]# crm status [root@node1 ~]# crm status
Last updated: Mon Jun 30 13:51:29 2014 Last updated: Mon Jun 30 13:51:29 2014
Last change: Mon Jun 30 13:51:27 2014 via crmd on node1 Last change: Mon Jun 30 13:51:27 2014 via crmd on node1
Stack: classic openais (with plugin) Stack: classic openais (with plugin)
Current DC: node2 - partition with quorum Current DC: node2 - partition with quorum
Version: 1.1.10-14.el6_5.3-368c726 Version: 1.1.10-14.el6_5.3-368c726
3 Nodes configured, 3 expected votes 3 Nodes configured, 3 expected votes
2 Resources configured 2 Resources configured
Online: [ node1 node2 node3 ] Online: [ node1 node2 node3 ]
@ -653,6 +529,7 @@ Online: [ node1 node2 node3 ]
maxscale_vip (ocf::heartbeat:IPaddr2): Started node2 maxscale_vip (ocf::heartbeat:IPaddr2): Started node2
MaxScale (lsb:maxscale): Started node2 MaxScale (lsb:maxscale): Started node2
```
With both resources on node2, now MaxScale service will be reachable via the configured VIP address 192.168.122.125 With both resources on node2, now MaxScale service will be reachable via the configured VIP address 192.168.122.125