diff --git a/doc/Clusters_from_Scratch/en-US/Ap-Configuration.txt b/doc/Clusters_from_Scratch/en-US/Ap-Configuration.txt index e84ff209f4..4857ce1ded 100644 --- a/doc/Clusters_from_Scratch/en-US/Ap-Configuration.txt +++ b/doc/Clusters_from_Scratch/en-US/Ap-Configuration.txt @@ -1,192 +1,192 @@ [appendix] = Configuration Recap = == Final Cluster Configuration == ..... # crm configure show node pcmk-1 node pcmk-2 primitive WebData ocf:linbit:drbd \ params drbd_resource="wwwdata" \ op monitor interval="60s" primitive WebFS ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="gfs2" primitive WebSite ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" \ op monitor interval="1min" primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" clusterip_hash="sourceip" \ op monitor interval="30s" primitive ipmi-fencing stonith::fence_ipmilan \ params pcmk_host_list="pcmk-1 pcmk-2" ipaddr=10.0.0.1 login=testuser passwd=abc123 \ op monitor interval="60s" ms WebDataClone WebData \ meta master-max="2" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" clone WebFSClone WebFS clone WebIP ClusterIP \ meta globally-unique="true" clone-max="2" clone-node-max="2" clone WebSiteClone WebSite colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone colocation fs_on_drbd inf: WebFSClone WebDataClone:Master colocation website-with-ip inf: WebSiteClone WebIP order WebFS-after-WebData inf: WebDataClone:promote WebFSClone:start order WebSite-after-WebFS inf: WebFSClone WebSiteClone order apache-after-ip inf: WebIP WebSiteClone property $id="cib-bootstrap-options" \ dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="true" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" ..... == Node List == The list of cluster nodes is automatically populated by the cluster. ..... node pcmk-1 node pcmk-2 ..... == Cluster Options == This is where the cluster automatically stores some information about the cluster * dc-version - the version (including upstream source-code hash) of Pacemaker used on the DC * cluster-infrastructure - the cluster infrastructure being used (heartbeat or openais) * expected-quorum-votes - the maximum number of nodes expected to be part of the cluster and where the admin can set options that control the way the cluster operates * stonith-enabled=true - Make use of STONITH * no-quorum-policy=ignore - Ignore loss of quorum and continue to host resources. ..... property $id="cib-bootstrap-options" \ dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="true" \ no-quorum-policy="ignore" ..... == Resources == === Default Options === Here we configure cluster options that apply to every resource. * resource-stickiness - Specify the aversion to moving resources to other machines ..... rsc_defaults $id="rsc-options" \ resource-stickiness="100" ..... === Fencing === [NOTE] ======= TODO: Add text here ======= ..... primitive ipmi-fencing stonith::fence_ipmilan \ params pcmk_host_list="pcmk-1 pcmk-2" ipaddr=10.0.0.1 login=testuser passwd=abc123 \ op monitor interval="60s" clone Fencing rsa-fencing ..... === Service Address === Users of the services provided by the cluster require an unchanging address with which to access it. Additionally, we cloned the address so it will be active on both nodes. An iptables rule (created as part of the -resource agent) is used to ensure that each request only processed by one +resource agent) is used to ensure that each request only gets processed by one of the two clone instances. The additional meta options tell the cluster that we want two instances of the clone (one "request bucket" for each node) and that if one node fails, then the remaining node should hold both. ..... primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" clusterip_hash="sourceip" \ op monitor interval="30s" clone WebIP ClusterIP meta globally-unique="true" clone-max="2" clone-node-max="2" ..... [NOTE] ======= TODO: The RA should check for globally-unique=true when cloned ======= === DRBD - Shared Storage === Here we define the DRBD service and specify which DRBD resource (from drbd.conf) it should manage. We make it a master/slave resource and, in order to have an active/active setup, allow both instances to be promoted by specifying master-max=2. We also set the notify option so that the cluster will tell DRBD agent when it's peer changes state. ..... primitive WebData ocf:linbit:drbd \ params drbd_resource="wwwdata" \ op monitor interval="60s" ms WebDataClone WebData \ meta master-max="2" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" ..... === Cluster Filesystem === The cluster filesystem ensures that files are read and written correctly. We need to specify the block device (provided by DRBD), where we want it mounted and that we are using GFS2. Again it is a clone because it is intended to be active on both nodes. The additional constraints ensure that it can only be started on nodes with active gfs-control and drbd instances. ..... primitive WebFS ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="gfs2" clone WebFSClone WebFS colocation WebFS-with-gfs-control inf: WebFSClone gfs-clone colocation fs_on_drbd inf: WebFSClone WebDataClone:Master order WebFS-after-WebData inf: WebDataClone:promote WebFSClone:start order start-WebFS-after-gfs-control inf: gfs-clone WebFSClone ..... === Apache === Lastly we have the actual service, Apache. We need only tell the cluster where to find it's main configuration file and restrict it to running on nodes that have the required filesystem mounted and the IP address active. ..... primitive WebSite ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" \ op monitor interval="1min" clone WebSiteClone WebSite colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone colocation website-with-ip inf: WebSiteClone WebIP order apache-after-ip inf: WebIP WebSiteClone order WebSite-after-WebFS inf: WebFSClone WebSiteClone ..... diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Active-Active.txt b/doc/Clusters_from_Scratch/en-US/Ch-Active-Active.txt index 0d0e08aaff..cca9bc1113 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Active-Active.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Active-Active.txt @@ -1,841 +1,841 @@ = Conversion to Active/Active = == Requirements == The primary requirement for an Active/Active cluster is that the data required for your services is available, simultaneously, on both machines. Pacemaker makes no requirement on how this is achieved, you could use a SAN if you had one available, however since DRBD supports multiple Primaries, we can also use that. The only hitch is that we need to use a cluster-aware filesystem. The one we used earlier with DRBD, ext4, is not one of those. Both OCFS2 and GFS2 are supported, however here we will use GFS2 which comes with Fedora 13. We'll also need to use CMAN for Cluster Membership and Quorum instead of our Corosync plugin. == Adding CMAN Support == http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Cluster_Suite_Overview/index.html#s2-clumembership-overview-CSO[CMAN v3] is a Corsync plugin that monitors the names and number of active cluster nodes in order to deliver membership and quorum information to clients (such as the Pacemaker daemons). In a traditional Corosync-Pacemaker cluster, a Pacemaker plugin is loaded to provide membership and quorum information. The motivation for wanting to use CMAN for this instead, is to ensure all elements of the cluster stack are making decisions based on the same membership and quorum data. -footnote:[A failure to do this can lead to what is called internal -split-brain - a situation where different parts of the stack disagree +footnote:[A failure to do this can lead to what is called 'internal +split-brain' - a situation where different parts of the stack disagree about whether some nodes are alive or dead - which quickly leads to -unnecssary down-time and/or data corruption.] +unnecessary down-time and/or data corruption.] In the case of GFS2, the key pieces are the dlm_controld and gfs_controld helpers which act as the glue between the filesystem and the cluster software. Supporting CMAN enables us to use the versions already being shipped by most distributions (since CMAN has been around longer than Pacemaker and is part of the Red Hat cluster stack). [WARNING] ========= Ensure Corosync and Pacemaker are stopped on all nodes before continuing ========= [WARNING] ========= Be sure to disable the Pacemaker plugin before continuing with this section. In most cases, this can be achieved by removing /etc/corosync/service.d/pcmk and stopping Corosync. ========= === Installing the required Software === [source,Bash] ----- # yum install -y cman gfs2-utils gfs2-cluster Loaded plugins: auto-update-debuginfo Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package cman.x86_64 0:3.1.7-1.fc15 will be installed --> Processing Dependency: modcluster >= 0.18.1-1 for package: cman-3.1.7-1.fc15.x86_64 --> Processing Dependency: fence-agents >= 3.1.5-1 for package: cman-3.1.7-1.fc15.x86_64 --> Processing Dependency: openais >= 1.1.4-1 for package: cman-3.1.7-1.fc15.x86_64 --> Processing Dependency: ricci >= 0.18.1-1 for package: cman-3.1.7-1.fc15.x86_64 --> Processing Dependency: libSaCkpt.so.3(OPENAIS_CKPT_B.01.01)(64bit) for package: cman-3.1.7-1.fc15.x86_64 --> Processing Dependency: libSaCkpt.so.3()(64bit) for package: cman-3.1.7-1.fc15.x86_64 ---> Package gfs2-cluster.x86_64 0:3.1.1-2.fc15 will be installed ---> Package gfs2-utils.x86_64 0:3.1.1-2.fc15 will be installed --> Running transaction check ---> Package fence-agents.x86_64 0:3.1.5-1.fc15 will be installed --> Processing Dependency: /usr/bin/virsh for package: fence-agents-3.1.5-1.fc15.x86_64 --> Processing Dependency: net-snmp-utils for package: fence-agents-3.1.5-1.fc15.x86_64 --> Processing Dependency: sg3_utils for package: fence-agents-3.1.5-1.fc15.x86_64 --> Processing Dependency: perl(Net::Telnet) for package: fence-agents-3.1.5-1.fc15.x86_64 --> Processing Dependency: /usr/bin/ipmitool for package: fence-agents-3.1.5-1.fc15.x86_64 --> Processing Dependency: perl-Net-Telnet for package: fence-agents-3.1.5-1.fc15.x86_64 --> Processing Dependency: pexpect for package: fence-agents-3.1.5-1.fc15.x86_64 --> Processing Dependency: pyOpenSSL for package: fence-agents-3.1.5-1.fc15.x86_64 --> Processing Dependency: python-suds for package: fence-agents-3.1.5-1.fc15.x86_64 ---> Package modcluster.x86_64 0:0.18.7-1.fc15 will be installed --> Processing Dependency: oddjob for package: modcluster-0.18.7-1.fc15.x86_64 ---> Package openais.x86_64 0:1.1.4-2.fc15 will be installed ---> Package openaislib.x86_64 0:1.1.4-2.fc15 will be installed ---> Package ricci.x86_64 0:0.18.7-1.fc15 will be installed --> Processing Dependency: parted for package: ricci-0.18.7-1.fc15.x86_64 --> Processing Dependency: nss-tools for package: ricci-0.18.7-1.fc15.x86_64 --> Running transaction check ---> Package ipmitool.x86_64 0:1.8.11-6.fc15 will be installed ---> Package libvirt-client.x86_64 0:0.8.8-7.fc15 will be installed --> Processing Dependency: libnetcf.so.1(NETCF_1.3.0)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: cyrus-sasl-md5 for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: gettext for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: nc for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libnuma.so.1(libnuma_1.1)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libnuma.so.1(libnuma_1.2)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libnetcf.so.1(NETCF_1.2.0)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: gnutls-utils for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libnetcf.so.1(NETCF_1.0.0)(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libyajl.so.1()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libnl.so.1()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libnuma.so.1()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libaugeas.so.0()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 --> Processing Dependency: libnetcf.so.1()(64bit) for package: libvirt-client-0.8.8-7.fc15.x86_64 ---> Package net-snmp-utils.x86_64 1:5.6.1-7.fc15 will be installed ---> Package nss-tools.x86_64 0:3.12.10-6.fc15 will be installed ---> Package oddjob.x86_64 0:0.31-2.fc15 will be installed ---> Package parted.x86_64 0:2.3-10.fc15 will be installed ---> Package perl-Net-Telnet.noarch 0:3.03-12.fc15 will be installed ---> Package pexpect.noarch 0:2.3-6.fc15 will be installed ---> Package pyOpenSSL.x86_64 0:0.10-3.fc15 will be installed ---> Package python-suds.noarch 0:0.3.9-3.fc15 will be installed ---> Package sg3_utils.x86_64 0:1.29-3.fc15 will be installed --> Processing Dependency: sg3_utils-libs = 1.29-3.fc15 for package: sg3_utils-1.29-3.fc15.x86_64 --> Processing Dependency: libsgutils2.so.2()(64bit) for package: sg3_utils-1.29-3.fc15.x86_64 --> Running transaction check ---> Package augeas-libs.x86_64 0:0.9.0-1.fc15 will be installed ---> Package cyrus-sasl-md5.x86_64 0:2.1.23-18.fc15 will be installed ---> Package gettext.x86_64 0:0.18.1.1-7.fc15 will be installed --> Processing Dependency: libgomp.so.1(GOMP_1.0)(64bit) for package: gettext-0.18.1.1-7.fc15.x86_64 --> Processing Dependency: libgettextlib-0.18.1.so()(64bit) for package: gettext-0.18.1.1-7.fc15.x86_64 --> Processing Dependency: libgettextsrc-0.18.1.so()(64bit) for package: gettext-0.18.1.1-7.fc15.x86_64 --> Processing Dependency: libgomp.so.1()(64bit) for package: gettext-0.18.1.1-7.fc15.x86_64 ---> Package gnutls-utils.x86_64 0:2.10.5-1.fc15 will be installed ---> Package libnl.x86_64 0:1.1-14.fc15 will be installed ---> Package nc.x86_64 0:1.100-3.fc15 will be installed --> Processing Dependency: libbsd.so.0(LIBBSD_0.0)(64bit) for package: nc-1.100-3.fc15.x86_64 --> Processing Dependency: libbsd.so.0(LIBBSD_0.2)(64bit) for package: nc-1.100-3.fc15.x86_64 --> Processing Dependency: libbsd.so.0()(64bit) for package: nc-1.100-3.fc15.x86_64 ---> Package netcf-libs.x86_64 0:0.1.9-1.fc15 will be installed ---> Package numactl.x86_64 0:2.0.7-1.fc15 will be installed ---> Package sg3_utils-libs.x86_64 0:1.29-3.fc15 will be installed ---> Package xen-libs.x86_64 0:4.1.1-3.fc15 will be installed --> Processing Dependency: xen-licenses for package: xen-libs-4.1.1-3.fc15.x86_64 ---> Package yajl.x86_64 0:1.0.11-1.fc15 will be installed --> Running transaction check ---> Package gettext-libs.x86_64 0:0.18.1.1-7.fc15 will be installed ---> Package libbsd.x86_64 0:0.2.0-4.fc15 will be installed ---> Package libgomp.x86_64 0:4.6.1-9.fc15 will be installed ---> Package xen-licenses.x86_64 0:4.1.1-3.fc15 will be installed --> Finished Dependency Resolution Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: cman x86_64 3.1.7-1.fc15 updates 366 k gfs2-cluster x86_64 3.1.1-2.fc15 fedora 69 k gfs2-utils x86_64 3.1.1-2.fc15 fedora 222 k Installing for dependencies: augeas-libs x86_64 0.9.0-1.fc15 updates 311 k cyrus-sasl-md5 x86_64 2.1.23-18.fc15 updates 46 k fence-agents x86_64 3.1.5-1.fc15 updates 186 k gettext x86_64 0.18.1.1-7.fc15 fedora 1.0 M gettext-libs x86_64 0.18.1.1-7.fc15 fedora 610 k gnutls-utils x86_64 2.10.5-1.fc15 fedora 101 k ipmitool x86_64 1.8.11-6.fc15 fedora 273 k libbsd x86_64 0.2.0-4.fc15 fedora 37 k libgomp x86_64 4.6.1-9.fc15 updates 95 k libnl x86_64 1.1-14.fc15 fedora 118 k libvirt-client x86_64 0.8.8-7.fc15 updates 2.4 M modcluster x86_64 0.18.7-1.fc15 fedora 187 k nc x86_64 1.100-3.fc15 updates 24 k net-snmp-utils x86_64 1:5.6.1-7.fc15 fedora 180 k netcf-libs x86_64 0.1.9-1.fc15 updates 50 k nss-tools x86_64 3.12.10-6.fc15 updates 723 k numactl x86_64 2.0.7-1.fc15 updates 54 k oddjob x86_64 0.31-2.fc15 fedora 61 k openais x86_64 1.1.4-2.fc15 fedora 190 k openaislib x86_64 1.1.4-2.fc15 fedora 88 k parted x86_64 2.3-10.fc15 updates 618 k perl-Net-Telnet noarch 3.03-12.fc15 fedora 55 k pexpect noarch 2.3-6.fc15 fedora 141 k pyOpenSSL x86_64 0.10-3.fc15 fedora 198 k python-suds noarch 0.3.9-3.fc15 fedora 195 k ricci x86_64 0.18.7-1.fc15 fedora 584 k sg3_utils x86_64 1.29-3.fc15 fedora 465 k sg3_utils-libs x86_64 1.29-3.fc15 fedora 54 k xen-libs x86_64 4.1.1-3.fc15 updates 310 k xen-licenses x86_64 4.1.1-3.fc15 updates 64 k yajl x86_64 1.0.11-1.fc15 fedora 27 k Transaction Summary ============================================================================= Install 34 Package(s) Total download size: 10 M Installed size: 38 M Downloading Packages: (1/34): augeas-libs-0.9.0-1.fc15.x86_64.rpm | 311 kB 00:00 (2/34): cman-3.1.7-1.fc15.x86_64.rpm | 366 kB 00:00 (3/34): cyrus-sasl-md5-2.1.23-18.fc15.x86_64.rpm | 46 kB 00:00 (4/34): fence-agents-3.1.5-1.fc15.x86_64.rpm | 186 kB 00:00 (5/34): gettext-0.18.1.1-7.fc15.x86_64.rpm | 1.0 MB 00:01 (6/34): gettext-libs-0.18.1.1-7.fc15.x86_64.rpm | 610 kB 00:00 (7/34): gfs2-cluster-3.1.1-2.fc15.x86_64.rpm | 69 kB 00:00 (8/34): gfs2-utils-3.1.1-2.fc15.x86_64.rpm | 222 kB 00:00 (9/34): gnutls-utils-2.10.5-1.fc15.x86_64.rpm | 101 kB 00:00 (10/34): ipmitool-1.8.11-6.fc15.x86_64.rpm | 273 kB 00:00 (11/34): libbsd-0.2.0-4.fc15.x86_64.rpm | 37 kB 00:00 (12/34): libgomp-4.6.1-9.fc15.x86_64.rpm | 95 kB 00:00 (13/34): libnl-1.1-14.fc15.x86_64.rpm | 118 kB 00:00 (14/34): libvirt-client-0.8.8-7.fc15.x86_64.rpm | 2.4 MB 00:01 (15/34): modcluster-0.18.7-1.fc15.x86_64.rpm | 187 kB 00:00 (16/34): nc-1.100-3.fc15.x86_64.rpm | 24 kB 00:00 (17/34): net-snmp-utils-5.6.1-7.fc15.x86_64.rpm | 180 kB 00:00 (18/34): netcf-libs-0.1.9-1.fc15.x86_64.rpm | 50 kB 00:00 (19/34): nss-tools-3.12.10-6.fc15.x86_64.rpm | 723 kB 00:00 (20/34): numactl-2.0.7-1.fc15.x86_64.rpm | 54 kB 00:00 (21/34): oddjob-0.31-2.fc15.x86_64.rpm | 61 kB 00:00 (22/34): openais-1.1.4-2.fc15.x86_64.rpm | 190 kB 00:00 (23/34): openaislib-1.1.4-2.fc15.x86_64.rpm | 88 kB 00:00 (24/34): parted-2.3-10.fc15.x86_64.rpm | 618 kB 00:00 (25/34): perl-Net-Telnet-3.03-12.fc15.noarch.rpm | 55 kB 00:00 (26/34): pexpect-2.3-6.fc15.noarch.rpm | 141 kB 00:00 (27/34): pyOpenSSL-0.10-3.fc15.x86_64.rpm | 198 kB 00:00 (28/34): python-suds-0.3.9-3.fc15.noarch.rpm | 195 kB 00:00 (29/34): ricci-0.18.7-1.fc15.x86_64.rpm | 584 kB 00:00 (30/34): sg3_utils-1.29-3.fc15.x86_64.rpm | 465 kB 00:00 (31/34): sg3_utils-libs-1.29-3.fc15.x86_64.rpm | 54 kB 00:00 (32/34): xen-libs-4.1.1-3.fc15.x86_64.rpm | 310 kB 00:00 (33/34): xen-licenses-4.1.1-3.fc15.x86_64.rpm | 64 kB 00:00 (34/34): yajl-1.0.11-1.fc15.x86_64.rpm | 27 kB 00:00 ----------------------------------------------------------------------------- Total 803 kB/s | 10 MB 00:12 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : openais-1.1.4-2.fc15.x86_64 1/34 Installing : openaislib-1.1.4-2.fc15.x86_64 2/34 Installing : libnl-1.1-14.fc15.x86_64 3/34 Installing : augeas-libs-0.9.0-1.fc15.x86_64 4/34 Installing : oddjob-0.31-2.fc15.x86_64 5/34 Installing : modcluster-0.18.7-1.fc15.x86_64 6/34 Installing : netcf-libs-0.1.9-1.fc15.x86_64 7/34 Installing : 1:net-snmp-utils-5.6.1-7.fc15.x86_64 8/34 Installing : sg3_utils-libs-1.29-3.fc15.x86_64 9/34 Installing : sg3_utils-1.29-3.fc15.x86_64 10/34 Installing : libgomp-4.6.1-9.fc15.x86_64 11/34 Installing : gnutls-utils-2.10.5-1.fc15.x86_64 12/34 Installing : pyOpenSSL-0.10-3.fc15.x86_64 13/34 Installing : parted-2.3-10.fc15.x86_64 14/34 Installing : cyrus-sasl-md5-2.1.23-18.fc15.x86_64 15/34 Installing : python-suds-0.3.9-3.fc15.noarch 16/34 Installing : ipmitool-1.8.11-6.fc15.x86_64 17/34 Installing : perl-Net-Telnet-3.03-12.fc15.noarch 18/34 Installing : numactl-2.0.7-1.fc15.x86_64 19/34 Installing : yajl-1.0.11-1.fc15.x86_64 20/34 Installing : gettext-libs-0.18.1.1-7.fc15.x86_64 21/34 Installing : gettext-0.18.1.1-7.fc15.x86_64 22/34 Installing : libbsd-0.2.0-4.fc15.x86_64 23/34 Installing : nc-1.100-3.fc15.x86_64 24/34 Installing : xen-licenses-4.1.1-3.fc15.x86_64 25/34 Installing : xen-libs-4.1.1-3.fc15.x86_64 26/34 Installing : libvirt-client-0.8.8-7.fc15.x86_64 27/34 Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration. Installing : nss-tools-3.12.10-6.fc15.x86_64 28/34 Installing : ricci-0.18.7-1.fc15.x86_64 29/34 Installing : pexpect-2.3-6.fc15.noarch 30/34 Installing : fence-agents-3.1.5-1.fc15.x86_64 31/34 Installing : cman-3.1.7-1.fc15.x86_64 32/34 Installing : gfs2-cluster-3.1.1-2.fc15.x86_64 33/34 Installing : gfs2-utils-3.1.1-2.fc15.x86_64 34/34 Installed: cman.x86_64 0:3.1.7-1.fc15 gfs2-cluster.x86_64 0:3.1.1-2.fc15 gfs2-utils.x86_64 0:3.1.1-2.fc15 Dependency Installed: augeas-libs.x86_64 0:0.9.0-1.fc15 cyrus-sasl-md5.x86_64 0:2.1.23-18.fc15 fence-agents.x86_64 0:3.1.5-1.fc15 gettext.x86_64 0:0.18.1.1-7.fc15 gettext-libs.x86_64 0:0.18.1.1-7.fc15 gnutls-utils.x86_64 0:2.10.5-1.fc15 ipmitool.x86_64 0:1.8.11-6.fc15 libbsd.x86_64 0:0.2.0-4.fc15 libgomp.x86_64 0:4.6.1-9.fc15 libnl.x86_64 0:1.1-14.fc15 libvirt-client.x86_64 0:0.8.8-7.fc15 modcluster.x86_64 0:0.18.7-1.fc15 nc.x86_64 0:1.100-3.fc15 net-snmp-utils.x86_64 1:5.6.1-7.fc15 netcf-libs.x86_64 0:0.1.9-1.fc15 nss-tools.x86_64 0:3.12.10-6.fc15 numactl.x86_64 0:2.0.7-1.fc15 oddjob.x86_64 0:0.31-2.fc15 openais.x86_64 0:1.1.4-2.fc15 openaislib.x86_64 0:1.1.4-2.fc15 parted.x86_64 0:2.3-10.fc15 perl-Net-Telnet.noarch 0:3.03-12.fc15 pexpect.noarch 0:2.3-6.fc15 pyOpenSSL.x86_64 0:0.10-3.fc15 python-suds.noarch 0:0.3.9-3.fc15 ricci.x86_64 0:0.18.7-1.fc15 sg3_utils.x86_64 0:1.29-3.fc15 sg3_utils-libs.x86_64 0:1.29-3.fc15 xen-libs.x86_64 0:4.1.1-3.fc15 xen-licenses.x86_64 0:4.1.1-3.fc15 yajl.x86_64 0:1.0.11-1.fc15 Complete! ----- === Configuring CMAN === The first thing we need to do, is tell CMAN complete starting up even without quorum. We can do this by changing the quorum timeout setting: [source,Bash] ----- # sed -i.sed "s/.*CMAN_QUORUM_TIMEOUT=.*/CMAN_QUORUM_TIMEOUT=0/g" /etc/sysconfig/cman ----- -Next we create a basic configuration file and place is in +Next we create a basic configuration file and place it in /etc/cluster/cluster.conf. The name used for each clusternode should correspond to that node's uname -n, just as Pacemaker expects. The nodeid -can be any positive mumber but nust be unique. +can be any positive mumber but must be unique. .Basic cluster.conf for a two-node cluster [source,XML] ----- ----- === Configuring CMAN Fencing === We configure the fence_pcmk agent (supplied with Pacemaker) to redirect any fencing requests from CMAN components (such as dlm_controld) to Pacemaker. Pacemaker's fencing subsystem lets other parts of the stack know that a node has been successfully fenced, thus avoiding the need for it to be fenced again when other subsystems notice the node is gone. [WARNING] ========= Warning Configuring real fencing devices in CMAN will result in nodes being fenced multiple times as different parts of the stack notice the node is missing or failed. ========= The definition should be placed in the fencedevices section and contain: [source,XML] ----- ----- Each clusternode must be configured to use this device by adding a fence method block that lists the node's name as the port. [source,XML] ----- ----- Putting everything together, we have: .cluster.conf for a two-node cluster with fencing [source,XML] ----- ----- === Bringing the Cluster Online with CMAN === The first thing to do is check that the configuration is valid [source,Bash] ----- # ccs_config_validate Configuration validates ----- Now start CMAN [source,Bash] ----- # service cman start Starting cluster: Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ] Waiting for quorum... [ OK ] Starting fenced... [ OK ] Starting dlm_controld... [ OK ] Starting gfs_controld... [ OK ] Unfencing self... [ OK ] Joining fence domain... [ OK ] # crm_mon -1 ----- Once you have confirmed that the first node is happily online, start the second node. [source,Bash] ----- [root@pcmk-2 ~]# service cman startStarting cluster: Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ] Waiting for quorum... [ OK ] Starting fenced... [ OK ] Starting dlm_controld... [ OK ] Starting gfs_controld... [ OK ] Unfencing self... [ OK ] Joining fence domain... [ OK ] # cman_tool nodes Node Sts Inc Joined Name 1 M 548 2011-09-28 10:52:21 pcmk-1 2 M 548 2011-09-28 10:52:21 pcmk-2 # crm_mon -1 ----- You should now see both nodes online and services started. == Create a GFS2 Filesystem == [[GFS2_prep]] === Preparation === Before we do anything to the existing partition, we need to make sure it -is unmounted. We do this by tell the cluster to stop the WebFS resource. +is unmounted. We do this by telling the cluster to stop the WebFS resource. This will ensure that other resources (in our case, Apache) using WebFS are not only stopped, but stopped in the correct order. [source,Bash] ----- # crm_resource --resource WebFS --set-parameter target-role --meta --parameter-value Stopped # crm_mon ============ Last updated: Thu Sep 3 15:18:06 2009 Stack: openais Current DC: pcmk-1 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 6 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] Master/Slave Set: WebDataClone Masters: [ pcmk-1 ] Slaves: [ pcmk-2 ] ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1 ----- [NOTE] ======= Note that both Apache and WebFS have been stopped. ======= === Create and Populate an GFS2 Partition === Now that the cluster stack and integration pieces are running smoothly, we can create an GFS2 partition. [WARNING] ========= This will erase all previous content stored on the DRBD device. Ensure you have a copy of any important data. ========= We need to specify a number of additional parameters when creating a GFS2 partition. First we must use the -p option to specify that we want to use the the Kernel's DLM. Next we use -j to indicate that it should reserve enough space for two journals (one per node accessing the filesystem). Lastly, we use -t to specify the lock table name. The format for this field is clustername:fsname. For the fsname, we just need to pick something unique and descriptive and since we haven't specified a clustername yet, we will use the default (pcmk). To specify an alternate name for the cluster, locate the service section containing +name: pacemaker+ in corosync.conf and insert the following line anywhere inside the block: ..... clustername: myname ..... Do this on each node in the cluster and be sure to restart them before continuing. [source,Bash] ----- # mkfs.gfs2 -p lock_dlm -j 2 -t pcmk:web /dev/drbd1 This will destroy any data on /dev/drbd1. It appears to contain: data Are you sure you want to proceed? [y/n] y Device: /dev/drbd1 Blocksize: 4096 Device Size 1.00 GB (131072 blocks) Filesystem Size: 1.00 GB (131070 blocks) Journals: 2 Resource Groups: 2 Locking Protocol: "lock_dlm" Lock Table: "pcmk:web" UUID: 6B776F46-177B-BAF8-2C2B-292C0E078613 ----- Then (re)populate the new filesystem with data (web pages). For now we'll create another variation on our home page. [source,Bash] ----- # mount /dev/drbd1 /mnt/# cat <<-END >/mnt/index.html My Test Site - GFS2 END # umount /dev/drbd1 # drbdadm verify wwwdata# ----- == Reconfigure the Cluster for GFS2 == [source,Bash] ----- # crm crm(live) # cib new GFS2 INFO: GFS2 shadow CIB created crm(GFS2) # configure delete WebFS crm(GFS2) # configure primitive WebFS ocf:heartbeat:Filesystem params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="gfs2" ----- Now that we've recreated the resource, we also need to recreate all the constraints that used it. This is because the shell will automatically remove any constraints that referenced WebFS. [source,Bash] ----- crm(GFS2) # configure colocation WebSite-with-WebFS inf: WebSite WebFS crm(GFS2) # configure colocation fs_on_drbd inf: WebFS WebDataClone:Master crm(GFS2) # configure order WebFS-after-WebData inf: WebDataClone:promote WebFS:start crm(GFS2) # configure order WebSite-after-WebFS inf: WebFS WebSite crm(GFS2) # configure show node pcmk-1 node pcmk-2 primitive WebData ocf:linbit:drbd \ params drbd_resource="wwwdata" \ op monitor interval="60s" primitive WebFS ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="gfs2" primitive WebSite ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" \ op monitor interval="1min" primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" \ op monitor interval="30s" ms WebDataClone WebData \ meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" colocation WebSite-with-WebFS inf: WebSite WebFS colocation fs_on_drbd inf: WebFS WebDataClone:Master colocation website-with-ip inf: WebSite ClusterIP order WebFS-after-WebData inf: WebDataClone:promote WebFS:start order WebSite-after-WebFS inf: WebFS WebSite order apache-after-ip inf: ClusterIP WebSite property $id="cib-bootstrap-options" \ dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" ----- Review the configuration before uploading it to the cluster, quitting the shell and watching the cluster's response [source,Bash] ----- crm(GFS2) # cib commit GFS2 INFO: commited 'GFS2' shadow CIB to the cluster crm(GFS2) # quit bye # crm_mon ============ Last updated: Thu Sep 3 20:49:54 2009 Stack: openais Current DC: pcmk-2 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 6 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] WebSite (ocf::heartbeat:apache): Started pcmk-2 Master/Slave Set: WebDataClone Masters: [ pcmk-1 ] Slaves: [ pcmk-2 ] ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2WebFS (ocf::heartbeat:Filesystem): Started pcmk-1 ----- == Reconfigure Pacemaker for Active/Active == Almost everything is in place. Recent versions of DRBD are capable of operating in Primary/Primary mode and the filesystem we're using is cluster aware. All we need to do now is reconfigure the cluster to take advantage of this. This will involve a number of changes, so we'll again use interactive mode. # crm # cib new active There's no point making the services active on both locations if we can't reach them, so lets first clone the IP address. Cloned IPaddr2 resources -use an iptables rule to ensure that each request only processed by one of +use an iptables rule to ensure that each request only gets processed by one of the two clone instances. The additional meta options tell the cluster how many instances of the clone we want (one "request bucket" for each node) and that if all other nodes fail, then the remaining node should hold all of them. Otherwise the requests would be simply discarded. [source,Bash] ----- # configure clone WebIP ClusterIP \ meta globally-unique="true" clone-max="2" clone-node-max="2" ----- Now we must tell the ClusterIP how to decide which requests are processed by which hosts. To do this we must specify the clusterip_hash parameter. Open the ClusterIP resource [source,Bash] ----- # configure edit ClusterIP ----- And add the following to the params line ..... clusterip_hash="sourceip" ..... So that the complete definition looks like: ..... primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" clusterip_hash="sourceip" \ op monitor interval="30s" ..... Here is the full transcript [source,Bash] ----- # crm crm(live) # cib new active INFO: active shadow CIB created crm(active) # configure clone WebIP ClusterIP \ meta globally-unique="true" clone-max="2" clone-node-max="2" crm(active) # configure shownode pcmk-1 node pcmk-2 primitive WebData ocf:linbit:drbd \ params drbd_resource="wwwdata" \ op monitor interval="60s" primitive WebFS ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="gfs2" primitive WebSite ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" \ op monitor interval="1min" primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" clusterip_hash="sourceip" \ op monitor interval="30s" ms WebDataClone WebData \ meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" clone WebIP ClusterIP \ meta globally-unique="true" clone-max="2" clone-node-max="2" colocation WebSite-with-WebFS inf: WebSite WebFS colocation fs_on_drbd inf: WebFS WebDataClone:Master colocation website-with-ip inf: WebSite WebIPorder WebFS-after-WebData inf: WebDataClone:promote WebFS:start order WebSite-after-WebFS inf: WebFS WebSiteorder apache-after-ip inf: WebIP WebSite property $id="cib-bootstrap-options" \ dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" ----- Notice how any constraints that referenced ClusterIP have been updated to use WebIP instead. This is an additional benefit of using the crm shell. Next we need to convert the filesystem and Apache resources into clones. Again, the shell will automatically update any relevant constraints. [source,Bash] ----- crm(active) # configure clone WebFSClone WebFS crm(active) # configure clone WebSiteClone WebSite ----- The last step is to tell the cluster that it is now allowed to promote both instances to be Primary (aka. Master). [source,Bash] ----- crm(active) # configure edit WebDataClone ----- Change master-max to 2 [source,Bash] ----- crm(active) # configure show node pcmk-1 node pcmk-2 primitive WebData ocf:linbit:drbd \ params drbd_resource="wwwdata" \ op monitor interval="60s" primitive WebFS ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="gfs2" primitive WebSite ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" \ op monitor interval="1min" primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" clusterip_hash="sourceip" \ op monitor interval="30s" ms WebDataClone WebData \ meta master-max="2" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" clone WebFSClone WebFSclone WebIP ClusterIP \ meta globally-unique="true" clone-max="2" clone-node-max="2" clone WebSiteClone WebSitecolocation WebSite-with-WebFS inf: WebSiteClone WebFSClone colocation fs_on_drbd inf: WebFSClone WebDataClone:Master colocation website-with-ip inf: WebSiteClone WebIP order WebFS-after-WebData inf: WebDataClone:promote WebFSClone:start order WebSite-after-WebFS inf: WebFSClone WebSiteClone order apache-after-ip inf: WebIP WebSiteClone property $id="cib-bootstrap-options" \ dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" ----- Review the configuration before uploading it to the cluster, quitting the shell and watching the cluster's response [source,Bash] ----- crm(active) # cib commit active INFO: commited 'active' shadow CIB to the cluster crm(active) # quit bye # crm_mon ============ Last updated: Thu Sep 3 21:37:27 2009 Stack: openais Current DC: pcmk-2 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 6 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] Master/Slave Set: WebDataClone Masters: [ pcmk-1 pcmk-2 ] Clone Set: WebIP Started: [ pcmk-1 pcmk-2 ] Clone Set: WebFSClone Started: [ pcmk-1 pcmk-2 ] Clone Set: WebSiteClone Started: [ pcmk-1 pcmk-2 ] ----- === Testing Recovery === [NOTE] ======= TODO: Put one node into standby to demonstrate failover ======= diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Shared-Storage.txt b/doc/Clusters_from_Scratch/en-US/Ch-Shared-Storage.txt index b18fe1025a..d124540c26 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Shared-Storage.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Shared-Storage.txt @@ -1,518 +1,518 @@ = Replicated Storage with DRBD = == Background == Even if you're serving up static websites, having to manually synchronize the contents of that website to all the machines in the cluster is not -ideal. For dynamic websites, such as a wiki, its not even an option. Not +ideal. For dynamic websites, such as a wiki, it's not even an option. Not everyone care afford network-attached storage but somehow the data needs to be kept in sync. Enter DRBD which can be thought of as network based RAID-1. See http://www.drbd.org/ for more details. == Install the DRBD Packages == Since its inclusion in the upstream 2.6.33 kernel, everything needed to use DRBD ships with Fedora 13. All you need to do is install it: [source,Bash] ---- # yum install -y drbd-pacemaker drbd-udev Loaded plugins: presto, refresh-packagekit Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package drbd-pacemaker.x86_64 0:8.3.7-2.fc13 set to be updated --> Processing Dependency: drbd-utils = 8.3.7-2.fc13 for package: drbd-pacemaker-8.3.7-2.fc13.x86_64 --> Running transaction check ---> Package drbd-utils.x86_64 0:8.3.7-2.fc13 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================= Package Arch Version Repository Size ================================================================================= Installing: drbd-pacemaker x86_64 8.3.7-2.fc13 fedora 19 k Installing for dependencies: drbd-utils x86_64 8.3.7-2.fc13 fedora 165 k Transaction Summary ================================================================================= Install 2 Package(s) Upgrade 0 Package(s) Total download size: 184 k Installed size: 427 k Downloading Packages: Setting up and reading Presto delta metadata fedora/prestodelta | 1.7 kB 00:00 Processing delta metadata Package(s) data still to download: 184 k (1/2): drbd-pacemaker-8.3.7-2.fc13.x86_64.rpm | 19 kB 00:01 (2/2): drbd-utils-8.3.7-2.fc13.x86_64.rpm | 165 kB 00:02 --------------------------------------------------------------------------------- Total 45 kB/s | 184 kB 00:04 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : drbd-utils-8.3.7-2.fc13.x86_64 1/2 Installing : drbd-pacemaker-8.3.7-2.fc13.x86_64 2/2 Installed: drbd-pacemaker.x86_64 0:8.3.7-2.fc13 Dependency Installed: drbd-utils.x86_64 0:8.3.7-2.fc13 Complete! ---- == Configure DRBD == Before we configure DRBD, we need to set aside some disk for it to use. === Create A Partition for DRBD === If you have more than 1Gb free, feel free to use it. For this guide however, 1Gb is plenty of space for a single html file and sufficient for later holding the GFS2 metadata. [source,Bash] ---- # lvcreate -n drbd-demo -L 1G VolGroup Logical volume "drbd-demo" created # lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert drbd-demo VolGroup -wi-a- 1.00G lv_root VolGroup -wi-ao 7.30G lv_swap VolGroup -wi-ao 500.00M ---- Repeat this on the second node, be sure to use the same size partition. [source,Bash] ---- # ssh pcmk-2 -- lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv_root VolGroup -wi-ao 7.30G lv_swap VolGroup -wi-ao 500.00M # ssh pcmk-2 -- lvcreate -n drbd-demo -L 1G VolGroup Logical volume "drbd-demo" created # ssh pcmk-2 -- lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert drbd-demo VolGroup -wi-a- 1.00G lv_root VolGroup -wi-ao 7.30G lv_swap VolGroup -wi-ao 500.00M ---- === Write the DRBD Config === -There is no series of commands for build a DRBD configuration, so simply +There is no series of commands for building a DRBD configuration, so simply copy the configuration below to /etc/drbd.conf Detailed information on the directives used in this configuration (and other alternatives) is available from http://www.drbd.org/users-guide/ch-configure.html [WARNING] ========= Be sure to use the names and addresses of your nodes if they differ from the ones used in this guide. ========= .... global { usage-count yes; } common { protocol C; } resource wwwdata { meta-disk internal; device /dev/drbd1; syncer { verify-alg sha1; } net { allow-two-primaries; } on pcmk-1 { disk /dev/mapper/VolGroup-drbd--demo; address 192.168.122.101:7789; } on pcmk-2 { disk /dev/mapper/VolGroup-drbd--demo; address 192.168.122.102:7789; } } .... [NOTE] ======= TODO: Explain the reason for the allow-two-primaries option ======= === Initialize and Load DRBD === With the configuration in place, we can now perform the DRBD initialization [source,Bash] ---- # drbdadm create-md wwwdata md_offset 12578816 al_offset 12546048 bm_offset 12541952 Found some data ==> This might destroy existing data! <== Do you want to proceed? [need to type 'yes' to confirm] yes Writing meta data... initializing activity log NOT initialized bitmap New drbd meta data block successfully created. success ---- Now load the DRBD kernel module and confirm that everything is sane [source,Bash] ---- # modprobe drbd# drbdadm up wwwdata# cat /proc/drbdversion: 8.3.6 (api:88/proto:86-90) GIT-hash: f3606c47cc6fcf6b3f086e425cb34af8b7a81bbf build by root@pcmk-1, 2009-12-08 11:22:57 1: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/DUnknown C r---- ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:12248 ---- Repeat on the second node [source,Bash] ---- # ssh pcmk-2 -- drbdadm --force create-md wwwdata Writing meta data... initializing activity log NOT initialized bitmap New drbd meta data block successfully created. success # ssh pcmk-2 -- modprobe drbd WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. # ssh pcmk-2 -- drbdadm up wwwdata # ssh pcmk-2 -- cat /proc/drbd version: 8.3.6 (api:88/proto:86-90) GIT-hash: f3606c47cc6fcf6b3f086e425cb34af8b7a81bbf build by root@pcmk-1, 2009-12-08 11:22:57 1: cs:Connected ro:Secondary/Secondary ds:Inconsistent/Inconsistent C r---- ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:12248 ---- Now we need to tell DRBD which set of data to use. Since both sides contain garbage, we can run the following on pcmk-1: [source,Bash] ---- # drbdadm -- --overwrite-data-of-peer primary wwwdata # cat /proc/drbd version: 8.3.6 (api:88/proto:86-90) GIT-hash: f3606c47cc6fcf6b3f086e425cb34af8b7a81bbf build by root@pcmk-1, 2009-12-08 11:22:57 1: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r---- ns:2184 nr:0 dw:0 dr:2472 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:10064 [=====>..............] sync'ed: 33.4% (10064/12248)K finish: 0:00:37 speed: 240 (240) K/sec # cat /proc/drbd version: 8.3.6 (api:88/proto:86-90) GIT-hash: f3606c47cc6fcf6b3f086e425cb34af8b7a81bbf build by root@pcmk-1, 2009-12-08 11:22:57 1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---- ns:12248 nr:0 dw:0 dr:12536 al:0 bm:1 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0 ---- pcmk-1 is now in the Primary state which allows it to be written to. -Which means its a good point at which to create a filesystem and populate +Which means it's a good point at which to create a filesystem and populate it with some data to serve up via our WebSite resource. === Populate DRBD with Data === [source,Bash] ---- # mkfs.ext4 /dev/drbd1 mke2fs 1.41.4 (27-Jan-2009) Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) 3072 inodes, 12248 blocks 612 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=12582912 2 block groups 8192 blocks per group, 8192 fragments per group 1536 inodes per group Superblock backups stored on blocks: 8193 Writing inode tables: done Creating journal (1024 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 26 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. ---- Now mount the newly created filesystem so we can create our index file [source,Bash] ---- # mount /dev/drbd1 /mnt/ # cat <<-END >/mnt/index.html My Test Site - drbd END # umount /dev/drbd1 ---- == Configure the Cluster for DRBD == One handy feature of the crm shell is that you can use it in interactive mode to make several changes atomically. First we launch the shell. The prompt will change to indicate you're in interactive mode. [source,Bash] ---- # crm cib crm(live) # ---- -Next we must create a working copy or the current configuration. This is +Next we must create a working copy of the current configuration. This is where all our changes will go. The cluster will not see any of them until -we say its ok. Notice again how the prompt changes, this time to indicate +we say it's ok. Notice again how the prompt changes, this time to indicate that we're no longer looking at the live cluster. [source,Bash] ---- cib crm(live) # cib new drbd INFO: drbd shadow CIB created crm(drbd) # ---- Now we can create our DRBD clone and display the revised configuration. [source,Bash] ---- crm(drbd) # configure primitive WebData ocf:linbit:drbd params drbd_resource=wwwdata \ op monitor interval=60s crm(drbd) # configure ms WebDataClone WebData meta master-max=1 master-node-max=1 \ clone-max=2 clone-node-max=1 notify=truecrm(drbd) # configure shownode pcmk-1 node pcmk-2primitive WebData ocf:linbit:drbd \ params drbd_resource="wwwdata" \ op monitor interval="60s"primitive WebSite ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" \ op monitor interval="1min" primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" \ op monitor interval="30s"ms WebDataClone WebData \ meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" location prefer-pcmk-1 WebSite 50: pcmk-1 colocation website-with-ip inf: WebSite ClusterIP order apache-after-ip inf: ClusterIP WebSite property $id="cib-bootstrap-options" \ dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" ---- Once we're happy with the changes, we can tell the cluster to start using them and use crm_mon to check everything is functioning. [source,Bash] ---- crm(drbd) # cib commit drbdINFO: commited 'drbd' shadow CIB to the cluster crm(drbd) # quitbye # crm_mon ============ Last updated: Tue Sep 1 09:37:13 2009 Stack: openais Current DC: pcmk-1 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 3 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1 WebSite (ocf::heartbeat:apache): Started pcmk-1Master/Slave Set: WebDataClone Masters: [ pcmk-2 ] Slaves: [ pcmk-1 ] ---- [NOTE] ======= Include details on adding a second DRBD resource ======= Now that DRBD is functioning we can configure a Filesystem resource to use it. In addition to the filesystem's definition, we also need to tell the cluster where it can be located (only on the DRBD Primary) and when it is allowed to start (after the Primary was promoted). Once again we'll use the shell's interactive mode [source,Bash] ---- # crm crm(live) # cib new fs INFO: fs shadow CIB created crm(fs) # configure primitive WebFS ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="ext4" crm(fs) # configure colocation fs_on_drbd inf: WebFS WebDataClone:Master crm(fs) # configure order WebFS-after-WebData inf: WebDataClone:promote WebFS:start We also need to tell the cluster that Apache needs to run on the same machine as the filesystem and that it must be active before Apache can start. crm(fs) # configure colocation WebSite-with-WebFS inf: WebSite WebFS crm(fs) # configure order WebSite-after-WebFS inf: WebFS WebSite ---- Time to review the updated configuration: [source,Bash] ---- crm(fs) # crm configure show node pcmk-1 node pcmk-2 primitive WebData ocf:linbit:drbd \ params drbd_resource="wwwdata" \ op monitor interval="60s" primitive WebFS ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="ext4" primitive WebSite ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" \ op monitor interval="1min" primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" \ op monitor interval="30s" ms WebDataClone WebData \ meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" location prefer-pcmk-1 WebSite 50: pcmk-1 colocation WebSite-with-WebFS inf: WebSite WebFS colocation fs_on_drbd inf: WebFS WebDataClone:Master colocation website-with-ip inf: WebSite ClusterIP order WebFS-after-WebData inf: WebDataClone:promote WebFS:start order WebSite-after-WebFS inf: WebFS WebSite order apache-after-ip inf: ClusterIP WebSite property $id="cib-bootstrap-options" \ dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" ---- After reviewing the new configuration, we again upload it and watch the cluster put it into effect. [source,Bash] ---- crm(fs) # cib commit fs INFO: commited 'fs' shadow CIB to the cluster crm(fs) # quit bye # crm_mon ============ Last updated: Tue Sep 1 10:08:44 2009 Stack: openais Current DC: pcmk-1 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 4 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1 WebSite (ocf::heartbeat:apache): Started pcmk-1 Master/Slave Set: WebDataClone Masters: [ pcmk-1 ] Slaves: [ pcmk-2 ] WebFS (ocf::heartbeat:Filesystem): Started pcmk-1 ---- === Testing Migration === We could shut down the active node again, but another way to safely simulate recovery is to put the node into what is called "standby mode". Nodes in this state tell the cluster that they are not allowed to run resources. Any resources found active there will be moved elsewhere. This feature can be particularly useful when updating the resources' packages. Put the local node into standby mode and observe the cluster move all the resources to the other node. Note also that the node's status will change to indicate that it can no longer host resources. [source,Bash] ---- # crm node standby # crm_mon ============ Last updated: Tue Sep 1 10:09:57 2009 Stack: openais Current DC: pcmk-1 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 4 Resources configured. ============ Node pcmk-1: standbyOnline: [ pcmk-2 ] ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2 WebSite (ocf::heartbeat:apache): Started pcmk-2 Master/Slave Set: WebDataClone Masters: [ pcmk-2 ] Stopped: [ WebData:1 ] WebFS (ocf::heartbeat:Filesystem): Started pcmk-2 ---- Once we've done everything we needed to on pcmk-1 (in this case nothing, we just wanted to see the resources move), we can allow the node to be a full cluster member again. [source,Bash] ---- # crm node online # crm_mon ============ Last updated: Tue Sep 1 10:13:25 2009 Stack: openais Current DC: pcmk-1 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 4 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2 WebSite (ocf::heartbeat:apache): Started pcmk-2 Master/Slave Set: WebDataClone Masters: [ pcmk-2 ] Slaves: [ pcmk-1 ] WebFS (ocf::heartbeat:Filesystem): Started pcmk-2 ---- Notice that our resource stickiness settings prevent the services from migrating back to pcmk-1. diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Stonith.txt b/doc/Clusters_from_Scratch/en-US/Ch-Stonith.txt index 0f0b7e0e5d..3afacd20d7 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Stonith.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Stonith.txt @@ -1,223 +1,223 @@ = Configure STONITH = == What Is STONITH == STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and it protects your data from being corrupted by rogue nodes or concurrent access. Just because a node is unresponsive, this doesn't mean it isn't accessing your data. The only way to be 100% sure that your data is safe, is to use STONITH so we can be certain that the node is truly offline, before allowing the data to be accessed from another node. STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere. == What STONITH Device Should You Use == It is crucial that the STONITH device can allow the cluster to differentiate between a node failure and a network one. The biggest mistake people make in choosing a STONITH device is to use remote power switch (such as many on-board IMPI controllers) that shares power with the node it controls. In such cases, the cluster cannot be sure if the node is really offline, or active and suffering from a network fault. Likewise, any device that relies on the machine being active (such as SSH-based "devices" used during testing) are inappropriate. == Configuring STONITH == . Find the correct driver: +stonith_admin --list-installed+ . Since every device is different, the parameters needed to configure it will vary. To find out the parameters associated with the device, run: +stonith_admin --metadata --agent type+ The output should be XML formatted text containing additional parameter descriptions. We will endevor to make the output more friendly in a later version. . Enter the shell crm Create an editable copy of the existing configuration cib new stonith Create a fencing resource containing a primitive resource with a class of stonith, a type of type and a parameter for each of the values returned in step 2: +configure primitive ...+ . If the device does not know how to fence nodes based on their uname, you may also need to set the special +pcmk_host_map+ parameter. See +man stonithd+ for details. . If the device does not support the list command, you may also need to set the special +pcmk_host_list+ and/or +pcmk_host_check+ parameters. See +man stonithd+ for details. . If the device does not expect the victim to be specified with the port parameter, you may also need to set the special +pcmk_host_argument+ parameter. See +man stonithd+ for details. . Upload it into the CIB from the shell: +cib commit stonith+ . Once the stonith resource is running, you can test it by executing: +stonith_admin --reboot nodename+. Although you might want to stop the cluster on that machine first. == Example == Assuming we have an chassis containing four nodes and an IPMI device active on 10.0.0.1, then we would chose the fence_ipmilan driver in step 2 and obtain the following list of parameters .Obtaining a list of STONITH Parameters [source,Bash] ---- # stonith_admin --metadata -a fence_ipmilan ---- [source,XML] ---- fence_ipmilan is an I/O Fencing agent which can be used with machines controlled by IPMI. This agent calls support software using ipmitool (http://ipmitool.sf.net/). To use fence_ipmilan with HP iLO 3 you have to enable lanplus option (lanplus / -P) and increase wait after operation to 4 seconds (power_wait=4 / -T 4) IPMI Lan Auth type (md5, password, or none) IPMI Lan IP to talk to Password (if required) to control power on IPMI device Script to retrieve password (if required) Use Lanplus Username/Login (if required) to control power on IPMI device Operation to perform. Valid operations: on, off, reboot, status, list, diag, monitor or metadata Timeout (sec) for IPMI operation Ciphersuite to use (same as ipmitool -C parameter) Method to fence (onoff or cycle) Wait X seconds after on/off operation Wait X seconds before fencing is started Verbose mode ---- from which we would create a STONITH resource fragment that might look like this .Sample STONITH Resource [source,Bash] ---- # crm crm(live)# cib new stonith INFO: stonith shadow CIB created crm(stonith)# configure primitive impi-fencing stonith::fence_ipmilan \ params pcmk_host_list="pcmk-1 pcmk-2" ipaddr=10.0.0.1 login=testuser passwd=abc123 \ op monitor interval="60s" ---- And finally, since we disabled it earlier, we need to re-enable STONITH. -At this point we should have the following configuration.. +At this point we should have the following configuration. [source,Bash] ---- crm(stonith)# configure property stonith-enabled="true"crm(stonith)# configure shownode pcmk-1 node pcmk-2 primitive WebData ocf:linbit:drbd \ params drbd_resource="wwwdata" \ op monitor interval="60s" primitive WebFS ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/wwwdata" directory="/var/www/html" fstype="gfs2" primitive WebSite ocf:heartbeat:apache \ params configfile="/etc/httpd/conf/httpd.conf" \ op monitor interval="1min" primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="192.168.122.101" cidr_netmask="32" clusterip_hash="sourceip" \ op monitor interval="30s"primitive ipmi-fencing stonith::fence_ipmilan \ params pcmk_host_list="pcmk-1 pcmk-2" ipaddr=10.0.0.1 login=testuser passwd=abc123 \ op monitor interval="60s"ms WebDataClone WebData \ meta master-max="2" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" clone WebFSClone WebFS clone WebIP ClusterIP \ meta globally-unique="true" clone-max="2" clone-node-max="2" clone WebSiteClone WebSite colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone colocation fs_on_drbd inf: WebFSClone WebDataClone:Master colocation website-with-ip inf: WebSiteClone WebIP order WebFS-after-WebData inf: WebDataClone:promote WebFSClone:start order WebSite-after-WebFS inf: WebFSClone WebSiteClone order apache-after-ip inf: WebIP WebSiteClone property $id="cib-bootstrap-options" \ dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="true" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" crm(stonith)# cib commit stonithINFO: commited 'stonith' shadow CIB to the cluster crm(stonith)# quit bye ---- diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Tools.txt b/doc/Clusters_from_Scratch/en-US/Ch-Tools.txt index 5116d5933e..7d3ff60956 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Tools.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Tools.txt @@ -1,56 +1,56 @@ = Pacemaker Tools = == Using Pacemaker Tools == In the dark past, configuring Pacemaker required the administrator to read and write XML. In true UNIX style, there were also a number of different commands that specialized in different aspects of querying and updating the cluster. Since Pacemaker 1.0, this has all changed and we have an integrated, scriptable, cluster shell that hides all the messy XML scaffolding. It even allows you to queue up several changes at once and commit them atomically. Take some time to familiarize yourself with what it can do. pass:[# crm --help] ------------------ sys::[crm --help] ------------------ The primary tool for monitoring the status of the cluster is crm_mon (also available as crm status). It can be run in a variety of modes and has a number of output options. To find out about any of the tools that come with Pacemaker, simply invoke them with the --help option or consult the included man pages. Both sets of output are created from the tool, and so will always be in sync with each other and the tool itself. -Additionally, the Pacemaker version and supported cluster stack(s) is +Additionally, the Pacemaker version and supported cluster stack(s) are available via the --feature option to pacemakerd. pass:[# pacemakerd --features] ------------------ sys::[pacemakerd --features] ------------------ pass:[# pacemakerd --help] ------------------ sys::[pacemakerd --help] ------------------ pass:[# crm_mon --help] ------------------ sys::[crm_mon --help] ------------------ [NOTE] ====== If the SNMP and/or email options are not listed, then Pacemaker was not built to support them. This may be by the choice of your distribution or the required libraries may not have been available. Please contact whoever supplied you with the packages for more details. ====== diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Verification.txt b/doc/Clusters_from_Scratch/en-US/Ch-Verification.txt index 098f8afb51..6982707534 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Verification.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Verification.txt @@ -1,125 +1,125 @@ = Verify Cluster Installation = == Verify Corosync Installation == Start Corosync on the first node [source,Bash] ---- # /etc/init.d/corosync start Starting Corosync Cluster Engine (corosync): [ OK ] ---- Check the cluster started correctly and that an initial membership was able to form [source,Bash] ---- # grep -e "corosync.*network interface" -e "Corosync Cluster Engine" -e "Successfully read main configuration file" /var/log/messages Aug 27 09:05:34 pcmk-1 corosync[1540]: [MAIN ] Corosync Cluster Engine ('1.1.0'): started and ready to provide service. Aug 27 09:05:34 pcmk-1 corosync[1540]: [MAIN ] Successfully read main configuration file '/etc/corosync/corosync.conf'. # grep TOTEM /var/log/messages Aug 27 09:05:34 pcmk-1 corosync[1540]: [TOTEM ] Initializing transport (UDP/IP). Aug 27 09:05:34 pcmk-1 corosync[1540]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0). Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] The network interface [192.168.122.101] is now up. Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed. ---- -With one node functional, its now safe to start Corosync on the second +With one node functional, it's now safe to start Corosync on the second node as well. [source,Bash] ---- # ssh pcmk-2 -- /etc/init.d/corosync start Starting Corosync Cluster Engine (corosync): [ OK ] # ---- Check the cluster formed correctly [source,Bash] ---- # grep TOTEM /var/log/messages Aug 27 09:05:34 pcmk-1 corosync[1540]: [TOTEM ] Initializing transport (UDP/IP). Aug 27 09:05:34 pcmk-1 corosync[1540]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0). Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] The network interface [192.168.122.101] is now up. Aug 27 09:05:35 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed. Aug 27 09:12:11 pcmk-1 corosync[1540]: [TOTEM ] A processor joined or left the membership and a new membership was formed. ---- == Verify Pacemaker Installation == Now that we have confirmed that Corosync is functional we can check the rest of the stack. [source,Bash] ---- # grep pcmk_startup /var/log/messages Aug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] info: pcmk_startup: CRM: InitializedAug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] Logging: Initialized pcmk_startup Aug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] info: pcmk_startup: Maximum core file size is: 18446744073709551615 Aug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] info: pcmk_startup: Service: 9Aug 27 09:05:35 pcmk-1 corosync[1540]: [pcmk ] info: pcmk_startup: Local hostname: pcmk-1 ---- Now try starting Pacemaker and check the necessary processes have been started [source,Bash] ---- # /etc/init.d/pacemaker start Starting Pacemaker Cluster Manager: [ OK ] # grep -e pacemakerd.*get_config_opt -e pacemakerd.*start_child -e "Starting Pacemaker" /var/log/messages Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'pacemaker' for option: name Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found '1' for option: ver Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Defaulting to 'no' for option: use_logd Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Defaulting to 'no' for option: use_mgmtd Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'on' for option: debug Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'yes' for option: to_logfile Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found '/var/log/corosync.log' for option: logfile Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'yes' for option: to_syslog Feb 8 13:31:24 pcmk-1 pacemakerd: [13155]: info: get_config_opt: Found 'daemon' for option: syslog_facility Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: main: Starting Pacemaker 1.1.5 (Build: 31f088949239+): docbook-manpages publican ncurses trace-logging cman cs-quorum heartbeat corosync snmp libesmtp Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14022 for process stonith-ng Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14023 for process cib Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14024 for process lrmd Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14025 for process attrd Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14026 for process pengine Feb 8 16:50:38 pcmk-1 pacemakerd: [13990]: info: start_child: Forked child 14027 for process crmd # ps axf PID TTY STAT TIME COMMAND 2 ? S< 0:00 [kthreadd] 3 ? S< 0:00 \_ [migration/0] ... lots of processes ... 13990 ? S 0:01 pacemakerd 14022 ? Sa 0:00 \_ /usr/lib64/heartbeat/stonithd 14023 ? Sa 0:00 \_ /usr/lib64/heartbeat/cib 14024 ? Sa 0:00 \_ /usr/lib64/heartbeat/lrmd 14025 ? Sa 0:00 \_ /usr/lib64/heartbeat/attrd 14026 ? Sa 0:00 \_ /usr/lib64/heartbeat/pengine 14027 ? Sa 0:00 \_ /usr/lib64/heartbeat/crmd ---- Next, check for any ERRORs during startup - there shouldn't be any. [source,Bash] ---- # grep ERROR: /var/log/messages | grep -v unpack_resources # ---- Repeat on the other node and display the cluster's status. [source,Bash] ---- # ssh pcmk-2 -- /etc/init.d/pacemaker start Starting Pacemaker Cluster Manager: [ OK ] # crm_mon ============ Last updated: Thu Aug 27 16:54:55 2009Stack: openais Current DC: pcmk-1 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 0 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] ----