diff --git a/doc/Clusters_from_Scratch/en-US/Ap-Corosync-Conf.txt b/doc/Clusters_from_Scratch/en-US/Ap-Corosync-Conf.txt index 2cb5019317..45215e846c 100644 --- a/doc/Clusters_from_Scratch/en-US/Ap-Corosync-Conf.txt +++ b/doc/Clusters_from_Scratch/en-US/Ap-Corosync-Conf.txt @@ -1,68 +1,85 @@ [appendix] == Sample Corosync Configuration == .Sample Corosync.conf for a two-node cluster ..... -# Please read the Corosync.conf.5 manual page -compatibility: whitetank - +# Please read the corosync.conf.5 manual page totem { - version: 2 - - # How long before declaring a token lost (ms) - token: 5000 - - # How many token retransmits before forming a new configuration - token_retransmits_before_loss_const: 10 - - # How long to wait for join messages in the membership protocol (ms) - join: 1000 - - # How long to wait for consensus to be achieved before starting a new - # round of membership configuration (ms) - consensus: 6000 - - # Turn off the virtual synchrony filter - vsftype: none - - # Number of messages that may be sent by one processor on receipt of the token - max_messages: 20 - - # Stagger sending the node join messages by 1..send_join ms - send_join: 45 - - # Limit generated nodeids to 31-bits (positive signed integers) - clear_node_high_bit: yes - - # Disable encryption - secauth: off - - # How many threads to use for encryption/decryption - threads: 0 - - # Optionally assign a fixed node id (integer) - # nodeid: 1234 - - interface { - ringnumber: 0 - - # The following values need to be set based on your environment - bindnetaddr: 192.168.122.0 - mcastaddr: 226.94.1.1 - mcastport: 4000 - } + version: 2 + + # cypto_cipher and crypto_hash: Used for mutual node authentication. + # If you choose to enable this, then do remember to create a shared + # secret with "corosync-keygen". + crypto_cipher: none + crypto_hash: none + + # interface: define at least one interface to communicate + # over. If you define more than one interface stanza, you must + # also set rrp_mode. + interface { + # Rings must be consecutively numbered, starting at 0. + ringnumber: 0 + # This is normally the *network* address of the + # interface to bind to. This ensures that you can use + # identical instances of this configuration file + # across all your cluster nodes, without having to + # modify this option. +bindnetaddr: 192.168.122.0 + # However, if you have multiple physical network + # interfaces configured for the same subnet, then the + # network address alone is not sufficient to identify + # the interface Corosync should bind to. In that case, + # configure the *host* address of the interface + # instead: + # bindnetaddr: 192.168.1.1 + # When selecting a multicast address, consider RFC + # 2365 (which, among other things, specifies that + # 239.255.x.x addresses are left to the discretion of + # the network administrator). Do not reuse multicast + # addresses across multiple Corosync clusters sharing + # the same network. +mcastaddr: 226.94.1.1 + # Corosync uses the port you specify here for UDP + # messaging, and also the immediately preceding + # port. Thus if you set this to 5405, Corosync sends + # messages over UDP ports 5405 and 5404. +mcastport: 4000 + # Time-to-live for cluster communication packets. The + # number of hops (routers) that this ring will allow + # itself to pass. Note that multicast routing must be + # specifically enabled on most network routers. + ttl: 1 + } } logging { - debug: off - fileline: off - to_syslog: yes - to_stderr: off - syslog_facility: daemon - timestamp: on + # Log the source file and line where messages are being + # generated. When in doubt, leave off. Potentially useful for + # debugging. + fileline: off + # Log to standard error. When in doubt, set to no. Useful when + # running in the foreground (when invoking "corosync -f") + to_stderr: no + # Log to a log file. When set to "no", the "logfile" option + # must not be set. + to_logfile: yes + logfile: /var/log/cluster/corosync.log + # Log to the system log daemon. When in doubt, set to yes. + to_syslog: yes + # Log debug messages (very verbose). When in doubt, leave off. + debug: off + # Log messages with time stamps. When in doubt, set to on + # (unless you are only logging to syslog, where double + # timestamps can be annoying). + timestamp: on + logger_subsys { + subsys: QUORUM + debug: off + } } -amf { - mode: disabled +quorum { + provider: corosync_votequorum + expected_votes: 2 } ..... 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 b53d748b84..f7692e1a6a 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,549 @@ = 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 Corosync 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 -about whether some nodes are alive or dead - which quickly leads to -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. -========= - +Fedora 17. === Installing the required Software === [source,Bash] ----- -# yum install -y cman gfs2-utils gfs2-cluster -Loaded plugins: auto-update-debuginfo -Setting up Install Process +# yum install -y gfs2-utils dlm +Loaded plugins: langpacks, presto, refresh-packagekit 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 +---> Package dlm.x86_64 0:3.99.1-4.fc17 will be installed +--> Processing Dependency: dlm-lib = 3.99.1-4.fc17 for package: dlm-3.99.1-4.fc17.x86_64 +--> Processing Dependency: libdlmcontrol.so.3()(64bit) for package: dlm-3.99.1-4.fc17.x86_64 +--> Processing Dependency: libdlm.so.3()(64bit) for package: dlm-3.99.1-4.fc17.x86_64 +---> Package gfs2-utils.x86_64 0:3.1.4-3.fc17 will be installed --> 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 +---> Package dlm-lib.x86_64 0:3.99.1-4.fc17 will be installed --> Finished Dependency Resolution Dependencies Resolved -============================================================================= - Package Arch Version Repository Size -============================================================================= +===================================================================================== + 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 + dlm x86_64 3.99.1-4.fc17 updates-testing 77 k + gfs2-utils x86_64 3.1.4-3.fc17 fedora 214 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 + dlm-lib x86_64 3.99.1-4.fc17 updates-testing 19 k Transaction Summary -============================================================================= -Install 34 Package(s) +===================================================================================== +Install 2 Packages (+1 Dependent package) -Total download size: 10 M -Installed size: 38 M +Total download size: 309 k +Installed size: 879 k 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 +(1/3): dlm-3.99.1-4.fc17.x86_64.rpm | 77 kB 00:00 +(2/3): dlm-lib-3.99.1-4.fc17.x86_64.rpm | 19 kB 00:00 +(3/3): gfs2-utils-3.1.4-3.fc17.x86_64.rpm | 214 kB 00:00 + ------------------------------------------------------------------------------------- +Total 241 kB/s | 309 kB 00:01 +Running Transaction Check 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 + Installing : dlm-lib-3.99.1-4.fc17.x86_64 1/3 + Installing : dlm-3.99.1-4.fc17.x86_64 2/3 + Installing : gfs2-utils-3.1.4-3.fc17.x86_64 3/3 + Verifying : dlm-lib-3.99.1-4.fc17.x86_64 1/3 + Verifying : gfs2-utils-3.1.4-3.fc17.x86_64 2/3 + Verifying : dlm-3.99.1-4.fc17.x86_64 3/3 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 + dlm.x86_64 0:3.99.1-4.fc17 gfs2-utils.x86_64 0:3.1.4-3.fc17 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 + dlm-lib.x86_64 0:3.99.1-4.fc17 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 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 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 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 +# crm resource stop WebFS +# crm_mon -1 ============ -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. +Last updated: Tue Apr 3 14:07:36 2012 +Last change: Tue Apr 3 14:07:15 2012 via cibadmin on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes +5 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] -Master/Slave Set: WebDataClone - Masters: [ pcmk-1 ] - Slaves: [ pcmk-2 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1 + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2 + Master/Slave Set: WebDataClone [WebData] + Masters: [ pcmk-2 ] + Slaves: [ 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). +field is +clustername:fsname+. For the +fsname+, we need to use the same +value as specified in 'cluster.conf' for +cluster_name+. Just pick +something unique and descriptive and add somewhere inside the +totem+ +block. For example: -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 +totem { + version: 2 + + # cypto_cipher and crypto_hash: Used for mutual node authentication. + # If you choose to enable this, then do remember to create a shared + # secret with "corosync-keygen". + crypto_cipher: none + crypto_hash: none + cluster_name: webtest + ... ..... + +[IMPORTANT] +=========== Do this on each node in the cluster and be sure to restart them before continuing. +=========== + +[IMPORTANT] +=========== +We must run the next command on whichever node last had '/dev/drbd' +mounted. Otherwise you will receive the message: + +----- +/dev/drbd1: Read-only file system +----- +=========== [source,Bash] ----- -# mkfs.gfs2 -p lock_dlm -j 2 -t pcmk:web /dev/drbd1 +# ssh pcmk-2 -- mkfs.gfs2 -p lock_dlm -j 2 -t webtest /dev/drbd1 This will destroy any data on /dev/drbd1. -It appears to contain: data +It appears to contain: Linux rev 1.0 ext4 filesystem data, UUID=dc45fff3-c47a-4db2-96f7-a8049a323fe4 (extents) (large files) (huge files) +Are you sure you want to proceed? [y/n]y +Device: /dev/drbd1 +Blocksize: 4096 +Device Size 0.97 GB (253935 blocks) +Filesystem Size: 0.97 GB (253932 blocks) +Journals: 2 +Resource Groups: 4 +Locking Protocol: "lock_dlm" +Lock Table: "webtest" +UUID: ed293a02-9eee-3fa3-ed1c-435ef1fd0116 +----- -Are you sure you want to proceed? [y/n] y +[source,Bash] +----- +# crm +crm(live)# cib new dlm +INFO: dlm shadow CIB created +crm(dlm)# configure primitive dlm ocf:pacemaker:controld \ + op monitor interval=60s +crm(dlm)# configure clone dlm_clone dlm meta clone-max=2 clone-node-max=1 +crm(dlm)# configure show +node $id="1702537408" pcmk-1 \ + attributes standby="off" +node $id="1719314624" pcmk-2 +primitive ClusterIP ocf:heartbeat:IPaddr2 \ + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" +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" \ + meta target-role="Stopped" +primitive WebSite ocf:heartbeat:apache \ + params configfile="/etc/httpd/conf/httpd.conf" \ + op monitor interval="1min" +primitive dlm ocf:pacemaker:controld \ + op monitor interval="60s" +ms WebDataClone WebData \ + meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" +clone dlm_clone dlm \ + meta clone-max="2" clone-node-max="1" +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.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" \ + last-lrm-refresh="1333446866" +rsc_defaults $id="rsc-options" \ + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" +crm(dlm)# cib commit dlm +INFO: commited 'dlm' shadow CIB to the cluster +crm(dlm)# quit +bye +# crm_mon -1 +============ +Last updated: Wed Apr 4 01:15:11 2012 +Last change: Wed Apr 4 00:50:11 2012 via crmd on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes +7 Resources configured. +============ + +Online: [ pcmk-1 pcmk-2 ] -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 + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1 + Master/Slave Set: WebDataClone [WebData] + Masters: [ pcmk-1 ] + Slaves: [ pcmk-2 ] + Clone Set: dlm_clone [dlm] + Started: [ pcmk-1 pcmk-2 ] ----- + +[WARNING] +========= +Nothing has been updated past this point and is probably severely broken. +========= + 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 +# 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. +[source,Bash] +----- # 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 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-Active-Passive.txt b/doc/Clusters_from_Scratch/en-US/Ch-Active-Passive.txt index 5b7719993e..5bd57f6787 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Active-Passive.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Active-Passive.txt @@ -1,418 +1,372 @@ = Creating an Active/Passive Cluster = == Exploring the Existing Configuration == When Pacemaker starts up, it automatically records the number and details of the nodes in the cluster as well as which stack is being used and the version of Pacemaker being used. This is what the base configuration should look like. [source,Bash] ---- # crm configure show -node pcmk-1 -node pcmk-2 +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 property $id="cib-bootstrap-options" \ - dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ - cluster-infrastructure="openais" \ - expected-quorum-votes="2" + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" ---- For those that are not of afraid of XML, you can see the raw configuration by appending "xml" to the previous command. .The last XML you'll see in this document [source,Bash] ---- # crm configure show xml - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + ---- Before we make any changes, its a good idea to check the validity of the configuration. [source,Bash] ---- # crm_verify -L -crm_verify[2195]: 2009/08/27_16:57:12 ERROR: unpack_resources: Resource start-up disabled since no STONITH resources have been defined -crm_verify[2195]: 2009/08/27_16:57:12 ERROR: unpack_resources: Either configure some or disable STONITH with the stonith-enabled option -crm_verify[2195]: 2009/08/27_16:57:12 ERROR: unpack_resources: NOTE: Clusters with shared data need STONITH to ensure data integrity -Errors found during check: config not valid -V may provide more details -# + error: unpack_resources: Resource start-up disabled since no STONITH resources have been defined + error: unpack_resources: Either configure some or disable STONITH with the stonith-enabled option + error: unpack_resources: NOTE: Clusters with shared data need STONITH to ensure data integrity +Errors found during check: config not valid + -V may provide more details ---- As you can see, the tool has found some errors. In order to guarantee the safety of your data footnote:[If the data is corrupt, there is little point in continuing to make it available] , Pacemaker ships with STONITH footnote:[A common node fencing mechanism. Used to ensure data integrity by powering off "bad" nodes] enabled. However it also knows when no STONITH configuration has been supplied and reports this as a problem (since the cluster would not be able to make progress if a situation requiring node fencing arose). For now, we will disable this feature and configure it later in the Configuring STONITH section. It is important to note that the use of STONITH is highly encouraged, turning it off tells the cluster to simply pretend that failed nodes are safely powered off. Some vendors will even refuse to support clusters that have it disabled. To disable STONITH, we set the stonith-enabled cluster option to false. [source,Bash] ---- # crm configure property stonith-enabled=false # crm_verify -L ---- With the new cluster option set, the configuration is now valid. [WARNING] ========= The use of stonith-enabled=false is completely inappropriate for a production cluster. We use it here to defer the discussion of its configuration which can differ widely from one installation to the next. See <<_what_is_stonith>> for information on why STONITH is important and details on how to configure it. ========= == Adding a Resource == The first thing we should do is configure an IP address. Regardless of where the cluster service(s) are running, we need a consistent address -to contact them on. Here I will choose and add 192.168.122.101 as the +to contact them on. Here I will choose and add 192.168.122.120 as the floating address, give it the imaginative name ClusterIP and tell the cluster to check that its running every 30 seconds. [IMPORTANT] =========== The chosen address must not be one already associated with a physical node =========== [source,Bash] ---- # crm configure primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip=192.168.122.101 cidr_netmask=32 \ + params ip=192.168.122.120 cidr_netmask=32 \ op monitor interval=30s ---- The other important piece of information here is ocf:heartbeat:IPaddr2. This tells Pacemaker three things about the resource you want to add. The first field, ocf, is the standard to which the resource script conforms to and where to find it. The second field is specific to OCF resources and tells the cluster which namespace to find the resource script in, in this case heartbeat. The last field indicates the name of the resource script. To obtain a list of the available resource classes, run [source,Bash] ---- -# crm ra classesheartbeat -lsb ocf / heartbeat pacemakerstonith +# crm ra classes +heartbeat +lsb +ocf / heartbeat pacemaker +stonith ---- To then find all the OCF resource agents provided by Pacemaker and Heartbeat, run [source,Bash] ---- # crm ra list ocf pacemaker -ClusterMon Dummy Stateful SysInfo SystemHealth controld -ping pingd +ClusterMon Dummy HealthCPU HealthSMART Stateful SysInfo +SystemHealth controld o2cb ping pingd # crm ra list ocf heartbeat -AoEtarget AudibleAlarm ClusterMon Delay -Dummy EvmsSCC Evmsd Filesystem -ICP IPaddr IPaddr2 IPsrcaddr -LVM LinuxSCSI MailTo ManageRAID -ManageVE Pure-FTPd Raid1 Route -SAPDatabase SAPInstance SendArp ServeRAID -SphinxSearchDaemon Squid Stateful SysInfo -VIPArip VirtualDomain WAS WAS6 -WinPopup Xen Xinetd anything -apache db2 drbd eDir88 -iSCSILogicalUnit iSCSITarget ids iscsi -ldirectord mysql mysql-proxy nfsserver -oracle oralsnr pgsql pingd -portblock rsyncd scsi2reservation sfex -tomcat vmware -# +AoEtarget AudibleAlarm CTDB ClusterMon +Delay Dummy EvmsSCC Evmsd +Filesystem ICP IPaddr IPaddr2 +IPsrcaddr IPv6addr LVM LinuxSCSI +MailTo ManageRAID ManageVE Pure-FTPd +Raid1 Route SAPDatabase SAPInstance +SendArp ServeRAID SphinxSearchDaemon Squid +Stateful SysInfo VIPArip VirtualDomain +WAS WAS6 WinPopup Xen +Xinetd anything apache conntrackd +db2 drbd eDir88 ethmonitor +exportfs fio iSCSILogicalUnit iSCSITarget +ids iscsi jboss ldirectord +lxc mysql mysql-proxy nfsserver +nginx oracle oralsnr pgsql +pingd portblock postfix proftpd +rsyncd scsi2reservation sfex symlink +syslog-ng tomcat vmware ---- Now verify that the IP resource has been added and display the cluster's status to see that it is now active. [source,Bash] ---- -# crm configure shownode pcmk-1 -node pcmk-2primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip="192.168.122.101" cidr_netmask="32" \ - op monitor interval="30s" +# crm configure show +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 +primitive ClusterIP ocf:heartbeat:IPaddr2 \ + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" property $id="cib-bootstrap-options" \ - dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ - cluster-infrastructure="openais" \ - expected-quorum-votes="2" \ - stonith-enabled="false" \ -# crm_mon + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" +# crm_mon -1 ============ -Last updated: Fri Aug 28 15:23:48 2009 -Stack: openais -Current DC: pcmk-1 - partition with quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes +Last updated: Tue Apr 3 09:56:50 2012 +Last change: Tue Apr 3 09:54:37 2012 via cibadmin on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 1 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1 + + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1 ---- == Perform a Failover == Being a high-availability cluster, we should test failover of our new resource before moving on. First, find the node on which the IP address is running. [source,Bash] ---- # crm resource status ClusterIP resource ClusterIP is running on: pcmk-1 -# ---- Shut down Pacemaker and Corosync on that machine. [source,Bash] ---- -# ssh pcmk-1 -- /etc/init.d/pacemaker stop -Signaling Pacemaker Cluster Manager to terminate: [ OK ] -Waiting for cluster services to unload:. [ OK ] -# ssh pcmk-1 -- /etc/init.d/corosync stop -Stopping Corosync Cluster Engine (corosync): [ OK ] -Waiting for services to unload: [ OK ] -# +# ssh pcmk-1 -- service pacemaker stop +# ssh pcmk-1 -- service corosync stop ---- Once Corosync is no longer running, go to the other node and check the cluster status with crm_mon. [source,Bash] ---- -# crm_mon +# crm_mon -1 ============ -Last updated: Fri Aug 28 15:27:35 2009 -Stack: openais -Current DC: pcmk-2 - partition WITHOUT quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes +Last updated: Tue Apr 3 10:01:28 2012 +Last change: Tue Apr 3 09:54:39 2012 via cibadmin on pcmk-1 +Stack: corosync +Current DC: pcmk-2 (1719314624) - partition WITHOUT quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 1 Resources configured. ============ -Online: [ pcmk-2 ]OFFLINE: [ pcmk-1 ] +Online: [ pcmk-2 ] +OFFLINE: [ pcmk-1 ] ---- There are three things to notice about the cluster's current -state. The first is that, as expected, pcmk-1 is now offline. However -we can also see that ClusterIP isn't running anywhere! +state. The first is that, as expected, +pcmk-1+ is now offline. However +we can also see that +ClusterIP+ isn't running anywhere! === Quorum and Two-Node Clusters === This is because the cluster no longer has quorum, as can be seen by the text "partition WITHOUT quorum" (emphasised green) in the output above. In order to reduce the possibility of data corruption, Pacemaker's default behavior is to stop all resources if the cluster does not have quorum. A cluster is said to have quorum when more than half the known or expected nodes are online, or for the mathematically inclined, whenever the following equation is true: .... total_nodes < 2 * active_nodes .... Therefore a two-node cluster only has quorum when both nodes are running, which is no longer the case for our cluster. This would normally make the creation of a two-node cluster pointless footnote:[Actually some would argue that two-node clusters are always pointless, but that is an argument for another time] , however it is possible to control how Pacemaker behaves when quorum is lost. In particular, we can tell the cluster to simply ignore quorum altogether. [source,Bash] ---- # crm configure property no-quorum-policy=ignore # crm configure show -node pcmk-1 -node pcmk-2 +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip="192.168.122.101" cidr_netmask="32" \ - op monitor interval="30s" + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" 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" + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" ---- After a few moments, the cluster will start the IP address on the remaining node. Note that the cluster still does not have quorum. [source,Bash] ---- -# crm_mon +# crm_mon -1 ============ -Last updated: Fri Aug 28 15:30:18 2009 -Stack: openais -Current DC: pcmk-2 - partition WITHOUT quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes +Last updated: Tue Apr 3 10:02:46 2012 +Last change: Tue Apr 3 10:02:08 2012 via cibadmin on pcmk-2 +Stack: corosync +Current DC: pcmk-2 (1719314624) - partition WITHOUT quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 1 Resources configured. ============ + Online: [ pcmk-2 ] OFFLINE: [ pcmk-1 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2 + + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2 ---- -Now simulate node recovery by restarting the cluster stack on pcmk-1 and +Now simulate node recovery by restarting the cluster stack on +pcmk-1+ and check the cluster's status. [source,Bash] ---- -# /etc/init.d/corosync start +# service corosync start Starting Corosync Cluster Engine (corosync): [ OK ] -# /etc/init.d/pacemaker start +# service pacemaker start Starting Pacemaker Cluster Manager: [ OK ]# crm_mon ============ Last updated: Fri Aug 28 15:32:13 2009 Stack: openais Current DC: pcmk-2 - partition with quorum Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f 2 Nodes configured, 2 expected votes 1 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1 +ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2 ---- -Here we see something that some may consider surprising, the IP is back -running at its original location! - +[NOTE] +====== +In the dark days, the cluster may have moved the IP back to its +original location (+pcmk-1+). Usually this is no longer the case. +====== === Prevent Resources from Moving after Recovery === -In some circumstances, it is highly desirable to prevent healthy +In most circumstances, it is highly desirable to prevent healthy resources from being moved around the cluster. Moving resources almost always requires a period of downtime. For complex services like Oracle databases, this period can be quite long. To address this, Pacemaker has the concept of resource stickiness which controls how much a service prefers to stay running where it is. You may like to think of it as the "cost" of any downtime. By default, Pacemaker assumes there is zero cost associated with moving resources and will do so to achieve "optimal" footnote:[It should be noted that Pacemaker's definition of optimal may not always agree with that of a human's. The order in which Pacemaker processes lists of resources and nodes creates implicit preferences in situations where the administrator has not explicitly specified them] resource placement. We can specify a different stickiness for every resource, but it is often sufficient to change the default. [source,Bash] ---- # crm configure rsc_defaults resource-stickiness=100 # crm configure show -node pcmk-1 -node pcmk-2 +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip="192.168.122.101" cidr_netmask="32" \ - op monitor interval="30s" + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" 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" ----- - -If we now retry the failover test, we see that as expected ClusterIP -still moves to pcmk-2 when pcmk-1 is taken offline. - -[source,Bash] ----- -# ssh pcmk-1 -- /etc/init.d/pacemaker stop -Signaling Pacemaker Cluster Manager to terminate: [ OK ] -Waiting for cluster services to unload:. [ OK ] -# ssh pcmk-1 -- /etc/init.d/corosync stop -Stopping Corosync Cluster Engine (corosync): [ OK ] -Waiting for services to unload: [ OK ] -# ssh pcmk-2 -- crm_mon -1 -============ -Last updated: Fri Aug 28 15:39:38 2009 -Stack: openais -Current DC: pcmk-2 - partition WITHOUT quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes -1 Resources configured. -============ - -Online: [ pcmk-2 ] -OFFLINE: [ pcmk-1 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2 ----- - -However when we bring pcmk-1 back online, ClusterIP now remains running -on pcmk-2. - -[source,Bash] ----- -# /etc/init.d/corosync start -Starting Corosync Cluster Engine (corosync): [ OK ] -# /etc/init.d/pacemaker start -Starting Pacemaker Cluster Manager: [ OK ] -# crm_mon -============ -Last updated: Fri Aug 28 15:41:23 2009 -Stack: openais -Current DC: pcmk-2 - partition with quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes -1 Resources configured. -============ - -Online: [ pcmk-1 pcmk-2 ] - -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2 + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" +rsc_defaults $id="rsc-options" \ + resource-stickiness="100" ---- diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Apache.txt b/doc/Clusters_from_Scratch/en-US/Ch-Apache.txt index ef747ab3cd..497616bf9c 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Apache.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Apache.txt @@ -1,492 +1,572 @@ = Apache - Adding More Services = == Forward == Now that we have a basic but functional active/passive two-node cluster, we're ready to add some real services. We're going to start with Apache because its a feature of many clusters and relatively simple to configure. == Installation == Before continuing, we need to make sure Apache is installed on both hosts. [source,Bash] ------ -# yum install -y httpdSetting up Install Process +..... +# yum install -y httpd +Loaded plugins: langpacks, presto, refresh-packagekit +fedora/metalink | 2.6 kB 00:00 +updates/metalink | 3.2 kB 00:00 +updates-testing/metalink | 41 kB 00:00 Resolving Dependencies --> Running transaction check ----> Package httpd.x86_64 0:2.2.13-2.fc12 set to be updated ---> Processing Dependency: httpd-tools = 2.2.13-2.fc12 for package: httpd-2.2.13-2.fc12.x86_64 ---> Processing Dependency: apr-util-ldap for package: httpd-2.2.13-2.fc12.x86_64 ---> Processing Dependency: /etc/mime.types for package: httpd-2.2.13-2.fc12.x86_64 ---> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.2.13-2.fc12.x86_64 ---> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.2.13-2.fc12.x86_64 +---> Package httpd.x86_64 0:2.2.22-3.fc17 will be installed +--> Processing Dependency: httpd-tools = 2.2.22-3.fc17 for package: httpd-2.2.22-3.fc17.x86_64 +--> Processing Dependency: apr-util-ldap for package: httpd-2.2.22-3.fc17.x86_64 +--> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.2.22-3.fc17.x86_64 +--> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.2.22-3.fc17.x86_64 --> Running transaction check ----> Package apr.x86_64 0:1.3.9-2.fc12 set to be updated ----> Package apr-util.x86_64 0:1.3.9-2.fc12 set to be updated ----> Package apr-util-ldap.x86_64 0:1.3.9-2.fc12 set to be updated ----> Package httpd-tools.x86_64 0:2.2.13-2.fc12 set to be updated ----> Package mailcap.noarch 0:2.1.30-1.fc12 set to be updated +---> Package apr.x86_64 0:1.4.6-1.fc17 will be installed +---> Package apr-util.x86_64 0:1.4.1-2.fc17 will be installed +---> Package apr-util-ldap.x86_64 0:1.4.1-2.fc17 will be installed +---> Package httpd-tools.x86_64 0:2.2.22-3.fc17 will be installed --> Finished Dependency Resolution Dependencies Resolved -======================================================================================= -Package Arch Version Repository Size -======================================================================================= +===================================================================================== + Package Arch Version Repository Size +===================================================================================== Installing: -httpd x86_64 2.2.13-2.fc12 rawhide 735 k + httpd x86_64 2.2.22-3.fc17 updates-testing 823 k Installing for dependencies: -apr x86_64 1.3.9-2.fc12 rawhide 117 k -apr-util x86_64 1.3.9-2.fc12 rawhide 84 k -apr-util-ldap x86_64 1.3.9-2.fc12 rawhide 15 k -httpd-tools x86_64 2.2.13-2.fc12 rawhide 63 k -mailcap noarch 2.1.30-1.fc12 rawhide 25 k + apr x86_64 1.4.6-1.fc17 fedora 99 k + apr-util x86_64 1.4.1-2.fc17 fedora 78 k + apr-util-ldap x86_64 1.4.1-2.fc17 fedora 17 k + httpd-tools x86_64 2.2.22-3.fc17 updates-testing 74 k Transaction Summary -======================================================================================= -Install 6 Package(s) -Upgrade 0 Package(s) +===================================================================================== +Install 1 Package (+4 Dependent packages) -Total download size: 1.0 M +Total download size: 1.1 M +Installed size: 3.5 M Downloading Packages: -(1/6): apr-1.3.9-2.fc12.x86_64.rpm | 117 kB 00:00 -(2/6): apr-util-1.3.9-2.fc12.x86_64.rpm | 84 kB 00:00 -(3/6): apr-util-ldap-1.3.9-2.fc12.x86_64.rpm | 15 kB 00:00 -(4/6): httpd-2.2.13-2.fc12.x86_64.rpm | 735 kB 00:00 -(5/6): httpd-tools-2.2.13-2.fc12.x86_64.rpm | 63 kB 00:00 -(6/6): mailcap-2.1.30-1.fc12.noarch.rpm | 25 kB 00:00 - ---------------------------------------------------------------------------------------- -Total 875 kB/s | 1.0 MB 00:01 -Running rpm_check_debug +(1/5): apr-1.4.6-1.fc17.x86_64.rpm | 99 kB 00:00 +(2/5): apr-util-1.4.1-2.fc17.x86_64.rpm | 78 kB 00:00 +(3/5): apr-util-ldap-1.4.1-2.fc17.x86_64.rpm | 17 kB 00:00 +(4/5): httpd-2.2.22-3.fc17.x86_64.rpm | 823 kB 00:01 +(5/5): httpd-tools-2.2.22-3.fc17.x86_64.rpm | 74 kB 00:00 +------------------------------------------------------------------------------------- +Total 238 kB/s | 1.1 MB 00:04 +Running Transaction Check Running Transaction Test -Finished Transaction Test Transaction Test Succeeded Running Transaction - Installing : apr-1.3.9-2.fc12.x86_64 1/6 - Installing : apr-util-1.3.9-2.fc12.x86_64 2/6 - Installing : apr-util-ldap-1.3.9-2.fc12.x86_64 3/6 - Installing : httpd-tools-2.2.13-2.fc12.x86_64 4/6 - Installing : mailcap-2.1.30-1.fc12.noarch 5/6 - Installing : httpd-2.2.13-2.fc12.x86_64 6/6 + Installing : apr-1.4.6-1.fc17.x86_64 1/5 + Installing : apr-util-1.4.1-2.fc17.x86_64 2/5 + Installing : apr-util-ldap-1.4.1-2.fc17.x86_64 3/5 + Installing : httpd-tools-2.2.22-3.fc17.x86_64 4/5 + Installing : httpd-2.2.22-3.fc17.x86_64 5/5 + Verifying : apr-util-ldap-1.4.1-2.fc17.x86_64 1/5 + Verifying : httpd-tools-2.2.22-3.fc17.x86_64 2/5 + Verifying : apr-util-1.4.1-2.fc17.x86_64 3/5 + Verifying : apr-1.4.6-1.fc17.x86_64 4/5 + Verifying : httpd-2.2.22-3.fc17.x86_64 5/5 Installed: - httpd.x86_64 0:2.2.13-2.fc12 + httpd.x86_64 0:2.2.22-3.fc17 Dependency Installed: - apr.x86_64 0:1.3.9-2.fc12 apr-util.x86_64 0:1.3.9-2.fc12 - apr-util-ldap.x86_64 0:1.3.9-2.fc12 httpd-tools.x86_64 0:2.2.13-2.fc12 - mailcap.noarch 0:2.1.30-1.fc12 + apr.x86_64 0:1.4.6-1.fc17 apr-util.x86_64 0:1.4.1-2.fc17 + apr-util-ldap.x86_64 0:1.4.1-2.fc17 httpd-tools.x86_64 0:2.2.22-3.fc17 Complete! ------ +..... Also, we need the wget tool in order for the cluster to be able to check the status of the Apache server. [source,Bash] ------ -# yum install -y wgetSetting up Install Process +..... +# yum install -y wget +Loaded plugins: langpacks, presto, refresh-packagekit Resolving Dependencies --> Running transaction check ----> Package wget.x86_64 0:1.11.4-5.fc12 set to be updated +---> Package wget.x86_64 0:1.13.4-2.fc17 will be installed --> Finished Dependency Resolution Dependencies Resolved -=========================================================================================== -Package Arch Version Repository Size -=========================================================================================== +===================================================================================== + Package Arch Version Repository Size +===================================================================================== Installing: -wget x86_64 1.11.4-5.fc12 rawhide 393 k + wget x86_64 1.13.4-2.fc17 fedora 495 k Transaction Summary -=========================================================================================== -Install 1 Package(s) -Upgrade 0 Package(s) +===================================================================================== +Install 1 Package -Total download size: 393 k +Total download size: 495 k +Installed size: 1.8 M Downloading Packages: -wget-1.11.4-5.fc12.x86_64.rpm | 393 kB 00:00 -Running rpm_check_debug +wget-1.13.4-2.fc17.x86_64.rpm | 495 kB 00:01 +Running Transaction Check Running Transaction Test -Finished Transaction Test Transaction Test Succeeded Running Transaction - Installing : wget-1.11.4-5.fc12.x86_64 1/1 + Installing : wget-1.13.4-2.fc17.x86_64 1/1 + Verifying : wget-1.13.4-2.fc17.x86_64 1/1 Installed: - wget.x86_64 0:1.11.4-5.fc12 + wget.x86_64 0:1.13.4-2.fc17 Complete! ------ - +..... == Preparation == First we need to create a page for Apache to serve up. On Fedora the default Apache docroot is /var/www/html, so we'll create an index file there. [source,Bash] ----- -[root@pcmk-1 ~]# cat <<-END >/var/www/html/index.html +# cat <<-END >/var/www/html/index.html + My Test Site - pcmk-1 - END +END ----- For the moment, we will simplify things by serving up only a static site and manually sync the data between the two nodes. So run the command again on pcmk-2. [source,Bash] ----- [root@pcmk-2 ~]# cat <<-END >/var/www/html/index.html My Test Site - pcmk-2 END ----- == Enable the Apache status URL == In order to monitor the health of your Apache instance, and recover it if it fails, the resource agent used by Pacemaker assumes the server-status -URL is available. Look for the following in /etc/httpd/conf/httpd.conf +URL is available. Look for the following in '/etc/httpd/conf/httpd.conf' and make sure it is not disabled or commented out: ..... SetHandler server-status Order deny,allow Deny from all Allow from 127.0.0.1 ..... == Update the Configuration == At this point, Apache is ready to go, all that needs to be done is to add it to the cluster. Lets call the resource WebSite. We need to use an OCF script called apache in the heartbeat namespace footnote:[Compare the key used here ocf:heartbeat:apache with the one we used earlier for the IP address: ocf:heartbeat:IPaddr2] , the only required parameter is the path to the main Apache configuration file and we'll tell the cluster to check once a minute that apache is still running. [source,Bash] ----- -# crm configure primitive WebSite ocf:heartbeat:apache params configfile=/etc/httpd/conf/httpd.conf op monitor interval=1min +# crm configure primitive WebSite ocf:heartbeat:apache \ + params configfile=/etc/httpd/conf/httpd.conf \ + op monitor interval=1min +WARNING: WebSite: default timeout 20s for start is smaller than the advised 40s +WARNING: WebSite: default timeout 20s for stop is smaller than the advised 60s +----- + +The easiest way resolve this, is to change the default: + +[source,Bash] +----- +# crm configure op_defaults timeout=240s # crm configure show -node pcmk-1 -node pcmk-2primitive 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" +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 +primitive ClusterIP ocf:heartbeat:IPaddr2 \ + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" +primitive WebSite ocf:heartbeat:apache \ + params configfile="/etc/httpd/conf/httpd.conf" \ + op monitor interval="1min" 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" + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ - resource-stickiness="100" + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" ----- After a short delay, we should see the cluster start apache [source,Bash] ----- -# crm_mon +# crm_mon -1 ============ -Last updated: Fri Aug 28 16:12:49 2009 -Stack: openais -Current DC: pcmk-2 - partition with quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes +Last updated: Tue Apr 3 11:54:29 2012 +Last change: Tue Apr 3 11:54:26 2012 via crmd on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 2 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2 -WebSite (ocf::heartbeat:apache): Started pcmk-1 +ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2 +WebSite (ocf::heartbeat:apache): Started pcmk-1 ----- Wait a moment, the WebSite resource isn't running on the same host as our IP address! +[NOTE] +====== +If, in the `crm_mon` output, you see: + +.... +Failed actions: + WebSite_start_0 (node=pcmk-2, call=301, rc=1, status=complete): unknown error +.... + +Then you've likely not enabled the status URL correctly. +You can check if this is the problem by running: + +.... +wget http://127.0.0.1/server-status +.... + +If you see +Connection refused+ in the output, then this is indeed the +problem. Check to ensure that +Allow from 127.0.0.1+ is present for +the ++ block. + +====== == Ensuring Resources Run on the Same Host == To reduce the load on any one machine, Pacemaker will generally try to spread the configured resources across the cluster nodes. However we can tell the cluster that two resources are related and need to run on the same host (or not at all). Here we instruct the cluster that WebSite can only run on the host that ClusterIP is active on. For the constraint, we need a name (choose something descriptive like website-with-ip), indicate that its mandatory (so that if ClusterIP is not active anywhere, WebSite will not be permitted to run anywhere either) by specifying a score of INFINITY and finally list the two resources. [NOTE] ======= If ClusterIP is not active anywhere, WebSite will not be permitted to run anywhere. ======= [IMPORTANT] =========== Colocation constraints are "directional", in that they imply certain things about the order in which the two resources will have a location chosen. In this case we're saying +WebSite+ needs to be placed on the same machine as +ClusterIP+, this implies that we must know the location of +ClusterIP+ before choosing a location for +WebSite+. =========== [source,Bash] ----- # crm configure colocation website-with-ip INFINITY: WebSite ClusterIP # crm configure show -node pcmk-1 -node pcmk-2 -primitive WebSite ocf:heartbeat:apache \ - params configfile="/etc/httpd/conf/httpd.conf" \ - op monitor interval="1min" +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip="192.168.122.101" cidr_netmask="32" \ - op monitor interval="30s"colocation website-with-ip inf: WebSite ClusterIPproperty $id="cib-bootstrap-options" \ - dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ - cluster-infrastructure="openais" \ - expected-quorum-votes="2" \ - stonith-enabled="false" \ - no-quorum-policy="ignore" + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" +primitive WebSite ocf:heartbeat:apache \ + params configfile="/etc/httpd/conf/httpd.conf" \ + op monitor interval="1min" +colocation website-with-ip inf: WebSite ClusterIP +property $id="cib-bootstrap-options" \ + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" \ + last-lrm-refresh="1333446866" rsc_defaults $id="rsc-options" \ - resource-stickiness="100" -# crm_mon + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" +# crm_mon -1 ============ -Last updated: Fri Aug 28 16:14:34 2009 -Stack: openais -Current DC: pcmk-2 - partition with quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes +Last updated: Tue Apr 3 11:57:13 2012 +Last change: Tue Apr 3 11:56:10 2012 via cibadmin on pcmk-1 +Stack: corosync +Current DC: pcmk-2 (1719314624) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 2 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2 -WebSite (ocf::heartbeat:apache): Started pcmk-2 + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2 + WebSite (ocf::heartbeat:apache): Started pcmk-2 ----- == Controlling Resource Start/Stop Ordering == When Apache starts, it binds to the available IP addresses. It doesn't know about any addresses we add afterwards, so not only do they need to run on the same node, but we need to make sure ClusterIP is already active before we start WebSite. We do this by adding an ordering constraint. We need to give it a name (choose something descriptive like apache-after-ip), indicate that its mandatory (so that any recovery for ClusterIP will also trigger recovery of WebSite) and list the two resources in the order we need them to start. [source,Bash] ----- # crm configure order apache-after-ip mandatory: ClusterIP WebSite # crm configure show -node pcmk-1 -node pcmk-2 -primitive WebSite ocf:heartbeat:apache \ - params configfile="/etc/httpd/conf/httpd.conf" \ - op monitor interval="1min" +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip="192.168.122.101" cidr_netmask="32" \ - op monitor interval="30s" -colocation website-with-ip inf: WebSite ClusterIPorder apache-after-ip inf: ClusterIP WebSiteproperty $id="cib-bootstrap-options" \ - dc-version="1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f" \ - cluster-infrastructure="openais" \ - expected-quorum-votes="2" \ - stonith-enabled="false" \ - no-quorum-policy="ignore" + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" +primitive WebSite ocf:heartbeat:apache \ + params configfile="/etc/httpd/conf/httpd.conf" \ + op monitor interval="1min" +colocation website-with-ip inf: WebSite ClusterIP +order apache-after-ip inf: ClusterIP WebSite +property $id="cib-bootstrap-options" \ + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" \ + last-lrm-refresh="1333446866" rsc_defaults $id="rsc-options" \ - resource-stickiness="100" + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" ----- == Specifying a Preferred Location == Pacemaker does not rely on any sort of hardware symmetry between nodes, so it may well be that one machine is more powerful than the other. In such cases it makes sense to host the resources there if it is available. To do this we create a location constraint. Again we give it a descriptive name (prefer-pcmk-1), specify the resource we want to run there (WebSite), how badly we'd like it to run there (we'll use 50 for now, but in a two-node situation almost any value above 0 will do) and the host's name. [source,Bash] ----- # crm configure location prefer-pcmk-1 WebSite 50: pcmk-1 +WARNING: prefer-pcmk-1: referenced node pcmk-1 does not exist +----- + +This warning should be ignored. + +[source,Bash] +----- # crm configure show -node pcmk-1 -node pcmk-2 -primitive WebSite ocf:heartbeat:apache \ - params configfile="/etc/httpd/conf/httpd.conf" \ - op monitor interval="1min" +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip="192.168.122.101" cidr_netmask="32" \ - op monitor interval="30s"location prefer-pcmk-1 WebSite 50: pcmk-1colocation website-with-ip inf: WebSite ClusterIP + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" +primitive WebSite ocf:heartbeat:apache \ + params configfile="/etc/httpd/conf/httpd.conf" \ + op monitor interval="1min" +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" + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" \ + last-lrm-refresh="1333446866" rsc_defaults $id="rsc-options" \ - resource-stickiness="100" -# crm_mon + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" +# crm_mon -1 ============ -Last updated: Fri Aug 28 16:17:35 2009 -Stack: openais -Current DC: pcmk-2 - partition with quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes +Last updated: Tue Apr 3 12:02:14 2012 +Last change: Tue Apr 3 11:59:42 2012 via cibadmin on pcmk-1 +Stack: corosync +Current DC: pcmk-2 (1719314624) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 2 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-2WebSite (ocf::heartbeat:apache): Started pcmk-2 + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2 + WebSite (ocf::heartbeat:apache): Started pcmk-2 ----- Wait a minute, the resources are still on pcmk-2! Even though we now prefer pcmk-1 over pcmk-2, that preference is (intentionally) less than the resource stickiness (how much we preferred not to have unnecessary downtime). -To see the current placement scores, you can use a tool called ptest +To see the current placement scores, you can use a tool called crm_simulate -.... -ptest -sL -.... +[source,Bash] +---- +# crm_simulate -sL +Current cluster status: +Online: [ pcmk-1 pcmk-2 ] -[NOTE] -======= -Include output There is a way to force them to move though... -======= + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2 + WebSite (ocf::heartbeat:apache): Started pcmk-2 + +Allocation scores: +native_color: ClusterIP allocation score on pcmk-1: 50 +native_color: ClusterIP allocation score on pcmk-2: 200 +native_color: WebSite allocation score on pcmk-1: -INFINITY +native_color: WebSite allocation score on pcmk-2: 100 + +Transition Summary: +---- == Manually Moving Resources Around the Cluster == There are always times when an administrator needs to override the cluster and force resources to move to a specific location. Underneath we use location constraints like the one we created above, happily you don't need to care. Just provide the name of the resource and the intended location, we'll do the rest. [source,Bash] ----- # crm resource move WebSite pcmk-1 -# crm_mon +# crm_mon -1 ============ -Last updated: Fri Aug 28 16:19:24 2009 -Stack: openais -Current DC: pcmk-2 - partition with quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes +Last updated: Tue Apr 3 12:03:41 2012 +Last change: Tue Apr 3 12:03:37 2012 via crm_resource on pcmk-1 +Stack: corosync +Current DC: pcmk-2 (1719314624) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 2 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] -ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1 -WebSite (ocf::heartbeat:apache): Started pcmk-1 + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1 + WebSite (ocf::heartbeat:apache): Started pcmk-1 ----- Notice how the colocation rule we created has ensured that ClusterIP was also moved to pcmk-1. For the curious, we can see the effect of this command by examining the configuration [source,Bash] ----- # crm configure show -node pcmk-1 -node pcmk-2 -primitive WebSite ocf:heartbeat:apache \ - params configfile="/etc/httpd/conf/httpd.conf" \ - op monitor interval="1min" +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip="192.168.122.101" cidr_netmask="32" \ - op monitor interval="30s" + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" +primitive WebSite ocf:heartbeat:apache \ + params configfile="/etc/httpd/conf/httpd.conf" \ + op monitor interval="1min" location cli-prefer-WebSite WebSite \ - rule $id="cli-prefer-rule-WebSite" inf: #uname eq pcmk-1 + rule $id="cli-prefer-rule-WebSite" inf: #uname eq pcmk-1 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" + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" \ + last-lrm-refresh="1333446866" rsc_defaults $id="rsc-options" \ - resource-stickiness="100" + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" ----- -Highlighted is the automated constraint used to move the resources to -pcmk-1 - +The automated constraint used to move the resources to +pcmk-1+ is the +line beginning with +location cli-prefer-WebSite+. === Giving Control Back to the Cluster === Once we've finished whatever activity that required us to move the resources to pcmk-1, in our case nothing, we can then allow the cluster to resume normal operation with the unmove command. Since we previously configured a default stickiness, the resources will remain on pcmk-1. [source,Bash] ----- # crm resource unmove WebSite # crm configure show -node pcmk-1 -node pcmk-2 -primitive WebSite ocf:heartbeat:apache \ - params configfile="/etc/httpd/conf/httpd.conf" \ - op monitor interval="1min" +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 primitive ClusterIP ocf:heartbeat:IPaddr2 \ - params ip="192.168.122.101" cidr_netmask="32" \ - op monitor interval="30s" + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" +primitive WebSite ocf:heartbeat:apache \ + params configfile="/etc/httpd/conf/httpd.conf" \ + op monitor interval="1min" 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" + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" \ + last-lrm-refresh="1333446866" rsc_defaults $id="rsc-options" \ - resource-stickiness="100" + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" ----- Note that the automated constraint is now gone. If we check the cluster status, we can also see that as expected the resources are still active on pcmk-1. [source,Bash] ----- # crm_mon ============ -Last updated: Fri Aug 28 16:20:53 2009 -Stack: openais -Current DC: pcmk-2 - partition with quorum -Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f -2 Nodes configured, 2 expected votes +Last updated: Tue Apr 3 12:05:08 2012 +Last change: Tue Apr 3 12:03:37 2012 via crm_resource on pcmk-1 +Stack: corosync +Current DC: pcmk-2 (1719314624) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 2 Resources configured. ============ Online: [ pcmk-1 pcmk-2 ] - ClusterIP (ocf::heartbeat:IPaddr): Started pcmk-1 - WebSite (ocf::heartbeat:apache): Started pcmk-1 + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1 + WebSite (ocf::heartbeat:apache): Started pcmk-1 ----- diff --git a/doc/Clusters_from_Scratch/en-US/Ch-Installation.txt b/doc/Clusters_from_Scratch/en-US/Ch-Installation.txt index f33015c677..1502c7f584 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Installation.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Installation.txt @@ -1,754 +1,932 @@ = Installation = == OS Installation == Detailed instructions for installing Fedora are available at -http://docs.fedoraproject.org/install-guide/f13/ in a number of +http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/ in a number of languages. The abbreviated version is as follows... Point your browser to http://fedoraproject.org/en/get-fedora-all, -locate the Install Media section and download the install DVD that +locate the +Install Media+ section and download the install DVD that matches your hardware. Burn the disk image to a DVD -footnote:[http://docs.fedoraproject.org/readme-burning-isos/en-US.html] -and boot from it. Or use the image to boot a virtual machine as I have -done here. After clicking through the welcome screen, select your -language and keyboard layout -footnote:[http://docs.fedoraproject.org/install-guide/f13/en-US/html/s1-langselection-x86.html] +footnote:[http://docs.fedoraproject.org/en-US/Fedora/16/html/Burning_ISO_images_to_disc/index.html] +and boot from it, or use the image to boot a virtual machine. -.Installation: Good choice -image::images/f-13.1-welcome.png["Welcome",align="center"] - -.Fedora Installation - Storage Devices -image::images/f-13.2-devices.png["Storage Devices",align="center"] +After clicking through the welcome screen, select your language, +keyboard layout +footnote:[http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/sn-keyboard-x86.html] +and storage type +footnote:[http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/Storage_Devices-x86.html] Assign your machine a host name. -footnote:[http://docs.fedoraproject.org/install-guide/f13/en-US/html/sn-networkconfig-fedora.html] +footnote:[http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/sn-Netconfig-x86.html] I happen to control the clusterlabs.org domain name, so I will use that here. -.Fedora Installation - Hostname -image::images/f-13.3-hostname.png["Hostname",align="center"] - -You will then be prompted to indicate the machine's physical location -and to supply a root password. -footnote:[http://docs.fedoraproject.org/install-guide/f13/en-US/html/sn-account_configuration.html] - -Now select where you want Fedora installed. -footnote:[http://docs.fedoraproject.org/install-guide/f13/en-US/html/s1-diskpartsetup-x86.html] - -As I don’t care about any existing data, I will accept the default and -allow Fedora to use the complete drive. However I want to reserve some -space for DRBD, so I'll check the Review and modify partitioning -layout box. - -.Fedora Installation - Installation Type -image::images/f-13.4-partition-overview.png["Choose Install Type",align="center"] +[IMPORTANT] +=========== +Do not accept the default network settings. +Cluster machines should never obtain an IP address via DHCP. +Before clicking next, select +Configure Network+ to specify a fixed IPv4 address for +System eth0+. +Here I will use the internal addresses for the clusterlab.org network. -By default, Fedora will give all the space to the / (aka. root) -partition. Wel'll take some back so we can use DRBD. +image::images/Network.png["Custom network settings",align="center"] -.Fedora Installation - Default Partitioning -image::images/f-13.5-partition-default.png["Default Partitioning",align="center"] +Be sure to also enter the +Routes+ section and add an entry for your default gateway. +=========== -The finalized partition layout should look something like the diagram -below. +You will then be prompted to indicate the machine's physical location +footnote:[http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-timezone-x86.html] +and to supply a root password. +footnote:[http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/sn-account_configuration-x86.html] +Now select where you want Fedora installed. +footnote:[http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-diskpartsetup-x86.html] +As I don’t care about any existing data, I will accept the default and +allow Fedora to use the complete drive. [IMPORTANT] =========== -If you plan on following the DRBD or GFS2 portions of this -guide, you should reserve at least 1Gb of space on each machine from -which to create a shared volume. Fedora Installation - Customize -PartitioningFedora Installation: Create a partition to use (later) for -website data -=========== -.Fedora Installation - Customize Partitioning -image::images/f-13.6-partition-custom.png["Customize Partitioning",align="center"] +By default Fedora uses LVM for partitioning which allows us to +dynamically change the amount of space allocated to a given partition. -.Fedora Installation - Bootloader -image::images/f-13.7-bootloader.png["Unless you have a strong reason not to, accept the default bootloader location",align="center"] +However, by default it also allocates all free space to the +/+ +(aka. +root+) partition which cannot be dynamically _reduced_ in size +(dynamic increases are fine by-the-way). +So if you plan on following the DRBD or GFS2 portions of this guide, +you should reserve at least 1Gb of space on each machine from which to +create a shared volume. To do so select the +Review and modify +partitioning layout+ checkbox before clicking +Next+. You will then +be given an opportunity to reduce the size of the +root+ partition. -Next choose which software should be installed. Change the selection to -Web Server since we plan on using Apache. Don't enable updates yet, we'll -do that (and install any extra software we need) later. After you click -next, Fedora will begin installing. +=========== -.Fedora Installation - Software -image::images/f-13.8-software.png["Software selection",align="center"] +Next choose which software should be +installed. footnote:[http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/s1-pkgselection-x86.html] +Change the selection to Minimal so that we see everything that gets +installed. Don't enable updates yet, we'll do that (and install any +extra software we need) later. After you click next, Fedora will begin +installing. Go grab something to drink, this may take a while -.Fedora Installation - Installing -image::images/f-13.9-installing.png["Installing",align="center"] +Once the node reboots, you'll see a (possibly mangled) login prompt on +the console. Login using +root+ and the password you created earlier. -.Fedora Installation - Installation Complete -image::images/f-13.10-install-complete.png["Stage 1, completed",align="center"] +image::images/Console.png["Initial Console",align="center"] +[NOTE] +====== -Once the node reboots, follow the on screen instructions -footnote:[http://docs.fedoraproject.org/install-guide/f13/en-US/html/ch-firstboot.html] -to create a system user and configure the time. +That was the last screenshot, from here on in we're going to be working +exclusively from the terminal. -.Fedora Installation - First Boot -image::images/f-13.11-post-welcome.png["First boot",align="center"] +====== -.Fedora Installation - Create Non-privileged User -image::images/f-13.12-new-user.png["Creating a new user, take note of the password, you'll need it soon",align="center"] +== Post Installation Tasks == +=== Networking === -[NOTE] -======= -It is highly recommended to enable NTP on your cluster nodes. Doing so -ensures all nodes agree on the current time and makes reading log files -significantly easier. Fedora Installation - Date and TimeFedora -Installation: Enable NTP to keep the times on all your nodes consistent -======= +Bring up the network and ensure it starts at boot -.Fedora Installation - Date and Time -image::images/f-13.13-date-time.png["Date and time",align="center"] +[source,Bash] +.... +# service network start +# chkconfig network on +.... -Click through the next screens until you reach the login window. Click on -the user you created and supply the password you indicated earlier. +Check the machine has the static IP address you configured earlier -.Fedora Installation - Customize Networking -image::images/f-13.14-networking.png["Click here to configure networking",align="center"] +[source,Bash] +.... +# ip addr +1: lo: mtu 16436 qdisc noqueue state UNKNOWN + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo + inet6 ::1/128 scope host + valid_lft forever preferred_lft forever +2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 + link/ether 52:54:00:d7:d6:08 brd ff:ff:ff:ff:ff:ff + inet 192.168.122.101/24 brd 192.168.122.255 scope global eth0 + inet6 fe80::5054:ff:fed7:d608/64 scope link + valid_lft forever preferred_lft forever +.... -[IMPORTANT] -=========== -Do not accept the default network settings. Cluster -machines should never obtain an ip address via DHCP. Here I will use -the internal addresses for the clusterlab.org network. -=========== +Now check the default route setting: + +[source,Bash] +.... +[root@pcmk-1 ~]# ip route +default via 192.168.122.1 dev eth0 +192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.101 +.... -.Fedora Installation - Specify Network Preferences -image::images/f-13.15-manual-networking.png["Specify network settings for your machine, never choose DHCP",align="center"] +If there is no line beginning with +default via+, then you may need to add a line such as -.Fedora Installation - Activate Networking -image::images/f-13.16-networking-activate.png["Click the big green button to activate your changes",align="center"] + GATEWAY=192.168.122.1 -.Fedora Installation - Bring up the Terminal -image::images/f-13.17-terminal.png["Down to business, fire up the command line",align="center"] +to '/etc/sysconfig/network' and restart the network. +Now check for connectivity to the outside world. Start small by +testing if we can read the gateway we configured. + +[source,Bash] +.... +# ping -c 1 192.168.122.1 +PING 192.168.122.1 (192.168.122.1) 56(84) bytes of data. +64 bytes from 192.168.122.1: icmp_req=1 ttl=64 time=0.249 ms -[NOTE] -====== +--- 192.168.122.1 ping statistics --- +1 packets transmitted, 1 received, 0% packet loss, time 0ms +rtt min/avg/max/mdev = 0.249/0.249/0.249/0.000 ms +.... -That was the last screenshot, from here on in we’re going to be working -from the terminal. +Now try something external, choose a location you know will be available. -====== +[source,Bash] +.... +# ping -c 1 www.google.com +PING www.l.google.com (173.194.72.106) 56(84) bytes of data. +64 bytes from tf-in-f106.1e100.net (173.194.72.106): icmp_req=1 ttl=41 time=167 ms -== Cluster Software Installation == +--- www.l.google.com ping statistics --- +1 packets transmitted, 1 received, 0% packet loss, time 0ms +rtt min/avg/max/mdev = 167.618/167.618/167.618/0.000 ms +.... -Go to the terminal window you just opened and switch to the super user -(aka. "root") account with the su command. You will need to supply the -password you entered earlier during the installation process. +=== Leaving the Console === +The console isn't a very friendly place to work from, we will now +switch to accessing the machine remotely via SSH where we can +use copy&paste etc. -[source,Bash] ----- -[beekhof@pcmk-1 ~]$ su - -Password: -[root@pcmk-1 ~]# ----- +First we check we can see the newly installed at all: -[NOTE] -====== +[source,Bash] +.... +beekhof@f16 ~ # ping -c 1 192.168.122.101 +PING 192.168.122.101 (192.168.122.101) 56(84) bytes of data. +64 bytes from 192.168.122.101: icmp_req=1 ttl=64 time=1.01 ms -Note that the username (the text before the @ symbol) now indicates we’re -running as the super user “root”. +--- 192.168.122.101 ping statistics --- +1 packets transmitted, 1 received, 0% packet loss, time 0ms +rtt min/avg/max/mdev = 1.012/1.012/1.012/0.000 ms +.... -====== +Next we login via SSH [source,Bash] .... -# ip addr -1: lo: mtu 16436 qdisc noqueue state UNKNOWN - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo - inet6 ::1/128 scope host - valid_lft forever preferred_lft forever -2: eth0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 - link/ether 00:0c:29:6f:e1:58 brd ff:ff:ff:ff:ff:ff - inet 192.168.9.41/24 brd 192.168.9.255 scope global eth0 - inet6 ::20c:29ff:fe6f:e158/64 scope global dynamic - valid_lft 2591667sec preferred_lft 604467sec - inet6 2002:57ae:43fc:0:20c:29ff:fe6f:e158/64 scope global dynamic - valid_lft 2591990sec preferred_lft 604790sec - inet6 fe80::20c:29ff:fe6f:e158/64 scope link - valid_lft forever preferred_lft forever -# ping -c 1 www.google.com -PING www.l.google.com (74.125.39.99) 56(84) bytes of data. -64 bytes from fx-in-f99.1e100.net (74.125.39.99): icmp_seq=1 ttl=56 time=16.7 ms - ---- www.l.google.com ping statistics --- -1 packets transmitted, 1 received, 0% packet loss, time 20ms -rtt min/avg/max/mdev = 16.713/16.713/16.713/0.000 ms -# /sbin/chkconfig network on -# +beekhof@f16 ~ # ssh -l root 192.168.122.11 +root@192.168.122.11's password: +Last login: Fri Mar 30 19:41:19 2012 from 192.168.122.1 +[root@pcmk-1 ~]# .... === Security Shortcuts === To simplify this guide and focus on the aspects directly connected to -clustering, we will now disable the machine’s firewall and SELinux -installation. Both of these actions create significant security issues +clustering, we will now disable the machine's firewall and SELinux +installation. + +[WARNING] +=========== +Both of these actions create significant security issues and should not be performed on machines that will be exposed to the outside world. - +=========== [IMPORTANT] =========== TODO: Create an Appendix that deals with (at least) re-enabling the firewall. =========== [source,Bash] ---- +# setenforce 0 # sed -i.bak "s/SELINUX=enforcing/SELINUX=permissive/g" /etc/selinux/config -# /sbin/chkconfig --del iptables -# service iptables stop -iptables: Flushing firewall rules: [ OK ] -iptables: Setting chains to policy ACCEPT: filter [ OK ] -iptables: Unloading modules: [ OK ] +# systemctl disable iptables.service +rm '/etc/systemd/system/basic.target.wants/iptables.service' +# systemctl stop iptables.service ---- -[NOTE] -================ - -You will need to reboot for the SELinux changes to take effect. Otherwise -you will see something like this when you start corosync: +=== Short Node Names === - May 4 19:30:54 pcmk-1 setroubleshoot: SELinux is preventing /usr/sbin/corosync "getattr" access on /. For complete SELinux messages. run sealert -l 6e0d4384-638e-4d55-9aaf-7dac011f29c1 - May 4 19:30:54 pcmk-1 setroubleshoot: SELinux is preventing /usr/sbin/corosync "getattr" access on /. For complete SELinux messages. run sealert -l 6e0d4384-638e-4d55-9aaf-7dac011f29c1 -================ +During installation, we filled in the machine's fully qualifier domain +name (FQDN) which can be rather long when it appears in cluster logs and +status output. See for yourself how the machine identifies itself: +(((Nodes, short name))) +[source,Bash] +---- +# uname -n +pcmk-1.clusterlabs.org +# dnsdomainname +clusterlabs.org +---- +(((Nodes, Domain name (Query)))) -=== Install the Cluster Software === +The output from the second command is fine, but we really don't need the +domain name included in the basic host details. To address this, we need +to update /etc/sysconfig/network. This is what it should look like before +we start. -Since version 12, Fedora comes with recent versions of everything you -need, so simply fire up the shell and run: +[source,Bash] +---- +# cat /etc/sysconfig/network +NETWORKING=yes +HOSTNAME=pcmk-1.clusterlabs.org +GATEWAY=192.168.122.1 +---- -.... -# sed -i.bak "s/enabled=0/enabled=1/g" -/etc/yum.repos.d/fedora.repo -# sed -i.bak "s/enabled=0/enabled=1/g" -/etc/yum.repos.d/fedora-updates.repo -# yum install -y pacemaker corosyncLoaded plugins: presto, refresh-packagekit -fedora/metalink | 22 kB 00:00 -fedora-debuginfo/metalink | 16 kB 00:00 -fedora-debuginfo | 3.2 kB 00:00 -fedora-debuginfo/primary_db | 1.4 MB 00:04 -fedora-source/metalink | 22 kB 00:00 -fedora-source | 3.2 kB 00:00 -fedora-source/primary_db | 3.0 MB 00:05 -updates/metalink | 26 kB 00:00 -updates | 2.6 kB 00:00 -updates/primary_db | 1.1 kB 00:00 -updates-debuginfo/metalink | 18 kB 00:00 -updates-debuginfo | 2.6 kB 00:00 -updates-debuginfo/primary_db | 1.1 kB 00:00 -updates-source/metalink | 25 kB 00:00 -updates-source | 2.6 kB 00:00 -updates-source/primary_db | 1.1 kB 00:00 -Setting up Install Process -Resolving Dependencies ---> Running transaction check ----> Package corosync.x86_64 0:1.2.1-1.fc13 set to be updated ---> Processing Dependency: corosynclib = 1.2.1-1.fc13 for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libquorum.so.4(COROSYNC_QUORUM_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libvotequorum.so.4(COROSYNC_VOTEQUORUM_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libcpg.so.4(COROSYNC_CPG_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libconfdb.so.4(COROSYNC_CONFDB_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libcfg.so.4(COROSYNC_CFG_0.82)(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libpload.so.4(COROSYNC_PLOAD_1.0)(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: liblogsys.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libconfdb.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libcoroipcc.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libcpg.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libquorum.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libcoroipcs.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libvotequorum.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libcfg.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libtotem_pg.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libpload.so.4()(64bit) for package: corosync-1.2.1-1.fc13.x86_64 ----> Package pacemaker.x86_64 0:1.1.5-1.fc13 set to be updated ---> Processing Dependency: heartbeat >= 3.0.0 for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: net-snmp >= 5.4 for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: resource-agents for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: cluster-glue for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libnetsnmp.so.20()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libcrmcluster.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libpengine.so.3()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libnetsnmpagent.so.20()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libesmtp.so.5()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libstonithd.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libhbclient.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libpils.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libpe_status.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libnetsnmpmibs.so.20()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libnetsnmphelpers.so.20()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libcib.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libccmclient.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libstonith.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: liblrm.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libtransitioner.so.1()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libpe_rules.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libcrmcommon.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Processing Dependency: libplumb.so.2()(64bit) for package: pacemaker-1.1.5-1.fc13.x86_64 ---> Running transaction check ----> Package cluster-glue.x86_64 0:1.0.2-1.fc13 set to be updated ---> Processing Dependency: perl-TimeDate for package: cluster-glue-1.0.2-1.fc13.x86_64 ---> Processing Dependency: libOpenIPMIutils.so.0()(64bit) for package: cluster-glue-1.0.2-1.fc13.x86_64 ---> Processing Dependency: libOpenIPMIposix.so.0()(64bit) for package: cluster-glue-1.0.2-1.fc13.x86_64 ---> Processing Dependency: libopenhpi.so.2()(64bit) for package: cluster-glue-1.0.2-1.fc13.x86_64 ---> Processing Dependency: libOpenIPMI.so.0()(64bit) for package: cluster-glue-1.0.2-1.fc13.x86_64 ----> Package cluster-glue-libs.x86_64 0:1.0.2-1.fc13 set to be updated ----> Package corosynclib.x86_64 0:1.2.1-1.fc13 set to be updated ---> Processing Dependency: librdmacm.so.1(RDMACM_1.0)(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libibverbs.so.1(IBVERBS_1.0)(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libibverbs.so.1(IBVERBS_1.1)(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64 ---> Processing Dependency: libibverbs.so.1()(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64 ---> Processing Dependency: librdmacm.so.1()(64bit) for package: corosynclib-1.2.1-1.fc13.x86_64 ----> Package heartbeat.x86_64 0:3.0.0-0.7.0daab7da36a8.hg.fc13 set to be updated ---> Processing Dependency: PyXML for package: heartbeat-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64 ----> Package heartbeat-libs.x86_64 0:3.0.0-0.7.0daab7da36a8.hg.fc13 set to be updated ----> Package libesmtp.x86_64 0:1.0.4-12.fc12 set to be updated ----> Package net-snmp.x86_64 1:5.5-12.fc13 set to be updated ---> Processing Dependency: libsensors.so.4()(64bit) for package: 1:net-snmp-5.5-12.fc13.x86_64 ----> Package net-snmp-libs.x86_64 1:5.5-12.fc13 set to be updated ----> Package pacemaker-libs.x86_64 0:1.1.5-1.fc13 set to be updated ----> Package resource-agents.x86_64 0:3.0.10-1.fc13 set to be updated ---> Processing Dependency: libnet.so.1()(64bit) for package: resource-agents-3.0.10-1.fc13.x86_64 ---> Running transaction check ----> Package OpenIPMI-libs.x86_64 0:2.0.16-8.fc13 set to be updated ----> Package PyXML.x86_64 0:0.8.4-17.fc13 set to be updated ----> Package libibverbs.x86_64 0:1.1.3-4.fc13 set to be updated ---> Processing Dependency: libibverbs-driver for package: libibverbs-1.1.3-4.fc13.x86_64 ----> Package libnet.x86_64 0:1.1.4-3.fc12 set to be updated ----> Package librdmacm.x86_64 0:1.0.10-2.fc13 set to be updated ----> Package lm_sensors-libs.x86_64 0:3.1.2-2.fc13 set to be updated ----> Package openhpi-libs.x86_64 0:2.14.1-3.fc13 set to be updated ----> Package perl-TimeDate.noarch 1:1.20-1.fc13 set to be updated ---> Running transaction check ----> Package libmlx4.x86_64 0:1.0.1-5.fc13 set to be updated ---> Finished Dependency Resolution +All we need to do now is strip off the domain name portion, which is +stored elsewhere anyway. -Dependencies Resolved +[source,Bash] +---- + # sed -i.sed 's/\.[a-z].*//g' /etc/sysconfig/network +---- +Now confirm the change was successful. The revised file contents should +look something like this. -========================================================================================== - Package Arch Version Repository Size -========================================================================================== -Installing: - corosync x86_64 1.2.1-1.fc13 fedora 136 k - pacemaker x86_64 1.1.5-1.fc13 fedora 543 k -Installing for dependencies: - OpenIPMI-libs x86_64 2.0.16-8.fc13 fedora 474 k - PyXML x86_64 0.8.4-17.fc13 fedora 906 k - cluster-glue x86_64 1.0.2-1.fc13 fedora 230 k - cluster-glue-libs x86_64 1.0.2-1.fc13 fedora 116 k - corosynclib x86_64 1.2.1-1.fc13 fedora 145 k - heartbeat x86_64 3.0.0-0.7.0daab7da36a8.hg.fc13 updates 172 k - heartbeat-libs x86_64 3.0.0-0.7.0daab7da36a8.hg.fc13 updates 265 k - libesmtp x86_64 1.0.4-12.fc12 fedora 54 k - libibverbs x86_64 1.1.3-4.fc13 fedora 42 k - libmlx4 x86_64 1.0.1-5.fc13 fedora 27 k - libnet x86_64 1.1.4-3.fc12 fedora 49 k - librdmacm x86_64 1.0.10-2.fc13 fedora 22 k - lm_sensors-libs x86_64 3.1.2-2.fc13 fedora 37 k - net-snmp x86_64 1:5.5-12.fc13 fedora 295 k - net-snmp-libs x86_64 1:5.5-12.fc13 fedora 1.5 M - openhpi-libs x86_64 2.14.1-3.fc13 fedora 135 k - pacemaker-libs x86_64 1.1.5-1.fc13 fedora 264 k - perl-TimeDate noarch 1:1.20-1.fc13 fedora 42 k - resource-agents x86_64 3.0.10-1.fc13 fedora 357 k +[source,Bash] +---- +# cat /etc/sysconfig/network +NETWORKING=yes +HOSTNAME=pcmk-1 +GATEWAY=192.168.122.1 +---- -Transaction Summary -========================================================================================= -Install 21 Package(s) -Upgrade 0 Package(s) +However we're not finished. The machine wont normally see the shortened +host name until about it reboots, but we can force it to update. -Total download size: 5.7 M -Installed size: 20 M -Downloading Packages: -Setting up and reading Presto delta metadata -updates-testing/prestodelta | 164 kB 00:00 -fedora/prestodelta | 150 B 00:00 -Processing delta metadata -Package(s) data still to download: 5.7 M -(1/21): OpenIPMI-libs-2.0.16-8.fc13.x86_64.rpm | 474 kB 00:00 -(2/21): PyXML-0.8.4-17.fc13.x86_64.rpm | 906 kB 00:01 -(3/21): cluster-glue-1.0.2-1.fc13.x86_64.rpm | 230 kB 00:00 -(4/21): cluster-glue-libs-1.0.2-1.fc13.x86_64.rpm | 116 kB 00:00 -(5/21): corosync-1.2.1-1.fc13.x86_64.rpm | 136 kB 00:00 -(6/21): corosynclib-1.2.1-1.fc13.x86_64.rpm | 145 kB 00:00 -(7/21): heartbeat-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64.rpm | 172 kB 00:00 -(8/21): heartbeat-libs-3.0.0-0.7.0daab7da36a8.hg.fc13.x86_64.rpm | 265 kB 00:00 -(9/21): libesmtp-1.0.4-12.fc12.x86_64.rpm | 54 kB 00:00 -(10/21): libibverbs-1.1.3-4.fc13.x86_64.rpm | 42 kB 00:00 -(11/21): libmlx4-1.0.1-5.fc13.x86_64.rpm | 27 kB 00:00 -(12/21): libnet-1.1.4-3.fc12.x86_64.rpm | 49 kB 00:00 -(13/21): librdmacm-1.0.10-2.fc13.x86_64.rpm | 22 kB 00:00 -(14/21): lm_sensors-libs-3.1.2-2.fc13.x86_64.rpm | 37 kB 00:00 -(15/21): net-snmp-5.5-12.fc13.x86_64.rpm | 295 kB 00:00 -(16/21): net-snmp-libs-5.5-12.fc13.x86_64.rpm | 1.5 MB 00:01 -(17/21): openhpi-libs-2.14.1-3.fc13.x86_64.rpm | 135 kB 00:00 -(18/21): pacemaker-1.1.5-1.fc13.x86_64.rpm | 543 kB 00:00 -(19/21): pacemaker-libs-1.1.5-1.fc13.x86_64.rpm | 264 kB 00:00 -(20/21): perl-TimeDate-1.20-1.fc13.noarch.rpm | 42 kB 00:00 -(21/21): resource-agents-3.0.10-1.fc13.x86_64.rpm | 357 kB 00:00 - -Total 539 kB/s | 5.7 MB 00:10 -warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID e8e40fde: NOKEY -fedora/gpgkey | 3.2 kB 00:00 ... -Importing GPG key 0xE8E40FDE "Fedora (13) Running transaction check +---> Package corosync.x86_64 0:1.99.9-1.fc17 will be installed +--> Processing Dependency: corosynclib = 1.99.9-1.fc17 for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libxslt for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libvotequorum.so.5(COROSYNC_VOTEQUORUM_1.0)(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libquorum.so.5(COROSYNC_QUORUM_1.0)(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libcpg.so.4(COROSYNC_CPG_1.0)(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libcmap.so.4(COROSYNC_CMAP_1.0)(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libcfg.so.6(COROSYNC_CFG_0.82)(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libvotequorum.so.5()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libtotem_pg.so.5()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libquorum.so.5()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libqb.so.0()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libnetsnmp.so.30()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libcpg.so.4()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libcorosync_common.so.4()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libcmap.so.4()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libcfg.so.6()(64bit) for package: corosync-1.99.9-1.fc17.x86_64 +---> Package pacemaker.x86_64 0:1.1.7-2.fc17 will be installed +--> Processing Dependency: pacemaker-libs = 1.1.7-2.fc17 for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: pacemaker-cluster-libs = 1.1.7-2.fc17 for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: pacemaker-cli = 1.1.7-2.fc17 for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: resource-agents for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: perl(Getopt::Long) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: cluster-glue for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: /usr/bin/perl for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libtransitioner.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libstonithd.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libstonith.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libplumb.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libpils.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libpengine.so.3()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libpe_status.so.3()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libpe_rules.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libltdl.so.7()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: liblrm.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libgnutls.so.26()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libcrmcommon.so.2()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libcrmcluster.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Processing Dependency: libcib.so.1()(64bit) for package: pacemaker-1.1.7-2.fc17.x86_64 +--> Running transaction check +---> Package cluster-glue.x86_64 0:1.0.6-9.fc17.1 will be installed +--> Processing Dependency: perl-TimeDate for package: cluster-glue-1.0.6-9.fc17.1.x86_64 +--> Processing Dependency: libOpenIPMIutils.so.0()(64bit) for package: cluster-glue-1.0.6-9.fc17.1.x86_64 +--> Processing Dependency: libOpenIPMIposix.so.0()(64bit) for package: cluster-glue-1.0.6-9.fc17.1.x86_64 +--> Processing Dependency: libOpenIPMI.so.0()(64bit) for package: cluster-glue-1.0.6-9.fc17.1.x86_64 +---> Package cluster-glue-libs.x86_64 0:1.0.6-9.fc17.1 will be installed +---> Package corosynclib.x86_64 0:1.99.9-1.fc17 will be installed +--> Processing Dependency: librdmacm.so.1(RDMACM_1.0)(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libibverbs.so.1(IBVERBS_1.1)(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libibverbs.so.1(IBVERBS_1.0)(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64 +--> Processing Dependency: librdmacm.so.1()(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64 +--> Processing Dependency: libibverbs.so.1()(64bit) for package: corosynclib-1.99.9-1.fc17.x86_64 +---> Package gnutls.x86_64 0:2.12.17-1.fc17 will be installed +--> Processing Dependency: libtasn1.so.3(LIBTASN1_0_3)(64bit) for package: gnutls-2.12.17-1.fc17.x86_64 +--> Processing Dependency: libtasn1.so.3()(64bit) for package: gnutls-2.12.17-1.fc17.x86_64 +--> Processing Dependency: libp11-kit.so.0()(64bit) for package: gnutls-2.12.17-1.fc17.x86_64 +---> Package libqb.x86_64 0:0.11.1-1.fc17 will be installed +---> Package libtool-ltdl.x86_64 0:2.4.2-3.fc17 will be installed +---> Package libxslt.x86_64 0:1.1.26-9.fc17 will be installed +---> Package net-snmp-libs.x86_64 1:5.7.1-4.fc17 will be installed +---> Package pacemaker-cli.x86_64 0:1.1.7-2.fc17 will be installed +---> Package pacemaker-cluster-libs.x86_64 0:1.1.7-2.fc17 will be installed +---> Package pacemaker-libs.x86_64 0:1.1.7-2.fc17 will be installed +---> Package perl.x86_64 4:5.14.2-211.fc17 will be installed +--> Processing Dependency: perl-libs = 4:5.14.2-211.fc17 for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(threads::shared) >= 1.21 for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(Socket) >= 1.3 for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(Scalar::Util) >= 1.10 for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(File::Spec) >= 0.8 for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl-macros for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl-libs for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(threads::shared) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(threads) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(Socket) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(Scalar::Util) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(Pod::Simple) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(Module::Pluggable) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(List::Util) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(File::Spec::Unix) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(File::Spec::Functions) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(File::Spec) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(Cwd) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: perl(Carp) for package: 4:perl-5.14.2-211.fc17.x86_64 +--> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.14.2-211.fc17.x86_64 +---> Package resource-agents.x86_64 0:3.9.2-2.fc17.1 will be installed +--> Processing Dependency: /usr/sbin/rpc.nfsd for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /usr/sbin/rpc.mountd for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /usr/sbin/ethtool for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /sbin/rpc.statd for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /sbin/quotaon for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /sbin/quotacheck for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /sbin/mount.nfs4 for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /sbin/mount.nfs for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /sbin/mount.cifs for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: /sbin/fsck.xfs for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Processing Dependency: libnet.so.1()(64bit) for package: resource-agents-3.9.2-2.fc17.1.x86_64 +--> Running transaction check +---> Package OpenIPMI-libs.x86_64 0:2.0.18-13.fc17 will be installed +---> Package cifs-utils.x86_64 0:5.3-2.fc17 will be installed +--> Processing Dependency: libtalloc.so.2(TALLOC_2.0.2)(64bit) for package: cifs-utils-5.3-2.fc17.x86_64 +--> Processing Dependency: keyutils for package: cifs-utils-5.3-2.fc17.x86_64 +--> Processing Dependency: libwbclient.so.0()(64bit) for package: cifs-utils-5.3-2.fc17.x86_64 +--> Processing Dependency: libtalloc.so.2()(64bit) for package: cifs-utils-5.3-2.fc17.x86_64 +---> Package ethtool.x86_64 2:3.2-2.fc17 will be installed +---> Package libibverbs.x86_64 0:1.1.6-2.fc17 will be installed +---> Package libnet.x86_64 0:1.1.5-3.fc17 will be installed +---> Package librdmacm.x86_64 0:1.0.15-1.fc17 will be installed +---> Package libtasn1.x86_64 0:2.12-1.fc17 will be installed +---> Package nfs-utils.x86_64 1:1.2.5-12.fc17 will be installed +--> Processing Dependency: rpcbind for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libtirpc for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libnfsidmap for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libgssglue.so.1(libgssapi_CITI_2)(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libgssglue for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libevent for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libtirpc.so.1()(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libnfsidmap.so.0()(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libgssglue.so.1()(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +--> Processing Dependency: libevent-2.0.so.5()(64bit) for package: 1:nfs-utils-1.2.5-12.fc17.x86_64 +---> Package p11-kit.x86_64 0:0.12-1.fc17 will be installed +---> Package perl-Carp.noarch 0:1.22-2.fc17 will be installed +---> Package perl-Module-Pluggable.noarch 1:3.90-211.fc17 will be installed +---> Package perl-PathTools.x86_64 0:3.33-211.fc17 will be installed +---> Package perl-Pod-Simple.noarch 1:3.16-211.fc17 will be installed +--> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.16-211.fc17.noarch +---> Package perl-Scalar-List-Utils.x86_64 0:1.25-1.fc17 will be installed +---> Package perl-Socket.x86_64 0:2.001-1.fc17 will be installed +---> Package perl-TimeDate.noarch 1:1.20-6.fc17 will be installed +---> Package perl-libs.x86_64 4:5.14.2-211.fc17 will be installed +---> Package perl-macros.x86_64 4:5.14.2-211.fc17 will be installed +---> Package perl-threads.x86_64 0:1.86-2.fc17 will be installed +---> Package perl-threads-shared.x86_64 0:1.40-2.fc17 will be installed +---> Package quota.x86_64 1:4.00-3.fc17 will be installed +--> Processing Dependency: quota-nls = 1:4.00-3.fc17 for package: 1:quota-4.00-3.fc17.x86_64 +--> Processing Dependency: tcp_wrappers for package: 1:quota-4.00-3.fc17.x86_64 +---> Package xfsprogs.x86_64 0:3.1.8-1.fc17 will be installed +--> Running transaction check +---> Package keyutils.x86_64 0:1.5.5-2.fc17 will be installed +---> Package libevent.x86_64 0:2.0.14-2.fc17 will be installed +---> Package libgssglue.x86_64 0:0.3-1.fc17 will be installed +---> Package libnfsidmap.x86_64 0:0.25-1.fc17 will be installed +---> Package libtalloc.x86_64 0:2.0.7-4.fc17 will be installed +---> Package libtirpc.x86_64 0:0.2.2-2.1.fc17 will be installed +---> Package libwbclient.x86_64 1:3.6.3-81.fc17.1 will be installed +---> Package perl-Pod-Escapes.noarch 1:1.04-211.fc17 will be installed +---> Package quota-nls.noarch 1:4.00-3.fc17 will be installed +---> Package rpcbind.x86_64 0:0.2.0-16.fc17 will be installed +---> Package tcp_wrappers.x86_64 0:7.6-69.fc17 will be installed +--> Finished Dependency Resolution -[source,Bash] ----- - # sed -i.bak 's/\.[a-z].*//g' /etc/sysconfig/network ----- +Dependencies Resolved -Now confirm the change was successful. The revised file contents should -look something like this. + ============================================================================================== + Package Arch Version Repository Size +===================================================================================== +Installing: + corosync x86_64 1.99.9-1.fc17 updates-testing 159 k + pacemaker x86_64 1.1.7-2.fc17 updates-testing 362 k +Installing for dependencies: + OpenIPMI-libs x86_64 2.0.18-13.fc17 fedora 466 k + cifs-utils x86_64 5.3-2.fc17 updates-testing 66 k + cluster-glue x86_64 1.0.6-9.fc17.1 fedora 229 k + cluster-glue-libs x86_64 1.0.6-9.fc17.1 fedora 121 k + corosynclib x86_64 1.99.9-1.fc17 updates-testing 96 k + ethtool x86_64 2:3.2-2.fc17 fedora 94 k + gnutls x86_64 2.12.17-1.fc17 fedora 385 k + keyutils x86_64 1.5.5-2.fc17 fedora 49 k + libevent x86_64 2.0.14-2.fc17 fedora 160 k + libgssglue x86_64 0.3-1.fc17 fedora 24 k + libibverbs x86_64 1.1.6-2.fc17 fedora 44 k + libnet x86_64 1.1.5-3.fc17 fedora 54 k + libnfsidmap x86_64 0.25-1.fc17 fedora 34 k + libqb x86_64 0.11.1-1.fc17 updates-testing 68 k + librdmacm x86_64 1.0.15-1.fc17 fedora 27 k + libtalloc x86_64 2.0.7-4.fc17 fedora 22 k + libtasn1 x86_64 2.12-1.fc17 updates-testing 319 k + libtirpc x86_64 0.2.2-2.1.fc17 fedora 78 k + libtool-ltdl x86_64 2.4.2-3.fc17 fedora 45 k + libwbclient x86_64 1:3.6.3-81.fc17.1 updates-testing 68 k + libxslt x86_64 1.1.26-9.fc17 fedora 416 k + net-snmp-libs x86_64 1:5.7.1-4.fc17 fedora 713 k + nfs-utils x86_64 1:1.2.5-12.fc17 fedora 311 k + p11-kit x86_64 0.12-1.fc17 updates-testing 36 k + pacemaker-cli x86_64 1.1.7-2.fc17 updates-testing 368 k + pacemaker-cluster-libs x86_64 1.1.7-2.fc17 updates-testing 77 k + pacemaker-libs x86_64 1.1.7-2.fc17 updates-testing 322 k + perl x86_64 4:5.14.2-211.fc17 fedora 10 M + perl-Carp noarch 1.22-2.fc17 fedora 17 k + perl-Module-Pluggable noarch 1:3.90-211.fc17 fedora 47 k + perl-PathTools x86_64 3.33-211.fc17 fedora 105 k + perl-Pod-Escapes noarch 1:1.04-211.fc17 fedora 40 k + perl-Pod-Simple noarch 1:3.16-211.fc17 fedora 223 k + perl-Scalar-List-Utils x86_64 1.25-1.fc17 updates-testing 33 k + perl-Socket x86_64 2.001-1.fc17 updates-testing 44 k + perl-TimeDate noarch 1:1.20-6.fc17 fedora 43 k + perl-libs x86_64 4:5.14.2-211.fc17 fedora 628 k + perl-macros x86_64 4:5.14.2-211.fc17 fedora 32 k + perl-threads x86_64 1.86-2.fc17 fedora 47 k + perl-threads-shared x86_64 1.40-2.fc17 fedora 36 k + quota x86_64 1:4.00-3.fc17 fedora 160 k + quota-nls noarch 1:4.00-3.fc17 fedora 74 k + resource-agents x86_64 3.9.2-2.fc17.1 fedora 466 k + rpcbind x86_64 0.2.0-16.fc17 fedora 52 k + tcp_wrappers x86_64 7.6-69.fc17 fedora 72 k + xfsprogs x86_64 3.1.8-1.fc17 updates-testing 715 k -[source,Bash] ----- -# cat /etc/sysconfig/network -NETWORKING=yes -HOSTNAME=pcmk-1 -GATEWAY=192.168.122.1 ----- +Transaction Summary +===================================================================================== +Install 2 Packages (+46 Dependent packages) -However we’re not finished. The machine wont normally see the shortened -host name until about it reboots, but we can force it to update. +Total download size: 18 M +Installed size: 59 M +Downloading Packages: +(1/48): OpenIPMI-libs-2.0.18-13.fc17.x86_64.rpm | 466 kB 00:00 +warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 1aca3465: NOKEY +Public key for OpenIPMI-libs-2.0.18-13.fc17.x86_64.rpm is not installed +(2/48): cifs-utils-5.3-2.fc17.x86_64.rpm | 66 kB 00:01 +Public key for cifs-utils-5.3-2.fc17.x86_64.rpm is not installed +(3/48): cluster-glue-1.0.6-9.fc17.1.x86_64.rpm | 229 kB 00:00 +(4/48): cluster-glue-libs-1.0.6-9.fc17.1.x86_64.rpm | 121 kB 00:00 +(5/48): corosync-1.99.9-1.fc17.x86_64.rpm | 159 kB 00:01 +(6/48): corosynclib-1.99.9-1.fc17.x86_64.rpm | 96 kB 00:00 +(7/48): ethtool-3.2-2.fc17.x86_64.rpm | 94 kB 00:00 +(8/48): gnutls-2.12.17-1.fc17.x86_64.rpm | 385 kB 00:00 +(9/48): keyutils-1.5.5-2.fc17.x86_64.rpm | 49 kB 00:00 +(10/48): libevent-2.0.14-2.fc17.x86_64.rpm | 160 kB 00:00 +(11/48): libgssglue-0.3-1.fc17.x86_64.rpm | 24 kB 00:00 +(12/48): libibverbs-1.1.6-2.fc17.x86_64.rpm | 44 kB 00:00 +(13/48): libnet-1.1.5-3.fc17.x86_64.rpm | 54 kB 00:00 +(14/48): libnfsidmap-0.25-1.fc17.x86_64.rpm | 34 kB 00:00 +(15/48): libqb-0.11.1-1.fc17.x86_64.rpm | 68 kB 00:01 +(16/48): librdmacm-1.0.15-1.fc17.x86_64.rpm | 27 kB 00:00 +(17/48): libtalloc-2.0.7-4.fc17.x86_64.rpm | 22 kB 00:00 +(18/48): libtasn1-2.12-1.fc17.x86_64.rpm | 319 kB 00:02 +(19/48): libtirpc-0.2.2-2.1.fc17.x86_64.rpm | 78 kB 00:00 +(20/48): libtool-ltdl-2.4.2-3.fc17.x86_64.rpm | 45 kB 00:00 +(21/48): libwbclient-3.6.3-81.fc17.1.x86_64.rpm | 68 kB 00:00 +(22/48): libxslt-1.1.26-9.fc17.x86_64.rpm | 416 kB 00:00 +(23/48): net-snmp-libs-5.7.1-4.fc17.x86_64.rpm | 713 kB 00:01 +(24/48): nfs-utils-1.2.5-12.fc17.x86_64.rpm | 311 kB 00:00 +(25/48): p11-kit-0.12-1.fc17.x86_64.rpm | 36 kB 00:01 +(26/48): pacemaker-1.1.7-2.fc17.x86_64.rpm | 362 kB 00:02 +(27/48): pacemaker-cli-1.1.7-2.fc17.x86_64.rpm | 368 kB 00:02 +(28/48): pacemaker-cluster-libs-1.1.7-2.fc17.x86_64.rpm | 77 kB 00:00 +(29/48): pacemaker-libs-1.1.7-2.fc17.x86_64.rpm | 322 kB 00:01 +(30/48): perl-5.14.2-211.fc17.x86_64.rpm | 10 MB 00:15 +(31/48): perl-Carp-1.22-2.fc17.noarch.rpm | 17 kB 00:00 +(32/48): perl-Module-Pluggable-3.90-211.fc17.noarch.rpm | 47 kB 00:00 +(33/48): perl-PathTools-3.33-211.fc17.x86_64.rpm | 105 kB 00:00 +(34/48): perl-Pod-Escapes-1.04-211.fc17.noarch.rpm | 40 kB 00:00 +(35/48): perl-Pod-Simple-3.16-211.fc17.noarch.rpm | 223 kB 00:00 +(36/48): perl-Scalar-List-Utils-1.25-1.fc17.x86_64.rpm | 33 kB 00:01 +(37/48): perl-Socket-2.001-1.fc17.x86_64.rpm | 44 kB 00:00 +(38/48): perl-TimeDate-1.20-6.fc17.noarch.rpm | 43 kB 00:00 +(39/48): perl-libs-5.14.2-211.fc17.x86_64.rpm | 628 kB 00:00 +(40/48): perl-macros-5.14.2-211.fc17.x86_64.rpm | 32 kB 00:00 +(41/48): perl-threads-1.86-2.fc17.x86_64.rpm | 47 kB 00:00 +(42/48): perl-threads-shared-1.40-2.fc17.x86_64.rpm | 36 kB 00:00 +(43/48): quota-4.00-3.fc17.x86_64.rpm | 160 kB 00:00 +(44/48): quota-nls-4.00-3.fc17.noarch.rpm | 74 kB 00:00 +(45/48): resource-agents-3.9.2-2.fc17.1.x86_64.rpm | 466 kB 00:00 +(46/48): rpcbind-0.2.0-16.fc17.x86_64.rpm | 52 kB 00:00 +(47/48): tcp_wrappers-7.6-69.fc17.x86_64.rpm | 72 kB 00:00 +(48/48): xfsprogs-3.1.8-1.fc17.x86_64.rpm | 715 kB 00:03 + --------------------------------------------------------------------------------------- +Total 333 kB/s | 18 MB 00:55 +Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64 +Importing GPG key 0x1ACA3465: + Userid : "Fedora (17) " + Fingerprint: cac4 3fb7 74a4 a673 d81c 5de7 50e9 4c99 1aca 3465 + Package : fedora-release-17-0.8.noarch (@anaconda-0) + From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64 +Running Transaction Check +Running Transaction Test +Transaction Test Succeeded +Running Transaction + Installing : libqb-0.11.1-1.fc17.x86_64 1/48 + Installing : libtool-ltdl-2.4.2-3.fc17.x86_64 2/48 + Installing : cluster-glue-libs-1.0.6-9.fc17.1.x86_64 3/48 + Installing : libxslt-1.1.26-9.fc17.x86_64 4/48 + Installing : 1:perl-Pod-Escapes-1.04-211.fc17.noarch 5/48 + Installing : perl-threads-1.86-2.fc17.x86_64 6/48 + Installing : 4:perl-macros-5.14.2-211.fc17.x86_64 7/48 + Installing : 1:perl-Pod-Simple-3.16-211.fc17.noarch 8/48 + Installing : perl-Socket-2.001-1.fc17.x86_64 9/48 + Installing : perl-Carp-1.22-2.fc17.noarch 10/48 + Installing : 4:perl-libs-5.14.2-211.fc17.x86_64 11/48 + Installing : perl-threads-shared-1.40-2.fc17.x86_64 12/48 + Installing : perl-Scalar-List-Utils-1.25-1.fc17.x86_64 13/48 + Installing : 1:perl-Module-Pluggable-3.90-211.fc17.noarch 14/48 + Installing : perl-PathTools-3.33-211.fc17.x86_64 15/48 + Installing : 4:perl-5.14.2-211.fc17.x86_64 16/48 + Installing : libibverbs-1.1.6-2.fc17.x86_64 17/48 + Installing : keyutils-1.5.5-2.fc17.x86_64 18/48 + Installing : libgssglue-0.3-1.fc17.x86_64 19/48 + Installing : libtirpc-0.2.2-2.1.fc17.x86_64 20/48 + Installing : 1:net-snmp-libs-5.7.1-4.fc17.x86_64 21/48 + Installing : rpcbind-0.2.0-16.fc17.x86_64 22/48 + Installing : librdmacm-1.0.15-1.fc17.x86_64 23/48 + Installing : corosynclib-1.99.9-1.fc17.x86_64 24/48 + Installing : corosync-1.99.9-1.fc17.x86_64 25/48 +error reading information on service corosync: No such file or directory + Installing : 1:perl-TimeDate-1.20-6.fc17.noarch 26/48 + Installing : 1:quota-nls-4.00-3.fc17.noarch 27/48 + Installing : tcp_wrappers-7.6-69.fc17.x86_64 28/48 + Installing : 1:quota-4.00-3.fc17.x86_64 29/48 + Installing : libnfsidmap-0.25-1.fc17.x86_64 30/48 + Installing : 1:libwbclient-3.6.3-81.fc17.1.x86_64 31/48 + Installing : libnet-1.1.5-3.fc17.x86_64 32/48 + Installing : 2:ethtool-3.2-2.fc17.x86_64 33/48 + Installing : libevent-2.0.14-2.fc17.x86_64 34/48 + Installing : 1:nfs-utils-1.2.5-12.fc17.x86_64 35/48 + Installing : libtalloc-2.0.7-4.fc17.x86_64 36/48 + Installing : cifs-utils-5.3-2.fc17.x86_64 37/48 + Installing : libtasn1-2.12-1.fc17.x86_64 38/48 + Installing : OpenIPMI-libs-2.0.18-13.fc17.x86_64 39/48 + Installing : cluster-glue-1.0.6-9.fc17.1.x86_64 40/48 + Installing : p11-kit-0.12-1.fc17.x86_64 41/48 + Installing : gnutls-2.12.17-1.fc17.x86_64 42/48 + Installing : pacemaker-libs-1.1.7-2.fc17.x86_64 43/48 + Installing : pacemaker-cluster-libs-1.1.7-2.fc17.x86_64 44/48 + Installing : pacemaker-cli-1.1.7-2.fc17.x86_64 45/48 + Installing : xfsprogs-3.1.8-1.fc17.x86_64 46/48 + Installing : resource-agents-3.9.2-2.fc17.1.x86_64 47/48 + Installing : pacemaker-1.1.7-2.fc17.x86_64 48/48 + Verifying : xfsprogs-3.1.8-1.fc17.x86_64 1/48 + Verifying : 1:net-snmp-libs-5.7.1-4.fc17.x86_64 2/48 + Verifying : corosync-1.99.9-1.fc17.x86_64 3/48 + Verifying : cluster-glue-1.0.6-9.fc17.1.x86_64 4/48 + Verifying : perl-PathTools-3.33-211.fc17.x86_64 5/48 + Verifying : p11-kit-0.12-1.fc17.x86_64 6/48 + Verifying : 1:perl-Pod-Simple-3.16-211.fc17.noarch 7/48 + Verifying : OpenIPMI-libs-2.0.18-13.fc17.x86_64 8/48 + Verifying : libtasn1-2.12-1.fc17.x86_64 9/48 + Verifying : perl-threads-1.86-2.fc17.x86_64 10/48 + Verifying : 1:perl-Pod-Escapes-1.04-211.fc17.noarch 11/48 + Verifying : pacemaker-1.1.7-2.fc17.x86_64 12/48 + Verifying : 4:perl-5.14.2-211.fc17.x86_64 13/48 + Verifying : gnutls-2.12.17-1.fc17.x86_64 14/48 + Verifying : perl-threads-shared-1.40-2.fc17.x86_64 15/48 + Verifying : 4:perl-macros-5.14.2-211.fc17.x86_64 16/48 + Verifying : 1:perl-Module-Pluggable-3.90-211.fc17.noarch 17/48 + Verifying : 1:nfs-utils-1.2.5-12.fc17.x86_64 18/48 + Verifying : cluster-glue-libs-1.0.6-9.fc17.1.x86_64 19/48 + Verifying : pacemaker-libs-1.1.7-2.fc17.x86_64 20/48 + Verifying : libtalloc-2.0.7-4.fc17.x86_64 21/48 + Verifying : libevent-2.0.14-2.fc17.x86_64 22/48 + Verifying : perl-Socket-2.001-1.fc17.x86_64 23/48 + Verifying : libgssglue-0.3-1.fc17.x86_64 24/48 + Verifying : perl-Carp-1.22-2.fc17.noarch 25/48 + Verifying : libtirpc-0.2.2-2.1.fc17.x86_64 26/48 + Verifying : 2:ethtool-3.2-2.fc17.x86_64 27/48 + Verifying : 4:perl-libs-5.14.2-211.fc17.x86_64 28/48 + Verifying : libxslt-1.1.26-9.fc17.x86_64 29/48 + Verifying : rpcbind-0.2.0-16.fc17.x86_64 30/48 + Verifying : librdmacm-1.0.15-1.fc17.x86_64 31/48 + Verifying : resource-agents-3.9.2-2.fc17.1.x86_64 32/48 + Verifying : 1:quota-4.00-3.fc17.x86_64 33/48 + Verifying : 1:perl-TimeDate-1.20-6.fc17.noarch 34/48 + Verifying : perl-Scalar-List-Utils-1.25-1.fc17.x86_64 35/48 + Verifying : libtool-ltdl-2.4.2-3.fc17.x86_64 36/48 + Verifying : pacemaker-cluster-libs-1.1.7-2.fc17.x86_64 37/48 + Verifying : cifs-utils-5.3-2.fc17.x86_64 38/48 + Verifying : libnet-1.1.5-3.fc17.x86_64 39/48 + Verifying : corosynclib-1.99.9-1.fc17.x86_64 40/48 + Verifying : libqb-0.11.1-1.fc17.x86_64 41/48 + Verifying : 1:libwbclient-3.6.3-81.fc17.1.x86_64 42/48 + Verifying : libnfsidmap-0.25-1.fc17.x86_64 43/48 + Verifying : tcp_wrappers-7.6-69.fc17.x86_64 44/48 + Verifying : keyutils-1.5.5-2.fc17.x86_64 45/48 + Verifying : libibverbs-1.1.6-2.fc17.x86_64 46/48 + Verifying : 1:quota-nls-4.00-3.fc17.noarch 47/48 + Verifying : pacemaker-cli-1.1.7-2.fc17.x86_64 48/48 -[source,Bash] ----- -# source /etc/sysconfig/network -# hostname $HOSTNAME ----- -(((Nodes, Domain name (Remove from host name)))) +Installed: + corosync.x86_64 0:1.99.9-1.fc17 pacemaker.x86_64 0:1.1.7-2.fc17 -Now check the machine is using the correct names +Dependency Installed: + OpenIPMI-libs.x86_64 0:2.0.18-13.fc17 cifs-utils.x86_64 0:5.3-2.fc17 + cluster-glue.x86_64 0:1.0.6-9.fc17.1 cluster-glue-libs.x86_64 0:1.0.6-9.fc17.1 + corosynclib.x86_64 0:1.99.9-1.fc17 ethtool.x86_64 2:3.2-2.fc17 + gnutls.x86_64 0:2.12.17-1.fc17 keyutils.x86_64 0:1.5.5-2.fc17 + libevent.x86_64 0:2.0.14-2.fc17 libgssglue.x86_64 0:0.3-1.fc17 + libibverbs.x86_64 0:1.1.6-2.fc17 libnet.x86_64 0:1.1.5-3.fc17 + libnfsidmap.x86_64 0:0.25-1.fc17 libqb.x86_64 0:0.11.1-1.fc17 + librdmacm.x86_64 0:1.0.15-1.fc17 libtalloc.x86_64 0:2.0.7-4.fc17 + libtasn1.x86_64 0:2.12-1.fc17 libtirpc.x86_64 0:0.2.2-2.1.fc17 + libtool-ltdl.x86_64 0:2.4.2-3.fc17 libwbclient.x86_64 1:3.6.3-81.fc17.1 + libxslt.x86_64 0:1.1.26-9.fc17 net-snmp-libs.x86_64 1:5.7.1-4.fc17 + nfs-utils.x86_64 1:1.2.5-12.fc17 p11-kit.x86_64 0:0.12-1.fc17 + pacemaker-cli.x86_64 0:1.1.7-2.fc17 pacemaker-cluster-libs.x86_64 0:1.1.7-2.fc17 + pacemaker-libs.x86_64 0:1.1.7-2.fc17 perl.x86_64 4:5.14.2-211.fc17 + perl-Carp.noarch 0:1.22-2.fc17 perl-Module-Pluggable.noarch 1:3.90-211.fc17 + perl-PathTools.x86_64 0:3.33-211.fc17 perl-Pod-Escapes.noarch 1:1.04-211.fc17 + perl-Pod-Simple.noarch 1:3.16-211.fc17 perl-Scalar-List-Utils.x86_64 0:1.25-1.fc17 + perl-Socket.x86_64 0:2.001-1.fc17 perl-TimeDate.noarch 1:1.20-6.fc17 + perl-libs.x86_64 4:5.14.2-211.fc17 perl-macros.x86_64 4:5.14.2-211.fc17 + perl-threads.x86_64 0:1.86-2.fc17 perl-threads-shared.x86_64 0:1.40-2.fc17 + quota.x86_64 1:4.00-3.fc17 quota-nls.noarch 1:4.00-3.fc17 + resource-agents.x86_64 0:3.9.2-2.fc17.1 rpcbind.x86_64 0:0.2.0-16.fc17 + tcp_wrappers.x86_64 0:7.6-69.fc17 xfsprogs.x86_64 0:3.1.8-1.fc17 -[source,Bash] ----- -# uname -npcmk-1 -# dnsdomainname clusterlabs.org ----- +Complete! +[root@pcmk-1 ~]# +..... -Now repeat on pcmk-2. +Now install the cluster software on the second node. +== Setup == === Configuring Corosync === -Choose a port number and multi-cast footnote:[http://en.wikipedia.org/wiki/Multicast] address. footnote:[http://en.wikipedia.org/wiki/Multicast_address] Be sure that the -values you chose do not conflict with any existing clusters you might -have. For advice on choosing a multi-cast address, see -http://www.29west.com/docs/THPM/multicast-address-assignment.html For -this document, I have chosen port 4000 and used 226.94.1.1 as the -multi-cast address. +Choose a port number and multi-cast footnote:[http://en.wikipedia.org/wiki/Multicast] address. footnote:[http://en.wikipedia.org/wiki/Multicast_address] +Be sure that the values you chose do not conflict with any existing clusters you might have. +For advice on choosing a multi-cast address, see +http://www.29west.com/docs/THPM/multicast-address-assignment.html +For this document, I have chosen port 4000 and used 226.94.1.1 as the multi-cast address. [IMPORTANT] =========== The instructions below only apply for a machine with a single NIC. If you have a more complicated setup, you should edit the configuration manually. =========== [source,Bash] ---- # export ais_port=4000 # export ais_mcast=226.94.1.1 ---- Next we automatically determine the hosts address. By not using the full address, we make the configuration suitable to be copied to other nodes. [source,Bash] ---- # export ais_addr=`ip addr | grep "inet " | tail -n 1 | awk '{print $4}' | sed s/255/0/` ---- Display and verify the configuration options [source,Bash] ---- -# env | grep ais_ais_mcast=226.94.1.1 +# env | grep ais_ +ais_mcast=226.94.1.1 ais_port=4000 ais_addr=192.168.122.0 ---- Once you're happy with the chosen values, update the Corosync configuration [source,Bash] ---- # cp /etc/corosync/corosync.conf.example /etc/corosync/corosync.conf # sed -i.bak "s/.*mcastaddr:.*/mcastaddr:\ $ais_mcast/g" /etc/corosync/corosync.conf # sed -i.bak "s/.*mcastport:.*/mcastport:\ $ais_port/g" /etc/corosync/corosync.conf -# sed -i.bak "s/.*bindnetaddr:.*/bindnetaddr:\ $ais_addr/g" /etc/corosync/corosync.conf +# sed -i.bak "s/.*\tbindnetaddr:.*/bindnetaddr:\ $ais_addr/g" /etc/corosync/corosync.conf ---- -Finally, tell Corosync to load the Pacemaker plugin. +Lastly, you'll need to enable quorum [source,Bash] ----- -# cat <<-END >>/etc/corosync/service.d/pcmkservice { - # Load the Pacemaker Cluster Resource Manager - name: pacemaker - ver: 1 +.... +cat << END >> /etc/corosync/corosync.conf +quorum { + provider: corosync_votequorum + expected_votes: 2 } END ----- +.... The final configuration should look something like the sample in Appendix B, Sample Corosync Configuration. [IMPORTANT] =========== -When run in version 1 mode, the plugin does not start the Pacemaker -daemons. Instead it just sets up the quorum and messaging interfaces -needed by the rest of the stack. Starting the dameons occurs when the -Pacemaker init script is invoked. This resolves two long standing issues: - -.. Forking inside a multi-threaded process like Corosync causes all - sorts of pain. This has been problematic for Pacemaker as it needs a - number of daemons to be spawned. - -.. Corosync was never designed for staggered shutdown - something - previously needed in order to prevent the cluster from leaving - before Pacemaker could stop all active resources. -=========== +Pacemaker used to obtain membership and quorum from a custom Corosync plugin. +This plugin also had the capability to start Pacemaker automatically when Corosync was started. +Neither behavior is possible with Corosync 2.0 and beyond as support for plugins was removed. + +Instead, Pacemaker must started as a separate job/initscript. +Also, since Pacemaker used to use the plugin for message routing, a node using the plugin (Corosync prior to 2.0) cannot talk to one that isn't (Corosync 2.0+). + +Rolling upgrades between these versions are therefor not possible and an alternate strategy footnote:[http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ap-upgrade.html] must be used. +=========== === Propagate the Configuration === Now we need to copy the changes so far to the other node: [source,Bash] ---- -# for f in /etc/corosync/corosync.conf /etc/corosync/service.d/pcmk /etc/hosts; do scp $f pcmk-2:$f ; done +# for f in /etc/corosync/corosync.conf /etc/hosts; do scp $f pcmk-2:$f ; done corosync.conf 100% 1528 1.5KB/s 00:00 hosts 100% 281 0.3KB/s 00:00 # ---- 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 d124540c26..15a6d9d078 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,556 @@ = 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, 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: +Since its inclusion in the upstream 2.6.33 kernel, everything needed +to use DRBD has shiped with Fedora since version 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 +Loaded plugins: langpacks, presto, refresh-packagekit 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 +---> Package drbd-pacemaker.x86_64 0:8.3.11-5.fc17 will be installed +--> Processing Dependency: drbd-utils = 8.3.11-5.fc17 for package: drbd-pacemaker-8.3.11-5.fc17.x86_64 +---> Package drbd-udev.x86_64 0:8.3.11-5.fc17 will be installed --> Running transaction check ----> Package drbd-utils.x86_64 0:8.3.7-2.fc13 set to be updated +---> Package drbd-utils.x86_64 0:8.3.11-5.fc17 will be installed --> Finished Dependency Resolution Dependencies Resolved -================================================================================= - Package Arch Version Repository Size -================================================================================= +====================================================================================== + Package Arch Version Repository Size +====================================================================================== Installing: - drbd-pacemaker x86_64 8.3.7-2.fc13 fedora 19 k + drbd-pacemaker x86_64 8.3.11-5.fc17 updates-testing 22 k + drbd-udev x86_64 8.3.11-5.fc17 updates-testing 6.4 k Installing for dependencies: - drbd-utils x86_64 8.3.7-2.fc13 fedora 165 k + drbd-utils x86_64 8.3.11-5.fc17 updates-testing 183 k Transaction Summary -================================================================================= -Install 2 Package(s) -Upgrade 0 Package(s) +====================================================================================== +Install 2 Packages (+1 Dependent package) -Total download size: 184 k -Installed size: 427 k +Total download size: 212 k +Installed size: 473 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 +(1/3): drbd-pacemaker-8.3.11-5.fc17.x86_64.rpm | 22 kB 00:00 +(2/3): drbd-udev-8.3.11-5.fc17.x86_64.rpm | 6.4 kB 00:00 +(3/3): drbd-utils-8.3.11-5.fc17.x86_64.rpm | 183 kB 00:00 +-------------------------------------------------------------------------------------- +Total 293 kB/s | 212 kB 00:00 +Running Transaction Check 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 + Installing : drbd-utils-8.3.11-5.fc17.x86_64 1/3 + Installing : drbd-pacemaker-8.3.11-5.fc17.x86_64 2/3 + Installing : drbd-udev-8.3.11-5.fc17.x86_64 3/3 + Verifying : drbd-pacemaker-8.3.11-5.fc17.x86_64 1/3 + Verifying : drbd-udev-8.3.11-5.fc17.x86_64 2/3 + Verifying : drbd-utils-8.3.11-5.fc17.x86_64 3/3 Installed: - drbd-pacemaker.x86_64 0:8.3.7-2.fc13 + drbd-pacemaker.x86_64 0:8.3.11-5.fc17 drbd-udev.x86_64 0:8.3.11-5.fc17 Dependency Installed: - drbd-utils.x86_64 0:8.3.7-2.fc13 + drbd-utils.x86_64 0:8.3.11-5.fc17 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 +# vgdisplay | grep -e Name - e Free + VG Name vg_fedora13 + Free PE / Size 31 / 992.00 MiB +# lvs + LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert + lv_root vg_fedora13 -wi-ao-- 8.56g + lv_swap vg_fedora13 -wi-ao-- 960.00m +# lvcreate -n drbd-demo -L 1G vg_fedora13 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 + LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert + drbd-demo vg_fedora13 -wi-a--- 1.00G + lv_root vg_fedora13 -wi-ao-- 8.56g + lv_swap vg_fedora13 -wi-ao-- 960.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 + lv_root vg_fedora13 -wi-ao-- 8.56g + lv_swap vg_fedora13 -wi-ao-- 960.00m +# ssh pcmk-2 -- lvcreate -n drbd-demo -L 1G vg_fedora13 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 + drbd-demo vg_fedora13 -wi-a--- 1.00G + lv_root vg_fedora13 -wi-ao-- 8.56g + lv_swap vg_fedora13 -wi-ao-- 960.00m ---- === Write the DRBD Config === 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; + disk /dev/vg_fedora13/drbd-demo; + address 192.168.122.101:7789; } on pcmk-2 { - disk /dev/mapper/VolGroup-drbd--demo; - address 192.168.122.102:7789; + disk /dev/vg_fedora13/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 +# modprobe drbd +# drbdadm up wwwdata +# cat /proc/drbd +version: 8.3.11 (api:88/proto:86-96) +srcversion: 0D2B62DEDB020A425130935 + + 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:f oos:1015740 ---- 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 +version: 8.3.11 (api:88/proto:86-96) +srcversion: 0D2B62DEDB020A425130935 + + 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:f oos:1015740 ---- 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 +version: 8.3.11 (api:88/proto:86-96) +srcversion: 0D2B62DEDB020A425130935 + + 1: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r----- + ns:8064 nr:0 dw:0 dr:8728 al:0 bm:0 lo:0 pe:1 ua:0 ap:0 ep:1 wo:f oos:1007804 + [>....................] sync'ed: 0.9% (1007804/1015740)K + finish: 0:12:35 speed: 1,320 (1,320) K/sec +---- + +After a while, the sync should finish and you'll see: + +[source,Bash] +---- # 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 +version: 8.3.11 (api:88/proto:86-96) +srcversion: 0D2B62DEDB020A425130935 + + 1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----- + ns:1015740 nr:0 dw:0 dr:1016404 al:0 bm:62 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0 ---- pcmk-1 is now in the Primary state which allows it to be written to. 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) +mke2fs 1.42 (29-Nov-2011) 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 +Block size=4096 (log=2) +Fragment size=4096 (log=2) +Stride=0 blocks, Stripe width=0 blocks +63488 inodes, 253935 blocks +12696 blocks (5.00%) reserved for the super user +First data block=0 +Maximum filesystem blocks=260046848 +8 block groups +32768 blocks per group, 32768 fragments per group +7936 inodes per group Superblock backups stored on blocks: - 8193 + 32768, 98304, 163840, 229376 -Writing inode tables: done -Creating journal (1024 blocks): done +Allocating group tables: done +Writing inode tables: done +Creating journal (4096 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 +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 crm(live) # ---- 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 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" + clone-max=2 clone-node-max=1 notify=true +crm(drbd) # configure show +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 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" + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" +primitive 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" +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" + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" \ + last-lrm-refresh="1333446866" rsc_defaults $id="rsc-options" \ - resource-stickiness="100" + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" ---- 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 +crm(drbd) # cib commit drbd +INFO: commited 'drbd' shadow CIB to the cluster +crm(drbd) # quit +bye +# crm_mon -1 ============ -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. +Last updated: Tue Apr 3 13:50:01 2012 +Last change: Tue Apr 3 13:49:46 2012 via crm_shadow on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes +4 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 ] + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1 + WebSite (ocf::heartbeat:apache): Started pcmk-1 + Master/Slave Set: WebDataClone [WebData] + Masters: [ pcmk-1 ] + Slaves: [ pcmk-2 ] ---- [NOTE] ======= -Include details on adding a second DRBD resource +TODO: 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. +[source,Bash] +---- 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 +crm(fs) # configure show +node $id="1702537408" pcmk-1 +node $id="1719314624" pcmk-2 +primitive ClusterIP ocf:heartbeat:IPaddr2 \ + params ip="192.168.122.120" cidr_netmask="32" \ + op monitor interval="30s" primitive WebData ocf:linbit:drbd \ - params drbd_resource="wwwdata" \ - op monitor interval="60s" + 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" + 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" + params configfile="/etc/httpd/conf/httpd.conf" \ + op monitor interval="1min" ms WebDataClone WebData \ - meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" + 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" + dc-version="1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff" \ + cluster-infrastructure="corosync" \ + stonith-enabled="false" \ + no-quorum-policy="ignore" \ + last-lrm-refresh="1333446866" rsc_defaults $id="rsc-options" \ - resource-stickiness="100" + resource-stickiness="100" +op_defaults $id="op-options" \ + timeout="240s" ---- 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 +# crm_mon -1 ============ -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. +Last updated: Tue Apr 3 13:52:21 2012 +Last change: Tue Apr 3 13:52:06 2012 via crm_shadow on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes +5 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 + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-1 + WebSite (ocf::heartbeat:apache): Started pcmk-1 + Master/Slave Set: WebDataClone [WebData] + 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 +# crm_mon -1 ============ -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. +Last updated: Tue Apr 3 13:59:14 2012 +Last change: Tue Apr 3 13:52:36 2012 via crm_attribute on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes +5 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 +Node pcmk-1 (1702537408): standby +Online: [ pcmk-2 ] + +ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2 +WebSite (ocf::heartbeat:apache): Started pcmk-2 + Master/Slave Set: WebDataClone [WebData] + 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 +# crm_mon -1 ============ -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. +Last updated: Tue Apr 3 14:00:06 2012 +Last change: Tue Apr 3 14:00:00 2012 via crm_attribute on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes +5 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 + + ClusterIP (ocf::heartbeat:IPaddr2): Started pcmk-2 + WebSite (ocf::heartbeat:apache): Started pcmk-2 + Master/Slave Set: WebDataClone [WebData] + 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-Verification.txt b/doc/Clusters_from_Scratch/en-US/Ch-Verification.txt index 6982707534..1ab35db47f 100644 --- a/doc/Clusters_from_Scratch/en-US/Ch-Verification.txt +++ b/doc/Clusters_from_Scratch/en-US/Ch-Verification.txt @@ -1,125 +1,162 @@ = 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 ] +# systemctl start corosync.service ---- -Check the cluster started correctly and that an initial membership was -able to form +The first thing to check is if cluster communication is happy, for +that we use `corosync-cfgtool`. [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. +# corosync-cfgtool -s +Printing ring status. +Local node ID 1702537408 +RING ID 0 + id = 192.168.122.101 + status = ring 0 active with no faults ---- -With one node functional, it's now safe to start Corosync on the second -node as well. +We can see here that everything appears normal with our fixed IP +address, not a 127.0.0.x loopback address, listed as the +id+ and +no +faults+ for the status. + +If you see something different, you might want to start by checking +the node's network, firewall and selinux configurations. + +Next we check the membership and quorum APIs: [source,Bash] ---- -# ssh pcmk-2 -- /etc/init.d/corosync start -Starting Corosync Cluster Engine (corosync): [ OK ] -# +# corosync-cmapctl | grep members +runtime.totem.pg.mrp.srp.members.1702537408.ip (str) = r(0) ip(192.168.122.101) +runtime.totem.pg.mrp.srp.members.1702537408.join_count (u32) = 1 +runtime.totem.pg.mrp.srp.members.1702537408.status (str) = joined +# corosync-quorumtool -l + +Membership information + ---------------------- + Nodeid Votes Name +1702537408 1 pcmk-1 ---- -Check the cluster formed correctly +The node see's itself in both locations which is a good sign. + +If the node list is empty when you call `corosync-quorumtool`, then +you've not correctly quorum in 'corosync.conf'. + +With everything looking healthy, we start Corosync on the second node +and run the same communications check. [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. +# ssh pcmk-2 -- systemctl start corosync.service +# ssh pcmk-2 -- corosync-cfgtool -s +Printing ring status. +Local node ID 1719314624 +RING ID 0 + id = 192.168.122.102 + status = ring 0 active with no faults +---- + +Everything appears to look ok from +pcmk-2+, time to re-run the +membership and quorum checks to see if it shows up there too. + +Again, if you see something different to the above, check for the +usual suspects: network, firewall and selinux. + +[source,Bash] ---- +# corosync-cmapctl | grep members +runtime.totem.pg.mrp.srp.members.1702537408.ip (str) = r(0) ip(192.168.122.101) +runtime.totem.pg.mrp.srp.members.1702537408.join_count (u32) = 1 +runtime.totem.pg.mrp.srp.members.1702537408.status (str) = joined +runtime.totem.pg.mrp.srp.members.1719314624.ip (str) = r(0) ip(192.168.122.102) +runtime.totem.pg.mrp.srp.members.1719314624.join_count (u32) = 1 +runtime.totem.pg.mrp.srp.members.1719314624.status (str) = joined + +# corosync-quorumtool -l + +Membership information + ---------------------- + Nodeid Votes Name +1702537408 1 pcmk-1 +1719314624 1 pcmk-2 +---- + +All good! == Verify Pacemaker Installation == -Now that we have confirmed that Corosync is functional we can check the -rest of the stack. +Now that we have confirmed that Corosync is functional we can check +the rest of the stack. Start Pacemaker and check the necessary +processes have been started. [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 +# systemctl start pacemaker.service +# ps axf + PID TTY STAT TIME COMMAND + 2 ? S 0:00 [kthreadd] +...lots of processes... +28019 ? Ssl 0:03 /usr/sbin/corosync +28047 ? Ss 0:00 /usr/sbin/pacemakerd -f +28048 ? Ss 0:00 \_ /usr/libexec/pacemaker/cib +28049 ? Ss 0:00 \_ /usr/libexec/pacemaker/stonithd +28050 ? Ss 0:00 \_ /usr/lib64/heartbeat/lrmd +28051 ? Ss 0:00 \_ /usr/libexec/pacemaker/attrd +28052 ? Ss 0:00 \_ /usr/libexec/pacemaker/pengine +28053 ? Ss 0:00 \_ /usr/libexec/pacemaker/crmd ---- -Now try starting Pacemaker and check the necessary processes have been -started +If that looks ok, check the logs and crm_mon. [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 +# grep pacemakerd /var/log/messages | grep -e get_cluster_type -e read_config +Apr 3 09:19:32 pcmk-1 pacemakerd[28047]: info: get_cluster_type: Detected an active 'corosync' cluster +Apr 3 09:19:32 pcmk-1 pacemakerd[28047]: info: read_config: Reading configure for stack: corosync +# crm_mon -1 +============ +Last updated: Tue Apr 3 09:21:37 2012 +Last change: Tue Apr 3 09:19:54 2012 via crmd on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +1 Nodes configured, unknown expected votes +0 Resources configured. +============ + +Online: [ pcmk-1 ] ---- Next, check for any ERRORs during startup - there shouldn't be any. [source,Bash] ---- -# grep ERROR: /var/log/messages | grep -v unpack_resources -# +# grep -i error /var/log/messages ---- 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 +# ssh pcmk-2 -- systemctl start pacemaker.service +# crm_mon -1 ============ -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 +Last updated: Tue Apr 3 09:26:23 2012 +Last change: Tue Apr 3 09:26:21 2012 via crmd on pcmk-1 +Stack: corosync +Current DC: pcmk-1 (1702537408) - partition with quorum +Version: 1.1.7-2.fc17-ee0730e13d124c3d58f00016c3376a1de5323cff +2 Nodes configured, unknown expected votes 0 Resources configured. ============ + Online: [ pcmk-1 pcmk-2 ] ----