RHCS Stable 3 Tutorial - Multinode VM Cluster: Difference between revisions

From Alteeve Wiki
Jump to navigation Jump to search
No edit summary
Line 10: Line 10:
#. A 5-Node cluster hosting [[KVM]] virtual servers, each VM hosted on a dedicated [[LUN]] from the SAN cluster, using Pacemaker for high availability.
#. A 5-Node cluster hosting [[KVM]] virtual servers, each VM hosted on a dedicated [[LUN]] from the SAN cluster, using Pacemaker for high availability.


= Pacemaker =


notes:
* Create a multicast calculator.
* ais_addr is set in beekhof's scriptlet to use the last interface on the system. Manually choose the BCN interface IP.
* Check the ais_* values with `env | grep ais_`.
* Does pacemaker 1.1 in EL6 support a second ring?
<source lang="bash">
yum install pacemaker
cp /etc/corosync/corosync.conf.example /etc/corosync/corosync.conf
vim /etc/corosync/corosync.conf
</source>
Add/edit the following three lines to the 'interface { }' section:
<source lang="bash">
        interface {
                ringnumber: 0
                # Interface to use for cluster comms (BCN).
                bindnetaddr: 192.168.3.0
                # Multicast IP used for CPG. Must be unique per cluster.
                mcastaddr: 226.94.1.1
                # Multicast TCP port. Must be unique per ring.
                mcastport: 4000
                ttl: 1
        }
</source>
Create the pacemaker service file.
<source lang="bash">
vim /etc/corosync/service.d/pcmk
</source>
<source lang="bash">
service {
        # Load the Pacemaker Cluster Resource Manager
        name: pacemaker
        ver:  1
}
</source>
Copy the two files to the other node.
<source lang="bash">
rsync -av /etc/corosync/service.d/pcmk root@an-node02:/etc/corosync/service.d/
</source>
<source lang="text">
sending incremental file list
pcmk
sent 178 bytes  received 31 bytes  59.71 bytes/sec
total size is 106  speedup is 0.51
</source>
<source lang="bash">
rsync -av /etc/corosync/corosync.conf root@an-node02:/etc/corosync/
</source>
<source lang="text">
sending incremental file list
corosync.conf
sent 526 bytes  received 31 bytes  1114.00 bytes/sec
total size is 445  speedup is 0.80
</source>
= cmirror =


cmirror - DOC-55285 - Jonathan Brassow - visegrips - #lvm
cmirror - DOC-55285 - Jonathan Brassow - visegrips - #lvm


{{footer}}
{{footer}}

Revision as of 05:08, 28 May 2011

 AN!Wiki :: How To :: RHCS Stable 3 Tutorial - Multinode VM Cluster

Warning: This document is very much a work in progress. And and all data here could be wrong, inaccurate and missing important bits of information. In fact, it's little more than a dumping grounds for my notes. You really don't want to take anything below seriously until this warning has been removed.

Overview

This tutorial will walk you through building two distinct clusters:

  1. . A 2-Node cluster using DRBD for real-time replicated storage backing an iSCSI SAN using Pacemaker for high availability.
  2. . A 5-Node cluster hosting KVM virtual servers, each VM hosted on a dedicated LUN from the SAN cluster, using Pacemaker for high availability.

Pacemaker

notes:

  • Create a multicast calculator.
  • ais_addr is set in beekhof's scriptlet to use the last interface on the system. Manually choose the BCN interface IP.
  • Check the ais_* values with `env | grep ais_`.
  • Does pacemaker 1.1 in EL6 support a second ring?
yum install pacemaker
cp /etc/corosync/corosync.conf.example /etc/corosync/corosync.conf
vim /etc/corosync/corosync.conf

Add/edit the following three lines to the 'interface { }' section: 

        interface {
                ringnumber: 0
                # Interface to use for cluster comms (BCN).
                bindnetaddr: 192.168.3.0
                # Multicast IP used for CPG. Must be unique per cluster.
                mcastaddr: 226.94.1.1
                # Multicast TCP port. Must be unique per ring.
                mcastport: 4000
                ttl: 1
        }

Create the pacemaker service file. 

vim /etc/corosync/service.d/pcmk

service {
        # Load the Pacemaker Cluster Resource Manager
        name: pacemaker
        ver:  1
}

Copy the two files to the other node. 

rsync -av /etc/corosync/service.d/pcmk root@an-node02:/etc/corosync/service.d/

sending incremental file list
pcmk

sent 178 bytes  received 31 bytes  59.71 bytes/sec
total size is 106  speedup is 0.51

rsync -av /etc/corosync/corosync.conf root@an-node02:/etc/corosync/

sending incremental file list
corosync.conf

sent 526 bytes  received 31 bytes  1114.00 bytes/sec
total size is 445  speedup is 0.80


cmirror

cmirror - DOC-55285 - Jonathan Brassow - visegrips - #lvm

 

Any questions, feedback, advice, complaints or meanderings are welcome.
Alteeve's Niche! Enterprise Support:
Alteeve Support 		Community Support
© Alteeve's Niche! Inc. 1997-2024   Anvil! "Intelligent Availability®" Platform
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.
Retrieved from ‘https://alteeve.com/w/index.php?title=RHCS_Stable_3_Tutorial_-_Multinode_VM_Cluster&oldid=3461’