diff --git a/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt b/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt new file mode 100644 index 0000000000..954df04d78 --- /dev/null +++ b/doc/Pacemaker_Explained/en-US/Ap-FAQ.txt @@ -0,0 +1,74 @@ +[appendix] + +[[ap-faq]] +== FAQ == + + +[qanda] +Why is the Project Called Pacemaker?:: + indexterm:[Pacemaker] + First of all, the reason it's not called the CRM is because of the abundance + of terms footnote:[http://en.wikipedia.org/wiki/CRM] that are commonly + abbreviated to those three letters. The Pacemaker name came from Kham, + footnote:[http://khamsouk.souvanlasy.com/] a good friend of Pacemaker + developer Andrew Beekhof's, and was originally used by a Java GUI that Beekhof + was prototyping in early 2007. Alas, other commitments prevented the GUI from + progressing much and, when it came time to choose a name for this project, + Lars Marowsky-Bree suggested it was an even better fit for an independent CRM. + The idea stems from the analogy between the role of this software and that of + the little device that keeps the human heart pumping. Pacemaker monitors the + cluster and intervenes when necessary to ensure the smooth operation of the + services it provides. + There were a number of other names (and acronyms) tossed around, but suffice to + say "Pacemaker" was the best. + +Why was the Pacemaker Project Created?:: + + The decision was made to spin-off the CRM into its own project after the 2.1.3 + Heartbeat release in order to: + + * support both the Corosync and Heartbeat cluster stacks equally + * decouple the release cycles of two projects at very different stages of their life-cycles + * foster clearer package boundaries, thus leading to better and more stable interfaces + +What Messaging Layers are Supported?:: + indexterm:[Messaging Layers] + + * http://www.corosync.org/[Corosync] + * http://linux-ha.org/[Heartbeat] + +Can I Choose Which Messaging Layer to Use at Run Time?:: + + Yes. The CRM will automatically detect which started it and behave accordingly. + +Can I Have a Mixed Heartbeat-Corosync Cluster?:: + + No. + +[[q-messaging-layer]] Which Messaging Layer Should I Choose?:: + indexterm:[Cluster,Choosing Between Heartbeat and Corosync] + indexterm:[Cluster Stack,Corosync] indexterm:[Corosync] + indexterm:[Cluster Stack,Heartbeat] indexterm:[Heartbeat] + You can choose from multiple messaging layers, including + heartbeat, corosync 1 (with or without CMAN), and corosync 2. + Corosync 2 is the current state of the art due to its + more advanced features and better support for pacemaker, + but often the best choice is to use whatever comes with + your Linux distribution, and follow the distribution's + setup instructions. + +Where Can I Get Pre-built Packages?:: + + Most major Linux distributions have pacemaker packages in their standard + package repositories. See the http://clusterlabs.org/wiki/Install[Install wiki + page] for details. + +What Versions of Pacemaker Are Supported?:: + + Some Linux distributions (such as Red Hat Enterprise Linux and SUSE Linux + Enterprise) offer technical support for their customers; contact them + for details of such support. + For help within the community (mailing lists, IRC, etc.) from Pacemaker developers + and users, refer to the http://clusterlabs.org/wiki/Releases[Releases wiki page] + for an up-to-date list of versions considered to be supported by the project. + When seeking assistance, please try to ensure you have one of these versions. diff --git a/doc/Pacemaker_Explained/en-US/Ap-FAQ.xml b/doc/Pacemaker_Explained/en-US/Ap-FAQ.xml deleted file mode 100644 index 9e6d69f4c3..0000000000 --- a/doc/Pacemaker_Explained/en-US/Ap-FAQ.xml +++ /dev/null @@ -1,95 +0,0 @@ - - FAQ - - - History - - - Why is the Project Called PacemakernamingPacemaker? - - - First of all, the reason its not called the CRM is because of the abundance of terms that are commonly abbreviated to those three letters. - - The Pacemaker name came from Kham, a good friend of mine, and was originally used by a Java GUI that I was prototyping in early 2007. - Alas other commitments have prevented the GUI from progressing much and, when it came time to choose a name for this project, Lars suggested it was an even better fit for an independent CRM. - - - The idea stems from the analogy between the role of this software and that of the little device that keeps the human heart pumping. - Pacemaker monitors the cluster and intervenes when necessary to ensure the smooth operation of the services it provides. - - There were a number of other names (and acronyms) tossed around, but suffice to say "Pacemaker" was the best - - - - - Why was the Pacemaker Project Created? - - - The decision was made to spin-off the CRM into its own project after the 2.1.3 Heartbeat release in order to - - support both the Corosync and Heartbeat cluster stacks equally - decouple the release cycles of two projects at very different stages of their life-cycles - foster the clearer package boundaries, thus leading to - better and more stable interfaces - - - - - - Setup - - - What Messaging Layers Messaging Layers are Supported? - - - - Corosync () - Heartbeat () - - - - - - Can I Choose which Messaging Layer to use at Run Time? - - - Yes. The CRM will automatically detect which started it and behave accordingly. - - - - - Can I Have a Mixed Heartbeat-Corosync Cluster? - - - No. - - - - - Which Messaging Layer Should I Choose? - - - This is discussed in . - - - - - Where Can I Get Pre-built Packages? - - - Official packages for most major .rpm and based distributions are available from the ClusterLabs Website. - For Debian packages, building from source and details on using the above repositories, see our installation page. - - - - - What Versions of Pacemaker Are Supported? - - - Please refer to the Releases page for an up-to-date list of versions supported directly by the project. - When seeking assistance, please try to ensure you have one of these versions. - - - - - diff --git a/doc/Pacemaker_Explained/en-US/Ap-Install.txt b/doc/Pacemaker_Explained/en-US/Ap-Install.txt index 601a999b94..c34cb1482f 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-Install.txt +++ b/doc/Pacemaker_Explained/en-US/Ap-Install.txt @@ -1,119 +1,197 @@ [appendix] -[[ap-install]] -== Installation == - -[WARNING] -The following text may no longer be accurate in some places. - -=== Choosing a Cluster Stack === -indexterm:[Cluster,Choosing Between Heartbeat and Corosync] -indexterm:[Cluster Stack,Corosync] indexterm:[Corosync] -indexterm:[Cluster Stack,Heartbeat] indexterm:[Heartbeat] - -Ultimately the choice of cluster stack is a personal decision that -must be made in the context of you or your company's needs and -strategic direction. Pacemaker currently functions equally well with -both stacks. - -Here are some factors that may influence the decision: - -* SUSE/Novell, Red Hat and Oracle are all putting their collective - weight behind the Corosync cluster stack. -* Using Corosync gives your applications access to the following - additional cluster services -** distributed locking service -** extended virtual synchronization service -** cluster closed process group service -* It is likely that Pacemaker, at some point in the future, will make - use of some of these additional services not provided by Heartbeat - +== Installing == + +=== Installing the Software === + +Most major Linux distributions have pacemaker packages in their standard +package repositories, or the software can be built from source code. +See the http://clusterlabs.org/wiki/Install[Install wiki page] for details. + +See <> +for information about choosing a messaging layer. + === Enabling Pacemaker === -==== For Corosync ==== +==== Enabling Pacemaker For Corosync 2._x_ ==== + +High-level cluster management tools are available that can configure +corosync for you. This document focuses on the lower-level details +if you want to configure corosync yourself. + +Corosync configuration is normally located in ++/etc/corosync/corosync.conf+. + +.Corosync 2._x_ configuration file for two nodes *myhost1* and *myhost2* +==== +---- +totem { +version: 2 +secauth: off +cluster_name: mycluster +transport: udpu +} + +nodelist { + node { + ring0_addr: myhost1 + nodeid: 1 + } + node { + ring0_addr: myhost2 + nodeid: 2 + } +} + +quorum { +provider: corosync_votequorum +two_node: 1 +} + +logging { +to_syslog: yes +} +---- +==== + +.Corosync 2._x_ configuration file for three nodes *myhost1*, *myhost2* and *myhost3* +==== +---- +totem { +version: 2 +secauth: off +cluster_name: mycluster +transport: udpu +} + +nodelist { + node { + ring0_addr: myhost1 + nodeid: 1 + } + node { + ring0_addr: myhost2 + nodeid: 2 + } + node { + ring0_addr: myhost3 + nodeid: 3 + } +} -The Corosync configuration is normally located in -'/etc/corosync/corosync.conf' and an example for a machine with an -address of +1.2.3.4+ in a cluster communicating on port 1234 (without -peer authentication and message encryption) is shown below. +quorum { +provider: corosync_votequorum -.An example Corosync configuration file +} + +logging { +to_syslog: yes +} +---- +==== + +In the above examples, the +totem+ section defines what protocol version and +options (including encryption) to use, +footnote:[ +Please consult the Corosync website (http://www.corosync.org/) and +documentation for details on enabling encryption and peer authentication for +the cluster. +] +and gives the cluster a unique name (+mycluster+ in these examples). + +The +node+ section lists the nodes in this cluser. (See <> +for how this affects pacemaker.) + +The +quorum+ section defines how the cluster uses quorum. +The important thing is that two-node clusters must be handled specially, +so +two_node: 1+ must be defined for two-node clusters (and only for two-node +clusters). + +The +logging+ section should be self-explanatory. + +==== Enabling Pacemaker For Corosync 1._x_ ==== + +.Corosync 1._x_ configuration file for a cluster with all nodes on the +192.0.2.0/24+ network +==== [source,XML] ------- totem { version: 2 secauth: off threads: 0 interface { ringnumber: 0 - bindnetaddr: 1.2.3.4 + bindnetaddr: 192.0.2.0 mcastaddr: 239.255.1.1 mcastport: 1234 } } logging { fileline: off to_syslog: yes syslog_facility: daemon } amf { mode: disabled } - ------- +==== -The logging should be mostly obvious and the amf section refers to the -Availability Management Framework and is not covered in this document. +With corosync 1._x_, the +totem+ section contains the protocol version and +options as with 2._x_. However, nodes are also listed here, +in the +interface+ section. The +bindnetaddr+ option is usually the _network_ +address, thus allowing the same configuration file to be used on all nodes. +IPv4 or IPv6 addresses can be used with corosync. -The interesting part of the configuration is the totem section. This -is where we define how the node can communicate with the rest of the -cluster and what protocol version and options (including encryption -footnote:[ -Please consult the Corosync website (http://www.corosync.org/) and documentation for details on enabling encryption and peer authentication for the cluster. -] -) it should use. Beginners are encouraged to use the values shown and -modify the interface section based on their network. +The +amf+ section refers to the Availability Management Framework and +is not covered in this document. -It is also possible to configure Corosync for an IPv6 based -environment. Simply configure +bindnetaddr+ and +mcastaddr+ with their -IPv6 equivalents, eg. +The above corosync configuration is enough for corosync to operate by itself, +but corosync 1._x_ additionally needs to be told when it is being +used in conjunction with Pacemaker. This can be accomplished +in one of two ways: -.Example options for an IPv6 environment -------- - bindnetaddr: fec0::1:a800:4ff:fe00:20 - mcastaddr: ff05::1 -------- +* Via the CMAN software provided with Red Hat Enterprise Linux 6 and its derivatives +* Via the pacemaker corosync plugin -To tell Corosync to use the Pacemaker cluster manager, add the -following fragment to a functional Corosync configuration and restart -the cluster. +To use CMAN, consult its documentation. -.Configuration fragment for enabling Pacemaker under Corosync +To use the pacemaker corosync plugin, add the following fragment to the +corosync configuration and restart the cluster. + +.Corosync 1._x_configuration fragment to enable Pacemaker plugin +==== [source,XML] ------- aisexec { user: root group: root } service { name: pacemaker ver: 0 } ------- +==== The cluster needs to be run as root so that its child processes (the +lrmd+ in particular) have sufficient privileges to perform the actions requested of it. After all, a cluster manager that can't add an IP address or start apache is of little use. The second directive is the one that actually instructs the cluster to run Pacemaker. -==== For Heartbeat ==== +==== Enabling Pacemaker For Heartbeat ==== + +See the heartbeat documentation for how to set up a +ha.cf+ configuration file. -Add the following to a functional _ha.cf_ configuration file and restart Heartbeat: +To enable the use of pacemaker with heartbeat, add the following to a +functional +ha.cf+ configuration file and restart Heartbeat: -.Configuration fragment for enabling Pacemaker under Heartbeat +.Heartbeat configuration fragment to enable Pacemaker +==== ---- crm respawn ---- +==== diff --git a/doc/Pacemaker_Explained/en-US/Ap-LSB.txt b/doc/Pacemaker_Explained/en-US/Ap-LSB.txt index 8fa80f2b05..dd479111e3 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-LSB.txt +++ b/doc/Pacemaker_Explained/en-US/Ap-LSB.txt @@ -1,82 +1,82 @@ [appendix] [[ap-lsb]] -== init-Script LSB Compliance == +== Init Script LSB Compliance == -The relevant part of -http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html[LSB spec] +The relevant part of the +http://refspecs.linuxfoundation.org/lsb.shtml[LSB specifications] includes a description of all the return codes listed here. -Assuming +some_service+ is configured correctly and currently not -active, the following sequence will help you determine if it is LSB -compatible: +Assuming `some_service` is configured correctly and currently +inactive, the following sequence will help you determine if it is +LSB-compatible: . Start (stopped): + ---- # /etc/init.d/some_service start ; echo "result: $?" ---- + .. Did the service start? .. Did the command print result: 0 (in addition to the regular output)? + . Status (running): + ---- # /etc/init.d/some_service status ; echo "result: $?" ---- + .. Did the script accept the command? .. Did the script indicate the service was running? .. Did the command print result: 0 (in addition to the regular output)? + . Start (running): + ---- # /etc/init.d/some_service start ; echo "result: $?" ---- + .. Is the service still running? .. Did the command print result: 0 (in addition to the regular output)? + . Stop (running): + ---- # /etc/init.d/some_service stop ; echo "result: $?" ---- + .. Was the service stopped? .. Did the command print result: 0 (in addition to the regular output)? + . Status (stopped): + ---- # /etc/init.d/some_service status ; echo "result: $?" ---- + .. Did the script accept the command? .. Did the script indicate the service was not running? .. Did the command print result: 3 (in addition to the regular output)? + . Stop (stopped): + ---- # /etc/init.d/some_service stop ; echo "result: $?" ---- + .. Is the service still stopped? .. Did the command print result: 0 (in addition to the regular output)? + . Status (failed): + This step is not readily testable and relies on manual inspection of the script. + The script can use one of the error codes (other than 3) listed in the LSB spec to indicate that it is active but failed. This tells the cluster that before moving the resource to another node, it needs to stop it on the existing one first. If the answer to any of the above questions is no, then the script is not LSB compliant. Your options are then to either fix the script or write an OCF agent based on the existing script. diff --git a/doc/Pacemaker_Explained/en-US/Ap-Samples.txt b/doc/Pacemaker_Explained/en-US/Ap-Samples.txt index 7f4f05796c..4494c18d55 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-Samples.txt +++ b/doc/Pacemaker_Explained/en-US/Ap-Samples.txt @@ -1,142 +1,152 @@ [appendix] == Sample Configurations == === Empty === .An Empty Configuration ======= [source,XML] ------- - + ------- ======= === Simple === -.Simple Configuration - 2 nodes, some cluster options and a resource +.A simple configuration with two nodes, some cluster options and a resource ======= [source,XML] ------- - + - - + + + + + - - - - - - - - - + + + + + + + + + + + + + ------- ======= -In this example, we have one resource (an IP address) that we check +In the above example, we have one resource (an IP address) that we check every five minutes and will run on host +c001n01+ until either the resource fails 10 times or the host shuts down. - === Advanced Configuration === -.Advanced configuration - groups and clones with stonith +.An advanced configuration with groups, clones and STONITH ======= [source,XML] ------- - + - - - + + + + + - - - - - - - - - + + + + + + + + + + + + + ------- ======= diff --git a/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.txt b/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.txt index d83618840c..ef2d311fb5 100644 --- a/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.txt +++ b/doc/Pacemaker_Explained/en-US/Ap-Upgrade-Config.txt @@ -1,131 +1,123 @@ [appendix] == Upgrading the Configuration from 0.6 == -=== Preparation === indexterm:[Upgrading the Configuration] indexterm:[Configuration,Upgrading] -indexterm:[Download,DTD] -indexterm:[DTD,Download] - -Download the latest -http://hg.clusterlabs.org/pacemaker/stable-1.0/file-raw/tip/xml/crm.dtd[DTD] -and ensure your configuration validates. - === Perform the upgrade === ==== Upgrade the software ==== Refer to the appendix: <> ==== Upgrade the Configuration ==== As XML is not the friendliest of languages, it is common for cluster administrators to have scripted some of their activities. In such cases, it is likely that those scripts will not work with the new 1.0 syntax. In order to support such environments, it is actually possible to continue using the old 0.6 syntax. The downside is, however, that not all the new features will be available and there is a performance impact since the cluster must do a non-persistent configuration upgrade before each transition. So while using the old syntax is possible, it is not advisable to continue using it indefinitely. Even if you wish to continue using the old syntax, it is advisable to follow the upgrade procedure to ensure that the cluster is able to use your existing configuration (since it will perform much the same task internally). . Create a shadow copy to work with + ----- # crm_shadow --create upgrade06 ----- . Verify the configuration is valid indexterm:[Configuration,Verify]indexterm:[Verify,Configuration] + ----- # crm_verify --live-check ----- . Fix any errors or warnings . Perform the upgrade: + ----- # cibadmin --upgrade ----- . If this step fails, there are three main possibilities: .. The configuration was not valid to start with - go back to step 2 .. The transformation failed - report a bug or mailto:pacemaker@oss.clusterlabs.org?subject=Transformation%20failed%20during%20upgrade[email the project] .. The transformation was successful but produced an invalid result footnote:[ The most common reason is ID values being repeated or invalid. Pacemaker 1.0 is much stricter regarding this type of validation. ] + If the result of the transformation is invalid, you may see a number of errors from the validation library. If these are not helpful, visit http://clusterlabs.org/wiki/Validation_FAQ and/or try the procedure described below under <> + . Check the changes + ----- # crm_shadow --diff ----- + If at this point there is anything about the upgrade that you wish to fine-tune (for example, to change some of the automatic IDs) now is the time to do so. Since the shadow configuration is not in use by the cluster, it is safe to edit the file manually: + ----- # crm_shadow --edit ----- + This will open the configuration in your favorite editor (whichever is specified by the standard +$EDITOR+ environment variable) + . Preview how the cluster will react + Test what the cluster will do when you upload the new configuration + ------ # crm_simulate --live-check --save-dotfile upgrade06.dot -S # graphviz upgrade06.dot ------ + Verify that either no resource actions will occur or that you are happy with any that are scheduled. If the output contains actions you do not expect (possibly due to changes to the score calculations), you may need to make further manual changes. See <> for further details on how to interpret the output of `crm_simulate` + . Upload the changes + ----- # crm_shadow --commit upgrade06 --force ----- If this step fails, something really strange has occurred. You should report a bug. [[s-upgrade-config-manual]] ==== Manually Upgrading the Configuration ==== indexterm:[Configuration,Upgrade manually] It is also possible to perform the configuration upgrade steps manually. To do this Locate the 'upgrade06.xsl' conversion script or download the latest version from https://github.com/ClusterLabs/pacemaker/tree/master/xml/upgrade06.xsl[Git] . Convert the XML blob: indexterm:[XML,Convert] + ----- # xsltproc /path/to/upgrade06.xsl config06.xml > config10.xml ----- + . Locate the 'pacemaker.rng' script. . Check the XML validity: indexterm:[Validate Configuration]indexterm:[Configuration,Validate XML] + ---- # xmllint --relaxng /path/to/pacemaker.rng config10.xml ---- The advantage of this method is that it can be performed without the cluster running and any validation errors should be more informative (despite being generated by the same library!) since they include line numbers. diff --git a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.txt b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.txt index e3dde0b1aa..01380bd26d 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.txt @@ -1,682 +1,692 @@ = Advanced Configuration = [[s-remote-connection]] == Connecting from a Remote Machine == indexterm:[Cluster,Remote connection] indexterm:[Cluster,Remote administration] Provided Pacemaker is installed on a machine, it is possible to connect to the cluster even if the machine itself is not in the same cluster. To do this, one simply sets up a number of environment variables and runs the same commands as when working on a cluster node. .Environment Variables Used to Connect to Remote Instances of the CIB -[width="95%",cols="1m,2<",options="header",align="center"] +[width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Environment Variable +|Default |Description |CIB_user +|$USER |The user to connect as. Needs to be part of the +hacluster+ group on - the target host. Defaults to _$USER_. + the target host. indexterm:[Environment Variable,CIB_user] |CIB_passwd +| |The user's password. Read from the command line if unset. indexterm:[Environment Variable,CIB_passwd] |CIB_server -|The host to contact. Defaults to _localhost_. +|localhost +|The host to contact indexterm:[Environment Variable,CIB_server] |CIB_port +| |The port on which to contact the server; required. indexterm:[Environment Variable,CIB_port] |CIB_encrypted -|Encrypt network traffic; defaults to _true_. +|TRUE +|Whether to encrypt network traffic indexterm:[Environment Variable,CIB_encrypted] |========================================================= So, if +c001n01+ is an active cluster node and is listening on +1234+ for connections, and +someguy+ is a member of the +hacluster+ group, then the following would prompt for +someguy+'s password and return the cluster's current configuration: ---- # export CIB_port=1234; export CIB_server=c001n01; export CIB_user=someguy; # cibadmin -Q ---- For security reasons, the cluster does not listen for remote connections by default. If you wish to allow remote access, you need to set the +remote-tls-port+ (encrypted) or +remote-clear-port+ (unencrypted) top-level options (ie., those kept in the cib tag, like +num_updates+ and +epoch+). -.Extra top-level CIB options for remote access -[width="95%",cols="1m,2<",options="header",align="center"] +.Extra top-level CIB properties for remote access +[width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field +|Default |Description |remote-tls-port -|Listen for encrypted remote connections on this port. Default: _none_ +|_none_ +|Listen for encrypted remote connections on this port. indexterm:[remote-tls-port,Remote Connection Option] indexterm:[Remote Connection,Option,remote-tls-port] |remote-clear-port -|Listen for plaintext remote connections on this port. Default: _none_ +|_none_ +|Listen for plaintext remote connections on this port. indexterm:[remote-clear-port,Remote Connection Option] indexterm:[Remote Connection,Option,remote-clear-port] |========================================================= [[s-recurring-start]] == Specifying When Recurring Actions are Performed == By default, recurring actions are scheduled relative to when the resource started. So if your resource was last started at 14:32 and you have a backup set to be performed every 24 hours, then the backup will always run at in the middle of the business day - hardly desirable. To specify a date/time that the operation should be relative to, set the operation's +interval-origin+. The cluster uses this point to calculate the correct +start-delay+ such that the operation will occur at _origin + (interval * N)_. So, if the operation's interval is 24h, it's interval-origin is set to +02:00+ and it is currently +14:32+, then the cluster would initiate the operation with a start delay of 11 hours and 28 minutes. If the resource is moved to another node before 2am, then the operation is of course cancelled. The value specified for interval and +interval-origin+ can be any date/time conforming to the http://en.wikipedia.org/wiki/ISO_8601[ISO8601 standard]. By way of example, to specify an operation that would run on the first Monday of 2009 and every Monday after that you would add: .Specifying a Base for Recurring Action Intervals ===== [source,XML] ===== == Moving Resources == indexterm:[Moving,Resources] indexterm:[Resource,Moving] === Manual Intervention === There are primarily two occasions when you would want to move a -resource from it's current location: when the whole node is under +resource from its current location: when the whole node is under maintenance, and when a single resource needs to be moved. Since everything eventually comes down to a score, you could create constraints for every resource to prevent them from running on one node. While the configuration can seem convoluted at times, not even we would require this of administrators. Instead one can set a special node attribute which tells the cluster "don't let anything run here". There is even a helpful tool to help query and set it, called `crm_standby`. To check the standby status of the current machine, simply run: ---- -# crm_standby --get-value +# crm_standby -G ---- -A value of +true+ indicates that the node is _NOT_ able to host any -resources, while a value of +false+ says that it _CAN_. +A value of +on+ indicates that the node is _not_ able to host any +resources, while a value of +off+ says that it _can_. You can also check the status of other nodes in the cluster by -specifying the `--node-uname` option: +specifying the `--node` option: ---- -# crm_standby --get-value --node-uname sles-2 +# crm_standby -G --node sles-2 ---- -To change the current node's standby status, use `--attr-value` -instead of `--get-value`. +To change the current node's standby status, use `-v` instead of `-G`: ---- -# crm_standby --attr-value +# crm_standby -v on ---- -Again, you can change another host's value by supplying a host name with `--node-uname`. +Again, you can change another host's value by supplying a hostname with `--node`. + +==== Moving One Resource ==== When only one resource is required to move, we do this by creating location constraints. However, once again we provide a user friendly shortcut as part of the `crm_resource` command, which creates and -modifies the extra constraints for you. If +Email+ was running on +modifies the extra constraints for you. If +Email+ were running on +sles-1+ and you wanted it moved to a specific location, the command would look something like: ---- # crm_resource -M -r Email -H sles-2 ---- Behind the scenes, the tool will create the following location constraint: [source,XML] It is important to note that subsequent invocations of `crm_resource -M` are not cumulative. So, if you ran these commands ---- # crm_resource -M -r Email -H sles-2 # crm_resource -M -r Email -H sles-3 ---- then it is as if you had never performed the first command. To allow the resource to move back again, use: ---- # crm_resource -U -r Email ---- Note the use of the word _allow_. The resource can move back to its original location but, depending on +resource-stickiness+, it might stay where it is. To be absolutely certain that it moves back to +sles-1+, move it there before issuing the call to `crm_resource -U`: ---- # crm_resource -M -r Email -H sles-1 # crm_resource -U -r Email ---- Alternatively, if you only care that the resource should be moved from -its current location, try +its current location, try: ---- -# crm_resource -M -r Email` +# crm_resource -B -r Email ---- Which will instead create a negative constraint, like [source,XML] This will achieve the desired effect, but will also have long-term consequences. As the tool will warn you, the creation of a +-INFINITY+ constraint will prevent the resource from running on that node until `crm_resource -U` is used. This includes the situation where every other cluster node is no longer available! In some cases, such as when +resource-stickiness+ is set to +INFINITY+, it is possible that you will end up with the problem described in <>. The tool can detect some of these cases and deals with them by also creating both a positive and negative constraint. Eg. +Email+ prefers +sles-1+ with a score of +-INFINITY+ +Email+ prefers +sles-2+ with a score of +INFINITY+ which has the same long-term consequences as discussed earlier. [[s-failure-migration]] === Moving Resources Due to Failure === New in 1.0 is the concept of a migration threshold. footnote:[ The naming of this option was perhaps unfortunate as it is easily confused with true migration, the process of moving a resource from one node to another without stopping it. Xen virtual guests are the most common example of resources that can be migrated in this manner. ] Simply define +migration-threshold=N+ for a resource and it will migrate to a new node after N failures. There is no threshold defined by default. To determine the resource's current failure status and limits, use `crm_mon --failcounts`. By default, once the threshold has been reached, this node will no longer be allowed to run the failed resource until the administrator manually resets the resource's failcount using `crm_failcount` (after hopefully first fixing the failure's cause). However it is possible to expire them by setting the resource's +failure-timeout+ option. So a setting of +migration-threshold=2+ and +failure-timeout=60s+ would cause the resource to move to a new node after 2 failures, and allow it to move back (depending on the stickiness and constraint scores) after one minute. There are two exceptions to the migration threshold concept; they occur when a resource either fails to start or fails to stop. Start failures cause the failcount to be set to +INFINITY+ and thus always cause the resource to move immediately. Stop failures are slightly different and crucial. If a resource fails to stop and STONITH is enabled, then the cluster will fence the node in order to be able to start the resource elsewhere. If STONITH is not enabled, then the cluster has no way to continue and will not try to start the resource elsewhere, but will try to stop it again after the failure timeout. [IMPORTANT] Please read <> before enabling this option. === Moving Resources Due to Connectivity Changes === Setting up the cluster to move resources when external connectivity is lost is a two-step process. ==== Tell Pacemaker to monitor connectivity ==== To do this, you need to add a +ping+ resource to the cluster. The +ping+ resource uses the system utility of the same name to a test if list of machines (specified by DNS hostname or IPv4/IPv6 address) are reachable and uses the results to maintain a node attribute normally called +pingd+. footnote:[ The attribute name is customizable; that allows multiple ping groups to be defined. ] [NOTE] Older versions of Heartbeat required users to add ping nodes to _ha.cf_ - this is no longer required. [IMPORTANT] =========== Older versions of Pacemaker used a custom binary called 'pingd' for this functionality; this is now deprecated in favor of 'ping'. If your version of Pacemaker does not contain the ping agent, you can download the latest version from https://github.com/ClusterLabs/pacemaker/tree/master/extra/resources/ping =========== Normally the resource will run on all cluster nodes, which means that you'll need to create a clone. A template for this can be found below along with a description of the most interesting parameters. .Common Options for a 'ping' Resource [width="95%",cols="1m,4<",options="header",align="center"] |========================================================= |Field |Description |dampen |The time to wait (dampening) for further changes to occur. Use this to prevent a resource from bouncing around the cluster when cluster nodes notice the loss of connectivity at slightly different times. indexterm:[dampen,Ping Resource Option] indexterm:[Ping Resource,Option,dampen] |multiplier |The number of connected ping nodes gets multiplied by this value to get a score. Useful when there are multiple ping nodes configured. indexterm:[multiplier,Ping Resource Option] indexterm:[Ping Resource,Option,multiplier] |host_list |The machines to contact in order to determine the current connectivity status. Allowed values include resolvable DNS host names, IPv4 and IPv6 addresses. indexterm:[host_list,Ping Resource Option] indexterm:[Ping Resource,Option,host_list] |========================================================= .An example ping cluster resource that checks node connectivity once every minute ===== [source,XML] ------------ ------------ ===== [IMPORTANT] =========== You're only half done. The next section deals with telling Pacemaker how to deal with the connectivity status that +ocf:pacemaker:ping+ is recording. =========== ==== Tell Pacemaker how to interpret the connectivity data ==== [NOTE] ====== Before reading the following, please make sure you have read and understood <> above. ====== There are a number of ways to use the connectivity data provided by Heartbeat. The most common setup is for people to have a single ping node, to prevent the cluster from running a resource on any unconnected node. //// TODO: is the idea that only nodes that can reach eg. the router should have active resources? //// .Don't run on unconnected nodes ===== [source,XML] ------- ------- ===== A more complex setup is to have a number of ping nodes configured. You can require the cluster to only run resources on nodes that can connect to all (or a minimum subset) of them. .Run only on nodes connected to three or more ping nodes; this assumes +multiplier+ is set to 1000: ===== [source,XML] ------- ------- ===== Instead you can tell the cluster only to _prefer_ nodes with the best connectivity. Just be sure to set +multiplier+ to a value higher than that of +resource-stickiness+ (and don't set either of them to +INFINITY+). .Prefer the node with the most connected ping nodes ===== [source,XML] ------- ------- ===== It is perhaps easier to think of this in terms of the simple constraints that the cluster translates it into. For example, if +sles-1+ is connected to all 5 ping nodes but +sles-2+ is only connected to 2, then it would be as if you instead had the following constraints in your configuration: .How the cluster translates the pingd constraint ===== [source,XML] ------- ------- ===== The advantage is that you don't have to manually update any constraints whenever your network connectivity changes. You can also combine the concepts above into something even more complex. The example below shows how you can prefer the node with the most connected ping nodes provided they have connectivity to at least three (again assuming that +multiplier+ is set to 1000). .A more complex example of choosing a location based on connectivity ===== [source,XML] ------- ------- ===== === Resource Migration === Some resources, such as Xen virtual guests, are able to move to another location without loss of state. We call this resource migration; this is different from the normal practice of stopping the resource on the first machine and starting it elsewhere. Not all resources are able to migrate, see the Migration Checklist below, and those that can, won't do so in all situations. Conceptually there are two requirements from which the other prerequisites follow: * the resource must be active and healthy at the old location * everything required for the resource to run must be available on both the old and new locations The cluster is able to accommodate both push and pull migration models by requiring the resource agent to support two new actions: +migrate_to+ (performed on the current location) and +migrate_from+ (performed on the destination). In push migration, the process on the current location transfers the resource to the new location where is it later activated. In this scenario, most of the work would be done in the +migrate_to+ action and, if anything, the activation would occur during +migrate_from+. Conversely for pull, the +migrate_to+ action is practically empty and +migrate_from+ does most of the work, extracting the relevant resource state from the old location and activating it. There is no wrong or right way to implement migration for your service, as long as it works. ==== Migration Checklist ==== * The resource may not be a clone. * The resource must use an OCF style agent. * The resource must not be in a failed or degraded state. * The resource must not, directly or indirectly, depend on any primitive or group resources. * The resource must support two new actions: +migrate_to+ and +migrate_from+, and advertise them in its metadata. * The resource must have the +allow-migrate+ meta-attribute set to +true+ (which is not the default). //// TODO: how can a KVM with DRBD migrate? //// If the resource depends on a clone, and at the time the resource needs to be move, the clone has instances that are stopping and instances that are starting, then the resource will be moved in the traditional manner. The Policy Engine is not yet able to model this situation correctly and so takes the safe (yet less optimal) path. [[s-reusing-config-elements]] == Reusing Rules, Options and Sets of Operations == Sometimes a number of constraints need to use the same set of rules, and resources need to set the same options and parameters. To simplify this situation, you can refer to an existing object using an +id-ref+ instead of an id. So if for one resource you have [source,XML] ------ ------ Then instead of duplicating the rule for all your other resources, you can instead specify: .Referencing rules from other constraints ===== [source,XML] ------- ------- ===== [IMPORTANT] =========== The cluster will insist that the +rule+ exists somewhere. Attempting to add a reference to a non-existing rule will cause a validation failure, as will attempting to remove a +rule+ that is referenced elsewhere. =========== The same principle applies for +meta_attributes+ and +instance_attributes+ as illustrated in the example below: .Referencing attributes, options, and operations from other resources ===== [source,XML] ------- ------- ===== == Reloading Services After a Definition Change == The cluster automatically detects changes to the definition of services it manages. However, the normal response is to stop the service (using the old definition) and start it again (with the new definition). This works well, but some services are smarter and can be told to use a new set of options without restarting. To take advantage of this capability, your resource agent must: . Accept the +reload+ operation and perform any required actions. _The steps required here depend completely on your application!_ + .The DRBD Agent's Control logic for Supporting the +reload+ Operation ===== [source,Bash] ------- case $1 in start) drbd_start ;; stop) drbd_stop ;; reload) drbd_reload ;; monitor) drbd_monitor ;; *) drbd_usage exit $OCF_ERR_UNIMPLEMENTED ;; esac exit $? ------- ===== . Advertise the +reload+ operation in the +actions+ section of its metadata + .The DRBD Agent Advertising Support for the +reload+ Operation ===== [source,XML] ------- 1.1 Master/Slave OCF Resource Agent for DRBD ... ------- ===== . Advertise one or more parameters that can take effect using +reload+. + Any parameter with the +unique+ set to 0 is eligible to be used in this way. + .Parameter that can be changed using reload ===== [source,XML] ------- Full path to the drbd.conf file. Path to drbd.conf ------- ===== Once these requirements are satisfied, the cluster will automatically know to reload the resource (instead of restarting) when a non-unique -fields changes. +field changes. [NOTE] ====== The metadata is re-read when the resource is started. This may mean that the resource will be restarted the first time, even though you changed a parameter with +unique=0+ ====== [NOTE] ====== If both a unique and non-unique field are changed simultaneously, the resource will still be restarted. ====== diff --git a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.txt b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.txt index 8262578da5..52ca036d1e 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.txt @@ -1,1019 +1,1030 @@ = Advanced Resource Types = [[group-resources]] == Groups - A Syntactic Shortcut == indexterm:[Group Resources] indexterm:[Resources,Groups] One of the most common elements of a cluster is a set of resources that need to be located together, start sequentially, and stop in the reverse order. To simplify this configuration we support the concept of groups. .An example group ====== [source,XML] ------- - + - + ------- ====== Although the example above contains only two resources, there is no limit to the number of resources a group can contain. The example is also sufficient to explain the fundamental properties of a group: * Resources are started in the order they appear in (+Public-IP+ first, then +Email+) * Resources are stopped in the reverse order to which they appear in (+Email+ first, then +Public-IP+) If a resource in the group can't run anywhere, then nothing after that is allowed to run, too. * If +Public-IP+ can't run anywhere, neither can +Email+; * but if +Email+ can't run anywhere, this does not affect +Public-IP+ in any way The group above is logically equivalent to writing: .How the cluster sees a group resource ====== [source,XML] ------- - + ------- ====== Obviously as the group grows bigger, the reduced configuration effort can become significant. Another (typical) example of a group is a DRBD volume, the filesystem mount, an IP address, and an application that uses them. === Group Properties === .Properties of a Group Resource [width="95%",cols="3m,5<",options="header",align="center"] |========================================================= |Field |Description |id |Your name for the group indexterm:[id,Group Resource Property] indexterm:[Resource,Group Property,id] |========================================================= === Group Options === Options inherited from <> resources: +priority, target-role, is-managed+ === Group Instance Attributes === Groups have no instance attributes, however any that are set here will be inherited by the group's children. === Group Contents === Groups may only contain a collection of <> cluster resources. To refer to the child of a group resource, just use the child's id instead of the group's. === Group Constraints === Although it is possible to reference the group's children in constraints, it is usually preferable to use the group's name instead. .Example constraints involving groups ====== [source,XML] ------- ------- ====== === Group Stickiness === indexterm:[resource-stickiness,Groups] Stickiness, the measure of how much a resource wants to stay where it is, is additive in groups. Every active resource of the group will contribute its stickiness value to the group's total. So if the default +resource-stickiness+ is 100, and a group has seven members, five of which are active, then the group as a whole will prefer its current location with a score of 500. [[s-resource-clone]] == Clones - Resources That Get Active on Multiple Hosts == indexterm:[Clone Resources] indexterm:[Resources,Clones] Clones were initially conceived as a convenient way to start N instances of an IP resource and have them distributed throughout the cluster for load balancing. They have turned out to quite useful for a number of purposes including integrating with Red Hat's DLM, the fencing subsystem, and OCFS2. You can clone any resource, provided the resource agent supports it. Three types of cloned resources exist: * Anonymous * Globally Unique * Stateful Anonymous clones are the simplest type. These resources behave completely identically everywhere they are running. Because of this, there can only be one copy of an anonymous clone active per machine. Globally unique clones are distinct entities. A copy of the clone running on one machine is not equivalent to another instance on another node. Nor would any two copies on the same node be equivalent. Stateful clones are covered later in <>. .An example clone ====== [source,XML] ------- ------- ====== === Clone Properties === .Properties of a Clone Resource [width="95%",cols="3m,5<",options="header",align="center"] |========================================================= |Field |Description |id |Your name for the clone indexterm:[id,Clone Property] indexterm:[Clone,Property,id] |========================================================= === Clone Options === Options inherited from <> resources: +priority, target-role, is-managed+ -.Clone specific configuration options -[width="95%",cols="3m,5<",options="header",align="center"] +.Clone-specific configuration options +[width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field +|Default |Description |clone-max -|How many copies of the resource to start. Defaults to the number of - nodes in the cluster. +|number of nodes in cluster +|How many copies of the resource to start indexterm:[clone-max,Clone Option] indexterm:[Clone,Option,clone-max] |clone-node-max -|How many copies of the resource can be started on a single node; - default _1_. +|1 +|How many copies of the resource can be started on a single node indexterm:[clone-node-max,Clone Option] indexterm:[Clone,Option,clone-node-max] |notify +|true |When stopping or starting a copy of the clone, tell all the other - copies beforehand and when the action was successful. Allowed values: - _false_, +true+ + copies beforehand and again when the action was successful. Allowed values: + +false+, +true+ indexterm:[notify,Clone Option] indexterm:[Clone,Option,notify] |globally-unique +|false |Does each copy of the clone perform a different function? Allowed - values: _false_, +true+ + values: +false+, +true+ indexterm:[globally-unique,Clone Option] indexterm:[Clone,Option,globally-unique] |ordered +|false |Should the copies be started in series (instead of in - parallel). Allowed values: _false_, +true+ + parallel)? Allowed values: +false+, +true+ indexterm:[ordered,Clone Option] indexterm:[Clone,Option,ordered] |interleave -|Changes the behavior of ordering constraints (between clones/masters) - so that instances can start/stop as soon as their peer instance has - (rather than waiting for every instance of the other clone - has). Allowed values: _false_, +true+ +|false +|If this clone depends on another clone via an ordering constraint, +is it allowed to start after the local instance of the other clone +starts, rather than wait for all instances of the other clone to start? +Allowed values: +false+, +true+ indexterm:[interleave,Clone Option] indexterm:[Clone,Option,interleave] |========================================================= === Clone Instance Attributes === Clones have no instance attributes; however, any that are set here will be inherited by the clone's children. === Clone Contents === Clones must contain exactly one group or one regular resource. [WARNING] You should never reference the name of a clone's child. If you think you need to do this, you probably need to re-evaluate your design. === Clone Constraints === In most cases, a clone will have a single copy on each active cluster node. If this is not the case, you can indicate which nodes the cluster should preferentially assign copies to with resource location constraints. These constraints are written no differently to those for regular resources except that the clone's id is used. Ordering constraints behave slightly differently for clones. In the example below, +apache-stats+ will wait until all copies of the clone that need to be started have done so before being started itself. Only if _no_ copies can be started +apache-stats+ will be prevented from being active. Additionally, the clone will wait for +apache-stats+ to be stopped before stopping the clone. Colocation of a regular (or group) resource with a clone means that the resource can run on any machine with an active copy of the clone. The cluster will choose a copy based on where the clone is running and the resource's own location preferences. Colocation between clones is also possible. In such cases, the set of allowed locations for the clone is limited to nodes on which the clone is (or will be) active. Allocation is then performed as normally. .Example constraints involving clones ====== [source,XML] ------- ------- ====== === Clone Stickiness === indexterm:[resource-stickiness,Clones] To achieve a stable allocation pattern, clones are slightly sticky by default. If no value for +resource-stickiness+ is provided, the clone will use a value of 1. Being a small value, it causes minimal disturbance to the score calculations of other resources but is enough to prevent Pacemaker from needlessly moving copies around the cluster. === Clone Resource Agent Requirements === Any resource can be used as an anonymous clone, as it requires no additional support from the resource agent. Whether it makes sense to do so depends on your resource and its resource agent. Globally unique clones do require some additional support in the resource agent. In particular, it must only respond with -+${OCF_SUCCESS}+ if the node has that exact instance active. All ++$\{OCF_SUCCESS}+ if the node has that exact instance active. All other probes for instances of the clone should result in -+${OCF_NOT_RUNNING}+. Unless of course they are failed, in which case -they should return one of the other OCF error codes. ++$\{OCF_NOT_RUNNING}+ (or one of the other OCF error codes if +they are failed). Copies of a clone are identified by appending a colon and a numerical offset, eg. +apache:2+. Resource agents can find out how many copies there are by examining the +OCF_RESKEY_CRM_meta_clone_max+ environment variable and which copy it is by examining +OCF_RESKEY_CRM_meta_clone+. You should not make any assumptions (based on +OCF_RESKEY_CRM_meta_clone+) about which copies are active. In particular, the list of active copies will not always be an unbroken sequence, nor always start at 0. ==== Clone Notifications ==== Supporting notifications requires the +notify+ action to be implemented. Once supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it. .Environment variables supplied with Clone notify actions [width="95%",cols="5,3<",options="header",align="center"] |========================================================= |Variable |Description |OCF_RESKEY_CRM_meta_notify_type |Allowed values: +pre+, +post+ indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,type] indexterm:[type,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_operation |Allowed values: +start+, +stop+ indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,operation] indexterm:[operation,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_start_resource |Resources to be started indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,start_resource] indexterm:[start_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_stop_resource |Resources to be stopped indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,stop_resource] indexterm:[stop_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_active_resource |Resources that are running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,active_resource] indexterm:[active_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_inactive_resource |Resources that are not running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,inactive_resource] indexterm:[inactive_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_start_uname |Nodes on which resources will be started indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,start_uname] indexterm:[start_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_stop_uname |Nodes on which resources will be stopped indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,stop_uname] indexterm:[stop_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_active_uname |Nodes on which resources are running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,active_uname] indexterm:[active_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_inactive_uname |Nodes on which resources are not running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,inactive_uname] indexterm:[inactive_uname,Notification Environment Variable] |========================================================= The variables come in pairs, such as +OCF_RESKEY_CRM_meta_notify_start_resource+ and +OCF_RESKEY_CRM_meta_notify_start_uname+ and should be treated as an array of whitespace separated elements. Thus in order to indicate that +clone:0+ will be started on +sles-1+, +clone:2+ will be started on +sles-3+, and +clone:3+ will be started on +sles-2+, the cluster would set .Example notification variables ====== [source,Bash] ------- OCF_RESKEY_CRM_meta_notify_start_resource="clone:0 clone:2 clone:3" OCF_RESKEY_CRM_meta_notify_start_uname="sles-1 sles-3 sles-2" ------- ====== ==== Proper Interpretation of Notification Environment Variables ==== .Pre-notification (stop): * Active resources: +$OCF_RESKEY_CRM_meta_notify_active_resource+ * Inactive resources: +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (stop) / Pre-notification (start): * Active resources ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Inactive resources ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (start): * Active resources: ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Inactive resources: ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ [[s-resource-multistate]] == Multi-state - Resources That Have Multiple Modes == indexterm:[Multi-state Resources] indexterm:[Resources,Multi-state] Multi-state resources are a specialization of Clone resources; please ensure you understand the section on clones before continuing! They allow the instances to be in one of two operating modes; these are called +Master+ and +Slave+, but can mean whatever you wish them to mean. The only limitation is that when an instance is started, it must come up in the +Slave+ state. === Multi-state Properties === .Properties of a Multi-State Resource [width="95%",cols="3m,5<",options="header",align="center"] |========================================================= |Field |Description |id |Your name for the multi-state resource indexterm:[id,Multi-State Property] indexterm:[Multi-State,Property,id] |========================================================= === Multi-state Options === Options inherited from <> resources: +priority+, +target-role+, +is-managed+ Options inherited from <> resources: +clone-max+, +clone-node-max+, +notify+, +globally-unique+, +ordered+, +interleave+ -.Multi-state specific resource configuration options -[width="95%",cols="3m,5<",options="header",align="center"] +.Multi-state-specific resource configuration options +[width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field +|Default |Description |master-max -|How many copies of the resource can be promoted to +master+ status; - default 1. +|1 +|How many copies of the resource can be promoted to the +master+ role indexterm:[master-max,Multi-State Option] indexterm:[Multi-State,Option,master-max] |master-node-max -|How many copies of the resource can be promoted to +master+ status on - a single node; default 1. +|1 +|How many copies of the resource can be promoted to the +master+ role on + a single node indexterm:[master-node-max,Multi-State Option] indexterm:[Multi-State,Option,master-node-max] |========================================================= === Multi-state Instance Attributes === Multi-state resources have no instance attributes; however, any that are set here will be inherited by master's children. === Multi-state Contents === Masters must contain exactly one group or one regular resource. [WARNING] You should never reference the name of a master's child. If you think you need to do this, you probably need to re-evaluate your design. === Monitoring Multi-State Resources === The normal type of monitor actions are not sufficient to monitor a multi-state resource in the +Master+ state. To detect failures of the +Master+ instance, you need to define an additional monitor action with +role="Master"+. [IMPORTANT] =========== It is crucial that _every_ monitor operation has a different interval! This is because Pacemaker currently differentiates between operations only by resource and interval; so if eg. a master/slave resource has the same monitor interval for both roles, Pacemaker would ignore the role when checking the status - which would cause unexpected return codes, and therefore unnecessary complications. =========== .Monitoring both states of a multi-state resource ====== [source,XML] ------- ------- ====== === Multi-state Constraints === -In most cases, a multi-state resources will have a single copy on each +In most cases, multi-state resources will have a single copy on each active cluster node. If this is not the case, you can indicate which nodes the cluster should preferentially assign copies to with resource location constraints. These constraints are written no differently to those for regular resources except that the master's id is used. When considering multi-state resources in constraints, for most purposes it is sufficient to treat them as clones. The exception is when the +rsc-role+ and/or +with-rsc-role+ fields (for colocation constraints) and +first-action+ and/or +then-action+ fields (for ordering constraints) are used. .Additional constraint options relevant to multi-state resources -[width="95%",cols="3m,5<",options="header",align="center"] +[width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field +|Default |Description |rsc-role +|started |An additional attribute of colocation constraints that specifies the - role that +rsc+ must be in. Allowed values: _Started_, +Master+, - +Slave+. + role that +rsc+ must be in. Allowed values: +started+, +master+, + +slave+. indexterm:[rsc-role,Ordering Constraints] indexterm:[Constraints,Ordering,rsc-role] |with-rsc-role +|started |An additional attribute of colocation constraints that specifies the - role that +with-rsc+ must be in. Allowed values: _Started_, - +Master+, +Slave+. + role that +with-rsc+ must be in. Allowed values: +started+, + +master+, +slave+. indexterm:[with-rsc-role,Ordering Constraints] indexterm:[Constraints,Ordering,with-rsc-role] |first-action +|start |An additional attribute of ordering constraints that specifies the action that the +first+ resource must complete before executing the - specified action for the +then+ resource. Allowed values: _start_, + specified action for the +then+ resource. Allowed values: +start+, +stop+, +promote+, +demote+. indexterm:[first-action,Ordering Constraints] indexterm:[Constraints,Ordering,first-action] |then-action +|value of +first-action+ |An additional attribute of ordering constraints that specifies the action that the +then+ resource can only execute after the +first-action+ on the +first+ resource has completed. Allowed - values: +start+, +stop+, +promote+, +demote+. Defaults to the value - (specified or implied) of +first-action+. + values: +start+, +stop+, +promote+, +demote+. indexterm:[then-action,Ordering Constraints] indexterm:[Constraints,Ordering,then-action] |========================================================= In the example below, +myApp+ will wait until one of the database copies has been started and promoted to master before being started itself. Only if no copies can be promoted will +apache-stats+ be prevented from being active. Additionally, the database will wait for +myApp+ to be stopped before it is demoted. .Example constraints involving multi-state resources ====== [source,XML] ------- ------- ====== Colocation of a regular (or group) resource with a multi-state resource means that it can run on any machine with an active copy of the multi-state resource that is in the specified state (+Master+ or +Slave+). In the example, the cluster will choose a location based on where database is running as a +Master+, and if there are multiple +Master+ instances it will also factor in +myApp+'s own location preferences when deciding which location to choose. Colocation with regular clones and other multi-state resources is also possible. In such cases, the set of allowed locations for the +rsc+ clone is (after role filtering) limited to nodes on which the +with-rsc+ multi-state resource is (or will be) in the specified role. Allocation is then performed as-per-normal. ==== Using Multi-state Resources in Colocation/Ordering Sets ==== .Additional colocation set options relevant to multi-state resources -[width="95%",cols="3m,5<",options="header",align="center"] +[width="95%",cols="1m,1,6<",options="header",align="center"] |========================================================= |Field +|Default |Description |role -|An additional attribute of colocation constraint sets that specifies the - role that *all members of the set* must be in. Allowed values: _Started_, +Master+, - +Slave+. +|started +|The role that 'all members' of the set must be in. Allowed values: +started+, +master+, + +slave+. indexterm:[role,Ordering Constraints] indexterm:[Constraints,Ordering,role] |========================================================= In the following example +B+'s master must be located on the same node as +A+'s master. Additionally resources +C+ and +D+ must be located on the same node as +B+'s master. -.Colocate C and C with A and B's master instances +.Colocate C and D with A's and B's master instances ====== [source,XML] ------- - + - - - + ------- ====== .Additional ordered set options relevant to multi-state resources -[width="95%",cols="3m,5<",options="header",align="center"] +[width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field +|Default |Description |action -|An additional attribute of ordering constraint set that specifies the - action that applies to *all members of the set*. Allowed - values: +start+, +stop+, +promote+, +demote+. Defaults to the value - (specified or implied) of +first-action+. +|value of +first-action+ +|An additional attribute of ordering constraint sets that specifies the + action that applies to 'all members' of the set. Allowed + values: +start+, +stop+, +promote+, +demote+. indexterm:[action,Ordering Constraints] indexterm:[Constraints,Ordering,action] |========================================================= In the following example +B+ cannot be promoted until +A+'s has been promoted. Additionally resources +C+ and +D+ must wait until +A+ and +B+ have been promoted before they can start. -.Start C and C after first promoting A and B +.Start C and D after first promoting A and B ====== [source,XML] ------- - - + + - + - + ------- ====== === Multi-state Stickiness === indexterm:[resource-stickiness,Multi-State] To achieve a stable allocation pattern, multi-state resources are slightly sticky by default. If no value for +resource-stickiness+ is provided, the multi-state resource will use a value of 1. Being a small value, it causes minimal disturbance to the score calculations of other resources but is enough to prevent Pacemaker from needlessly moving copies around the cluster. === Which Resource Instance is Promoted === During the start operation, most Resource Agent scripts should call the `crm_master` utility. This tool automatically detects both the resource and host and should be used to set a preference for being promoted. Based on this, +master-max+, and +master-node-max+, the instance(s) with the highest preference will be promoted. The other alternative is to create a location constraint that indicates which nodes are most preferred as masters. .Manually specifying which node should be promoted ====== [source,XML] ------- ------- ====== === Multi-state Resource Agent Requirements === Since multi-state resources are an extension of cloned resources, all the requirements of Clones are also requirements of multi-state resources. Additionally, multi-state resources require two extra actions: +demote+ and +promote+; these actions are responsible for changing the state of the resource. Like +start+ and +stop+, they should return +OCF_SUCCESS+ if they completed successfully or a relevant error code if they did not. The states can mean whatever you wish, but when the resource is started, it must come up in the mode called +Slave+. From there the cluster will then decide which instances to promote to +Master+. In addition to the Clone requirements for monitor actions, agents must also _accurately_ report which state they are in. The cluster relies on the agent to report its status (including role) accurately and does not indicate to the agent what role it currently believes it to be in. .Role implications of OCF return codes [width="95%",cols="5,3<",options="header",align="center"] |========================================================= |Monitor Return Code |Description |OCF_NOT_RUNNING |Stopped indexterm:[Return Code,OCF_NOT_RUNNING] |OCF_SUCCESS |Running (Slave) indexterm:[Return Code,OCF_SUCCESS] |OCF_RUNNING_MASTER |Running (Master) indexterm:[Return Code,OCF_RUNNING_MASTER] |OCF_FAILED_MASTER |Failed (Master) indexterm:[Return Code,OCF_FAILED_MASTER] |Other |Failed (Slave) |========================================================= === Multi-state Notifications === Like clones, supporting notifications requires the +notify+ action to be implemented. Once supported the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it. .Environment variables supplied with Master notify actions footnote:[Emphasized variables are specific to +Master+ resources and all behave in the same manner as described for Clone resources.] [width="95%",cols="5,3<",options="header",align="center"] |========================================================= |Variable |Description |OCF_RESKEY_CRM_meta_notify_type |Allowed values: +pre+, +post+ indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,type] indexterm:[type,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_operation |Allowed values: +start+, +stop+ indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,operation] indexterm:[operation,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_active_resource |Resources the that are running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,active_resource] indexterm:[active_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_inactive_resource |Resources the that are not running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,inactive_resource] indexterm:[inactive_resource,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_master_resource_ |Resources that are running in +Master+ mode indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,master_resource] indexterm:[master_resource,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_slave_resource_ |Resources that are running in +Slave+ mode indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,slave_resource] indexterm:[slave_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_start_resource |Resources to be started indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,start_resource] indexterm:[start_resource,Notification Environment Variable] |indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,stop_resource] indexterm:[stop_resource,Notification Environment Variable] OCF_RESKEY_CRM_meta_notify_stop_resource |Resources to be stopped |_OCF_RESKEY_CRM_meta_notify_promote_resource_ |Resources to be promoted indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,promote_resource] indexterm:[promote_resource,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_demote_resource_ |Resources to be demoted indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,demote_resource] indexterm:[demote_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_start_uname |Nodes on which resources will be started indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,start_uname] indexterm:[start_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_stop_uname |Nodes on which resources will be stopped indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,stop_uname] indexterm:[stop_uname,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_promote_uname_ |Nodes on which resources will be promote indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,promote_uname] indexterm:[promote_uname,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_demote_uname_ |Nodes on which resources will be demoted indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,demote_uname] indexterm:[demote_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_active_uname |Nodes on which resources are running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,active_uname] indexterm:[active_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_inactive_uname |Nodes on which resources are not running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,inactive_uname] indexterm:[inactive_uname,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_master_uname_ |Nodes on which resources are running in +Master+ mode indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,master_uname] indexterm:[master_uname,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_slave_uname_ |Nodes on which resources are running in +Slave+ mode indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,slave_uname] indexterm:[slave_uname,Notification Environment Variable] |========================================================= === Multi-state - Proper Interpretation of Notification Environment Variables === .Pre-notification (demote): * +Active+ resources: +$OCF_RESKEY_CRM_meta_notify_active_resource+ * +Master+ resources: +$OCF_RESKEY_CRM_meta_notify_master_resource+ * +Slave+ resources: +$OCF_RESKEY_CRM_meta_notify_slave_resource+ * Inactive resources: +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (demote) / Pre-notification (stop): * +Active+ resources: +$OCF_RESKEY_CRM_meta_notify_active_resource+ * +Master+ resources: ** +$OCF_RESKEY_CRM_meta_notify_master_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * +Slave+ resources: +$OCF_RESKEY_CRM_meta_notify_slave_resource+ * Inactive resources: +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ .Post-notification (stop) / Pre-notification (start) * +Active+ resources: ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * +Master+ resources: ** +$OCF_RESKEY_CRM_meta_notify_master_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * +Slave+ resources: ** +$OCF_RESKEY_CRM_meta_notify_slave_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Inactive resources: ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (start) / Pre-notification (promote) * +Active+ resources: ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * +Master+ resources: ** +$OCF_RESKEY_CRM_meta_notify_master_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * +Slave+ resources: ** +$OCF_RESKEY_CRM_meta_notify_slave_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Inactive resources: ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (promote) * +Active+ resources: ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * +Master+ resources: ** +$OCF_RESKEY_CRM_meta_notify_master_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_demote_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * +Slave+ resources: ** +$OCF_RESKEY_CRM_meta_notify_slave_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Inactive resources: ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources that were demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ diff --git a/doc/Pacemaker_Explained/en-US/Ch-Basics.txt b/doc/Pacemaker_Explained/en-US/Ch-Basics.txt index affa9e32d9..21cc2be8a4 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Basics.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Basics.txt @@ -1,370 +1,380 @@ = Configuration Basics = == Configuration Layout == The cluster is written using XML notation and divided into two main sections: configuration and status. The status section contains the history of each resource on each node and based on this data, the cluster can construct the complete current state of the cluster. The authoritative source for the status section is the local resource manager (lrmd) process on each cluster node and the cluster will occasionally repopulate the entire section. For this reason it is never written to disk and administrators are advised against modifying it in any way. The configuration section contains the more traditional information like cluster options, lists of resources and indications of where they should be placed. The configuration section is the primary focus of this document. The configuration section itself is divided into four parts: * Configuration options (called +crm_config+) * Nodes * Resources * Resource relationships (called +constraints+) .An empty configuration ====== [source,XML] ------- - - - - - - - - - + + + + + + + + + ------- ====== == The Current State of the Cluster == Before one starts to configure a cluster, it is worth explaining how to view the finished product. For this purpose we have created the `crm_mon` utility that will display the current state of an active cluster. It can show the cluster status by node or by resource and can be used in either single-shot or dynamically-updating mode. There are also modes for displaying a list of the operations performed (grouped by node and resource) as well as information about failures. Using this tool, you can examine the state of the cluster for irregularities and see how it responds when you cause or simulate failures. Details on all the available options can be obtained using the `crm_mon --help` command. .Sample output from crm_mon ====== ------- ============ Last updated: Fri Nov 23 15:26:13 2007 Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec) 3 Nodes configured. 5 Resources configured. ============ Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1 192.168.100.182 (heartbeat:IPaddr): Started sles-1 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1 rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1 child_DoFencing:2 (stonith:external/vmware): Started sles-1 Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3 rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3 child_DoFencing:0 (stonith:external/vmware): Started sles-3 ------- ====== .Sample output from crm_mon -n ====== ------- ============ Last updated: Fri Nov 23 15:26:13 2007 Current DC: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec) 3 Nodes configured. 5 Resources configured. ============ Node: sles-1 (1186dc9a-324d-425a-966e-d757e693dc86): online Node: sles-2 (02fb99a8-e30e-482f-b3ad-0fb3ce27d088): standby Node: sles-3 (2298606a-6a8c-499a-9d25-76242f7006ec): online Resource Group: group-1 192.168.100.181 (heartbeat::ocf:IPaddr): Started sles-1 192.168.100.182 (heartbeat:IPaddr): Started sles-1 192.168.100.183 (heartbeat::ocf:IPaddr): Started sles-1 rsc_sles-1 (heartbeat::ocf:IPaddr): Started sles-1 rsc_sles-2 (heartbeat::ocf:IPaddr): Started sles-3 rsc_sles-3 (heartbeat::ocf:IPaddr): Started sles-3 Clone Set: DoFencing child_DoFencing:0 (stonith:external/vmware): Started sles-3 child_DoFencing:1 (stonith:external/vmware): Stopped child_DoFencing:2 (stonith:external/vmware): Started sles-1 ------- ====== The DC (Designated Controller) node is where all the decisions are made and if the current DC fails a new one is elected from the remaining cluster nodes. The choice of DC is of no significance to an administrator beyond the fact that its logs will generally be more interesting. == How Should the Configuration be Updated? == There are three basic rules for updating the cluster configuration: * Rule 1 - Never edit the cib.xml file manually. Ever. I'm not making this up. * Rule 2 - Read Rule 1 again. * Rule 3 - The cluster will notice if you ignored rules 1 & 2 and refuse to use the configuration. Now that it is clear how NOT to update the configuration, we can begin to explain how you should. The most powerful tool for modifying the configuration is the +cibadmin+ command which talks to a running cluster. With +cibadmin+, the user can query, add, remove, update or replace any part of the configuration; all changes take effect immediately, so there is no need to perform a reload-like operation. The simplest way of using cibadmin is to use it to save the current configuration to a temporary file, edit that file with your favorite text or XML editor and then upload the revised configuration. .Safely using an editor to modify the cluster configuration ====== -------- # cibadmin --query > tmp.xml # vi tmp.xml # cibadmin --replace --xml-file tmp.xml -------- ====== Some of the better XML editors can make use of a Relax NG schema to help make sure any changes you make are valid. The schema describing -the configuration can normally be found in -'/usr/lib/heartbeat/pacemaker.rng' on most systems. - +the configuration can be found in +pacemaker.rng+, which may be +deployed in a location such as +/usr/share/pacemaker+ or ++/usr/lib/heartbeat+ depending on your operating system and how you +installed the software. If you only wanted to modify the resources section, you could instead do .Safely using an editor to modify a subsection of the cluster configuration ====== -------- # cibadmin --query --obj_type resources > tmp.xml # vi tmp.xml # cibadmin --replace --obj_type resources --xml-file tmp.xml -------- ====== to avoid modifying any other part of the configuration. == Quickly Deleting Part of the Configuration == Identify the object you wish to delete. Eg. run .Searching for STONITH related configuration items ====== -------- # cibadmin -Q | grep stonith -------- [source,XML] -------- -------- ====== Next identify the resource's tag name and id (in this case we'll choose +primitive+ and +child_DoFencing+). Then simply execute: ---- # cibadmin --delete --crm_xml '' ---- == Updating the Configuration Without Using XML == Some common tasks can also be performed with one of the higher level tools that avoid the need to read or edit XML. To enable stonith for example, one could run: ---- -# crm_attribute --attr-name stonith-enabled --attr-value true +# crm_attribute --name stonith-enabled --update 1 ---- Or, to see if +somenode+ is allowed to run resources, there is: ---- -# crm_standby --get-value --node-uname somenode +# crm_standby --get-value --node somenode ---- Or, to find the current location of +my-test-rsc+, one can use: ---- # crm_resource --locate --resource my-test-rsc ---- +Examples of using these tools for specific cases will be given throughout this +document where appropriate. + +[NOTE] +==== +Old versions of pacemaker (1.0.3 and earlier) had different +command-line tool syntax. If you are using an older version, +check your installed manual pages for the proper syntax to use. +==== + [[s-config-sandboxes]] == Making Configuration Changes in a Sandbox == Often it is desirable to preview the effects of a series of changes before updating the configuration atomically. For this purpose we have created `crm_shadow` which creates a "shadow" copy of the configuration and arranges for all the command line tools to use it. To begin, simply invoke `crm_shadow` and give it the name of a configuration to create footnote:[Shadow copies are identified with a name, making it possible to have more than one.] ; be sure to follow the simple on-screen instructions. WARNING: Read the above carefully, failure to do so could result in you destroying the cluster's active configuration! .Creating and displaying the active sandbox ====== ---- # crm_shadow --create test Setting up shadow instance Type Ctrl-D to exit the crm_shadow shell shadow[test]: shadow[test] # crm_shadow --which test ---- ====== From this point on, all cluster commands will automatically use the shadow copy instead of talking to the cluster's active configuration. Once you have finished experimenting, you can either commit the changes, or discard them as shown below. Again, be sure to follow the on-screen instructions carefully. - For a full list of `crm_shadow` options and -commands, invoke it with the --help option. +commands, invoke it with the `--help` option. .Using a sandbox to make multiple changes atomically ====== ---- shadow[test] # crm_failcount -G -r rsc_c001n01 name=fail-count-rsc_c001n01 value=0 - shadow[test] # crm_standby -v on -n c001n02 - shadow[test] # crm_standby -G -n c001n02 + shadow[test] # crm_standby -v on -N c001n02 + shadow[test] # crm_standby -G -N c001n02 name=c001n02 scope=nodes value=on shadow[test] # cibadmin --erase --force shadow[test] # cibadmin --query shadow[test] # crm_shadow --delete test --force Now type Ctrl-D to exit the crm_shadow shell shadow[test] # exit # crm_shadow --which - No shadow instance provided + No active shadow configuration defined # cibadmin -Q ---- ====== Making changes in a sandbox and verifying the real configuration is untouched [[s-config-testing-changes]] == Testing Your Configuration Changes == We saw previously how to make a series of changes to a "shadow" copy of the configuration. Before loading the changes back into the cluster (eg. `crm_shadow --commit mytest --force`), it is often advisable to simulate the effect of the changes with +crm_simulate+, eg. ---- # crm_simulate --live-check -VVVVV --save-graph tmp.graph --save-dotfile tmp.dot ---- The tool uses the same library as the live cluster to show what it would have done given the supplied input. It's output, in addition to a significant amount of logging, is stored in two files +tmp.graph+ and +tmp.dot+, both are representations of the same thing -- the cluster's response to your changes. In the graph file is stored the complete transition, containing a list of all the actions, their parameters and their pre-requisites. Because the transition graph is not terribly easy to read, the tool also generates a Graphviz dot-file representing the same information. == Interpreting the Graphviz output == * Arrows indicate ordering dependencies * Dashed-arrows indicate dependencies that are not present in the transition graph * Actions with a dashed border of any color do not form part of the transition graph * Actions with a green border form part of the transition graph * Actions with a red border are ones the cluster would like to execute but cannot run * Actions with a blue border are ones the cluster does not feel need to be executed * Actions with orange text are pseudo/pretend actions that the cluster uses to simplify the graph * Actions with black text are sent to the LRM * Resource actions have text of the form pass:[rsc]_pass:[action]_pass:[interval] pass:[node] * Any action depending on an action with a red border will not be able to execute. * Loops are _really_ bad. Please report them to the development team. === Small Cluster Transition === image::images/Policy-Engine-small.png["An example transition graph as represented by Graphviz",width="16cm",height="6cm",align="center"] In the above example, it appears that a new node, +pcmk-2+, has come online and that the cluster is checking to make sure +rsc1+, +rsc2+ and +rsc3+ are not already running there (Indicated by the +*_monitor_0+ entries). Once it did that, and assuming the resources were not active there, it would have liked to stop +rsc1+ and +rsc2+ on +pcmk-1+ and move them to +pcmk-2+. However, there appears to be some problem and the cluster cannot or is not permitted to perform the stop actions which implies it also cannot perform the start actions. For some reason the cluster does not want to start +rsc3+ anywhere. For information on the options supported by `crm_simulate`, use the `--help` option. === Complex Cluster Transition === image::images/Policy-Engine-big.png["Another, slightly more complex, transition graph that you're not expected to be able to read",width="16cm",height="20cm",align="center"] == Do I Need to Update the Configuration on all Cluster Nodes? == No. Any changes are immediately synchronized to the other active members of the cluster. To reduce bandwidth, the cluster only broadcasts the incremental updates that result from your changes and uses MD5 checksums to ensure that each copy is completely consistent. diff --git a/doc/Pacemaker_Explained/en-US/Ch-Constraints.txt b/doc/Pacemaker_Explained/en-US/Ch-Constraints.txt index 84d272b42c..3a157e60c7 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Constraints.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Constraints.txt @@ -1,667 +1,661 @@ = Resource Constraints = indexterm:[Resource,Constraints] == Scores == Scores of all kinds are integral to how the cluster works. Practically everything from moving a resource to deciding which resource to stop in a degraded cluster is achieved by manipulating scores in some way. Scores are calculated on a per-resource basis and any node with a negative score for a resource can't run that resource. After calculating the scores for a resource, the cluster then chooses the node with the highest one. === Infinity Math === +INFINITY+ is currently defined as 1,000,000 and addition/subtraction with it follows these three basic rules: * Any value + +INFINITY+ = +INFINITY+ * Any value - +INFINITY+ = -+INFINITY+ * +INFINITY+ - +INFINITY+ = -+INFINITY+ == Deciding Which Nodes a Resource Can Run On == indexterm:[Location Constraints] indexterm:[Resource,Constraints,Location] There are two alternative strategies for specifying which nodes a resources can run on. One way is to say that by default they can run anywhere and then create location constraints for nodes that are not allowed. The other option is to have nodes "opt-in"... to start with nothing able to run anywhere and selectively enable allowed nodes. - -=== Options === -.Options for Simple Location Constraints -[width="95%",cols="2m,1,5<",options="header",align="center"] +=== Location Properties === + +.Properties for Simple Location Constraints +[width="95%",cols="2m,1,5 ------- ====== === Symmetrical "Opt-Out" Clusters === indexterm:[Symmetrical Opt-Out Clusters] indexterm:[Cluster Type,Symmetrical Opt-Out] To create an opt-out cluster, start by allowing resources to run anywhere by default: ---- -# crm_attribute --attr-name symmetric-cluster --attr-value true +# crm_attribute --name symmetric-cluster --update true ---- Then start disabling nodes. The following fragment is the equivalent of the above opt-in configuration. .Example set of opt-out location constraints ====== [source,XML] ------- ------- ====== Whether you should choose opt-in or opt-out depends both on your personal preference and the make-up of your cluster. If most of your resources can run on most of the nodes, then an opt-out arrangement is likely to result in a simpler configuration. On the other-hand, if most resources can only run on a small subset of nodes an opt-in configuration might be simpler. [[node-score-equal]] === What if Two Nodes Have the Same Score === If two nodes have the same score, then the cluster will choose one. This choice may seem random and may not be what was intended, however the cluster was not given enough information to know any better. .Example of two resources that prefer two nodes equally ====== [source,XML] ------- ------- ====== In the example above, assuming no other constraints and an inactive cluster, Webserver would probably be placed on sles-1 and Database on sles-2. It would likely have placed Webserver based on the node's uname and Database based on the desire to spread the resource load evenly across the cluster. However other factors can also be involved in more complex configurations. [[s-resource-ordering]] == Specifying in which Order Resources Should Start/Stop == indexterm:[Resource,Constraints,Ordering] indexterm:[Resource,Start Order] indexterm:[Ordering Constraints] The way to specify the order in which resources should start is by creating +rsc_order+ constraints. +=== Ordering Properties === + .Properties of an Ordering Constraint -[width="95%",cols="2m,5<",options="header",align="center"] +[width="95%",cols="1m,1,4 - - + + ------- ====== -Some additional information on ordering constraints can be found in -the document http://clusterlabs.org/doc/Ordering_Explained.pdf[Ordering Explained]. +Because the above example lets +symmetrical+ default to TRUE, ++Webserver+ must be stopped before +Database+ can be stopped, +and +Webserver+ should be stopped before +IP+ +if they both need to be stopped. [[s-resource-colocation]] == Placing Resources Relative to other Resources == indexterm:[Resource,Constraints,Colocation] indexterm:[Resource,Location Relative to other Resources] When the location of one resource depends on the location of another one, we call this colocation. There is an important side-effect of creating a colocation constraint between two resources: it affects the order in which resources are assigned to a node. If you think about it, it's somewhat obvious. You can't place A relative to B unless you know where B is. footnote:[ While the human brain is sophisticated enough to read the constraint in any order and choose the correct one depending on the situation, the cluster is not quite so smart. Yet. ] So when you are creating colocation constraints, it is important to consider whether you should colocate A with B or B with A. -Another thing to keep in mind is that, assuming A is collocated with -B, the cluster will also take into account A's preferences when +Another thing to keep in mind is that, assuming A is colocated with +B, the cluster will take into account A's preferences when deciding which node to choose for B. -For a detailed look at exactly how this occurs, see the -http://www.clusterlabs.org/mediawiki/images/6/61/Colocation_Explained.pdf[Colocation -Explained] document. +For a detailed look at exactly how this occurs, see +http://clusterlabs.org/doc/Colocation_Explained.pdf[Colocation Explained]. -=== Options === +=== Colocation Properties === -.Properties of a Collocation Constraint +.Properties of a Colocation Constraint [width="95%",cols="2m,5<",options="header",align="center"] |========================================================= |Field |Description |id |A unique name for the constraint. indexterm:[id,Colocation Constraints] indexterm:[Constraints,Colocation,id] |rsc -|The colocation source. If the constraint cannot be satisfied, the - cluster may decide not to allow the resource to run at all. +|The name of a resource that should be located relative to +with-rsc+. indexterm:[rsc,Colocation Constraints] indexterm:[Constraints,Colocation,rsc] |with-rsc -|The colocation target. The cluster will decide where to put this - resource first and then decide where to put the resource in the +rsc+ - field. +|The name of the resource used as the colocation target. The cluster will +decide where to put this resource first and then decide where to put +rsc+. indexterm:[with-rsc,Colocation Constraints] indexterm:[Constraints,Colocation,with-rsc] |score -|Positive values indicate the resource should run on the same - node. Negative values indicate the resources should not run on the - same node. Values of \+/- +INFINITY+ change "should" to "must". +|Positive values indicate the resources should run on the same + node. Negative values indicate the resources should run on + different nodes. Values of \+/- +INFINITY+ change "should" to "must". indexterm:[score,Colocation Constraints] indexterm:[Constraints,Colocation,score] |========================================================= === Mandatory Placement === Mandatory placement occurs any time the constraint's score is ++INFINITY+ or +-INFINITY+. In such cases, if the constraint can't be satisfied, then the +rsc+ resource is not permitted to run. For +score=INFINITY+, this includes cases where the +with-rsc+ resource is not active. If you need +resource1+ to always run on the same machine as +resource2+, you would add the following constraint: .An example colocation constraint [source,XML] Remember, because +INFINITY+ was used, if +resource2+ can't run on any of the cluster nodes (for whatever reason) then +resource1+ will not be allowed to run. Alternatively, you may want the opposite... that +resource1+ cannot run on the same machine as +resource2+. In this case use +score="-INFINITY"+ .An example anti-colocation constraint [source,XML] Again, by specifying +-INFINTY+, the constraint is binding. So if the only place left to run is where +resource2+ already is, then +resource1+ may not run anywhere. === Advisory Placement === If mandatory placement is about "must" and "must not", then advisory placement is the "I'd prefer if" alternative. For constraints with scores greater than +-INFINITY+ and less than +INFINITY+, the cluster will try and accommodate your wishes but may ignore them if the alternative is to stop some of the cluster resources. Like in life, where if enough people prefer something it effectively becomes mandatory, advisory colocation constraints can combine with other elements of the configuration to behave as if they were mandatory. .An example advisory-only colocation constraint [source,XML] [[s-resource-sets-ordering]] == Ordering Sets of Resources == A common situation is for an administrator to create a chain of ordered resources, such as: .A chain of ordered resources ====== [source,XML] ------- ------- ====== .Visual representation of the four resources' start order for the above constraints image::images/resource-set.png["Ordered set",width="16cm",height="2.5cm",align="center"] === Ordered Set === To simplify this situation, there is an alternate format for ordering constraints: .A chain of ordered resources expressed as a set ====== [source,XML] ------- ------- ====== [WARNING] ========= Always pay attention to how your tools expose this functionality. In some tools +create set A B+ is *NOT* equivalent to +create A then B+. ========= While the set-based format is not less verbose, it is significantly easier to get right and maintain. It can also be expanded to allow ordered sets of (un)ordered resources. In the example below, +rscA+ and +rscB+ can both start in parallel, as can +rscC+ and +rscD+, however +rscC+ and +rscD+ can only start once _both_ +rscA+ _and_ +rscB+ are active. .Ordered sets of unordered resources ====== [source,XML] ------- ------- ====== .Visual representation of the start order for two ordered sets of unordered resources image::images/two-sets.png["Two ordered sets",width="13cm",height="7.5cm",align="center"] Of course either set -- or both sets -- of resources can also be internally ordered (by setting +sequential="true"+) and there is no limit to the number of sets that can be specified. .Advanced use of set ordering - Three ordered sets, two of which are internally unordered ====== [source,XML] ------- ------- ====== .Visual representation of the start order for the three sets defined above image::images/three-sets.png["Three ordered sets",width="16cm",height="7.5cm",align="center"] === Resource Set OR Logic === The unordered set logic discussed so far has all been "AND" logic. To illustrate this take the 3 resource set figure in the previous section. -Those sets can be expressed, +(A and B) then (C) then (D) then (E and F)+ +Those sets can be expressed, +(A and B) then \(C) then (D) then (E and F)+. -Say for example we want change the first set, (A and B), to use "OR" logic -so the sets look like this, +(A or B) then (C) then (D) then (E and F)+. +Say for example we want to change the first set, +(A and B)+, to use "OR" logic +so the sets look like this: +(A or B) then \(C) then (D) then (E and F)+. This functionality can be achieved through the use of the +require-all+ option. By default this option is 'require-all=true' which is why the "AND" logic is used by default. Changing +require-all=false+ means only one resource in the set needs to be started before continuing on to the next set. Note that the 'require-all=false' option only makes sense to use in conjunction with unordered sets, 'sequential=false'. Think of it like this, 'sequential=false' modifies the set to be an unordered set that uses "AND" logic by default, by adding 'require-all=false' the unordered set's "AND" logic is flipped to "OR" logic. .Resource Set "OR" logic. Three ordered sets, where the first set is internally unordered with "OR" logic. ====== [source,XML] ------- ------- ====== [[s-resource-sets-colocation]] -== Collocating Sets of Resources == +== Colocating Sets of Resources == Another common situation is for an administrator to create a set of -collocated resources. Previously this was possible either by defining -a resource group (See <>) which could not always -accurately express the design; or by defining each relationship as an -individual constraint, causing a constraint explosion as the number of -resources and combinations grew. +colocated resources. + +One way to do this would be to define a resource group (see +<>), but that cannot always accurately express the desired +state. + +Another way would be to define each relationship as an individual constraint, +but that causes a constraint explosion as the number of resources and +combinations grow. An example of this approach: -.A chain of collocated resources +.Chain of colocated resources ====== [source,XML] ------- - - - + + + ------- ====== To make things easier, we allow an alternate form of colocation -constraints using +resource_sets+. Just like the expanded version, a -resource that can't be active also prevents any resource that must be -collocated with it from being active. For example, if +B+ was not -able to run, then both +C+ (and by inference +D+) must also remain -stopped. +constraints using +resource_set+. As with the chained version, a +resource that can't be active prevents any resource that must be +colocated with it from being active. For example, if +C+ is not +able to run, then both +B+ and by inference +A+ must also remain +stopped. Here is an example +resource_set+: -.The equivalent colocation chain expressed using +resource_sets+ +.Equivalent colocation chain expressed using +resource_set+ ====== [source,XML] ------- - + ------- ====== [WARNING] ========= Always pay attention to how your tools expose this functionality. In some tools +create set A B+ is *NOT* equivalent to +create A with B+. ========= .A group resource with the equivalent colocation rules [source,XML] ------- ------- This notation can also be used in this context to tell the cluster that a set of resources must all be located with a common peer, but have no dependencies on each other. In this scenario, unlike the previous, +B would+ be allowed to remain active even if +A or+ +C+ (or both) were inactive. .Using colocation sets to specify a common peer. ====== [source,XML] ------- - + - + ------- ====== Of course there is no limit to the number and size of the sets used. The only thing that matters is that in order for any member of set N to be active, all the members of set N+1 must also be active (and naturally on the same node); and if a set has +sequential="true"+, then in order for member M to be active, member M+1 must also be active. You can even specify the role in which the members of a set must be in using the set's role attribute. .A colocation chain where the members of the middle set have no inter-dependencies and the last has master status. ====== [source,XML] ------- - + - + - + ------- ====== .Visual representation of a colocation chain where the members of the middle set have no inter-dependencies image::images/three-sets-complex.png["Colocation chain",width="16cm",height="9cm",align="center"] diff --git a/doc/Pacemaker_Explained/en-US/Ch-Nodes.txt b/doc/Pacemaker_Explained/en-US/Ch-Nodes.txt index cc4add1c65..54ee9abf48 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Nodes.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Nodes.txt @@ -1,223 +1,224 @@ = Cluster Nodes = == Defining a Cluster Node == Each node in the cluster will have an entry in the nodes section containing its UUID, uname, and type. .Example Heartbeat cluster node entry ====== [source,XML] ====== .Example Corosync cluster node entry ====== [source,XML] ====== In normal circumstances, the admin should let the cluster populate this information automatically from the communications and membership data. However for Heartbeat, one can use the `crm_uuid` tool to read an existing UUID or define a value before the cluster starts. [[s-node-name]] == Where Pacemaker Gets the Node Name == Traditionally, Pacemaker required nodes to be referred to by the value returned by `uname -n`. This can be problematic for services that require the `uname -n` to be a specific value (ie. for a licence file). Since version 2.0.0 of Pacemaker, this requirement has been relaxed for clusters using Corosync 2.0 or later. The name Pacemaker uses is: . The value stored in 'corosync.conf' under +ring0_addr+ in the +nodelist+, if it does not contain an IP address; otherwise . The value stored in 'corosync.conf' under +name+ in the +nodelist+; otherwise . The value of `uname -n` Pacemaker provides the `crm_node -n` command which displays the name used by a running cluster. If a Corosync nodelist is used, `crm_node --name-for-id $number` is also available to display the name used by the node with the corosync +nodeid+ of '$number', for example: `crm_node --name-for-id 2`. [[s-node-attributes]] == Describing a Cluster Node == indexterm:[Node,attribute] Beyond the basic definition of a node the administrator can also describe the node's attributes, such as how much RAM, disk, what OS or kernel version it has, perhaps even its physical location. This information can then be used by the cluster when deciding where to place resources. For more information on the use of node attributes, see <>. Node attributes can be specified ahead of time or populated later, when the cluster is running, using `crm_attribute`. Below is what the node's definition would look like if the admin ran the command: .The result of using crm_attribute to specify which kernel pcmk-1 is running ====== ------- -# crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --attr-value `uname -r` +# crm_attribute --type nodes --node pcmk-1 --name kernel --update $(uname -r) ------- [source,XML] ------- - + ------- ====== A simpler way to determine the current value of an attribute is to use `crm_attribute` command again: ---- -# crm_attribute --type nodes --node-uname pcmk-1 --attr-name kernel --get-value +# crm_attribute --type nodes --node pcmk-1 --name kernel --query +scope=nodes name=kernel value=3.10.0-123.13.2.el7.x86_64 ---- By specifying `--type nodes` the admin tells the cluster that this attribute is persistent. There are also transient attributes which are kept in the status section which are "forgotten" whenever the node rejoins the cluster. The cluster uses this area to store a record of how many times a resource has failed on that node but administrators can also read and write to this section by specifying `--type status`. == Corosync == === Adding a New Corosync Node === indexterm:[Corosync,Add Cluster Node] indexterm:[Add Cluster Node,Corosync] Adding a new node is as simple as installing Corosync and Pacemaker, and copying '/etc/corosync/corosync.conf' and '/etc/corosync/authkey' (if it exists) from an existing node. You may need to modify the +mcastaddr+ option to match the new node's IP address. If a log message containing "Invalid digest" appears from Corosync, the keys are not consistent between the machines. === Removing a Corosync Node === indexterm:[Corosync,Remove Cluster Node] indexterm:[Remove Cluster Node,Corosync] Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for corosync to forget about the node (_pcmk-1_ in the example below). On the host to be removed: . Stop the cluster: `/etc/init.d/corosync stop` Next, from one of the remaining active cluster nodes: . Tell Pacemaker to forget about the removed host: + ---- # crm_node -R pcmk-1 ---- + This includes deleting the node from the CIB [NOTE] ====== This proceedure only works for versions after 1.1.8 ====== === Replacing a Corosync Node === indexterm:[Corosync,Replace Cluster Node] indexterm:[Replace Cluster Node,Corosync] The five-step guide to replacing an existing cluster node: . Make sure the old node is completely stopped . Give the new machine the same hostname and IP address as the old one . Install the cluster software :-) . Copy '/etc/corosync/corosync.conf' and '/etc/corosync/authkey' (if it exists) to the new node . Start the new cluster node If a log message containing "Invalid digest" appears from Corosync, the keys are not consistent between the machines. == CMAN == === Adding a New CMAN Node === indexterm:[CMAN,Add Cluster Node] indexterm:[Add Cluster Node,CMAN] === Removing a CMAN Node === indexterm:[CMAN,Remove Cluster Node] indexterm:[Remove Cluster Node,CMAN] == Heartbeat == === Adding a New Heartbeat Node === indexterm:[Heartbeat,Add Cluster Node] indexterm:[Add Cluster Node,Heartbeat] Provided you specified +autojoin any+ in 'ha.cf', adding a new node is as simple as installing heartbeat and copying 'ha.cf' and 'authkeys' from an existing node. If you don't want to use +autojoin+, then after setting up 'ha.cf' and 'authkeys', you must use `hb_addnode` before starting the new node. === Removing a Heartbeat Node === indexterm:[Heartbeat,Remove Cluster Node] indexterm:[Remove Cluster Node,Heartbeat] Because the messaging and membership layers are the authoritative source for cluster nodes, deleting them from the CIB is not a reliable solution. First one must arrange for Heartbeat to forget about the node (pcmk-1 in the example below). On the host to be removed: . Stop the cluster: `/etc/init.d/corosync stop` Next, from one of the remaining active cluster nodes: . Tell Heartbeat the node should be removed ---- # hb_delnode pcmk-1 ---- . Tell Pacemaker to forget about the removed host: ---- # crm_node -R pcmk-1 ---- [NOTE] ====== This proceedure only works for versions after 1.1.8 ====== === Replacing a Heartbeat Node === indexterm:[Heartbeat,Replace Cluster Node] indexterm:[Replace Cluster Node,Heartbeat] The seven-step guide to replacing an existing cluster node: . Make sure the old node is completely stopped . Give the new machine the same hostname as the old one . Go to an active cluster node and look up the UUID for the old node in '/var/lib/heartbeat/hostcache' . Install the cluster software . Copy 'ha.cf' and 'authkeys' to the new node . On the new node, populate it's UUID using `crm_uuid -w` and the UUID from step 2 . Start the new cluster node diff --git a/doc/Pacemaker_Explained/en-US/Ch-Notifications.txt b/doc/Pacemaker_Explained/en-US/Ch-Notifications.txt index 13b835d4f7..fdad43c64f 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Notifications.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Notifications.txt @@ -1,138 +1,138 @@ = Receiving Notification for Cluster Events = //// -We prefer [[ch-notifications]], but older versions of asciidoc dont deal well +We prefer [[ch-notifications]], but older versions of asciidoc don't deal well with that construct for chapter headings //// anchor:ch-notifications[Chapter 7, Receiving Notification for Cluster Events] indexterm:[Resource,Notification] A Pacemaker cluster is an event driven system. In this context, an event is a resource failure or configuration change (not exhaustive). The +ocf:pacemaker:ClusterMon+ resource can monitor the cluster status and triggers alerts on each cluster event. This resource runs +crm_mon+ in the background at regular intervals (configurable) and uses +crm_mon+ capabilities to send emails (SMTP), SNMP traps or to execute an external program via the +extra_options+ parameter. [NOTE] ===== Depending on your system settings and compilation settings, SNMP or email alerts might be unavailable. Check +crm_mon --help+ output to see if these options are available to you. In any case, executing an external agent will always be available, and you can have this agent to send emails, SNMP traps, or whatever action you develop. ===== [[s-notification-snmp]] == Configuring SNMP Notifications == indexterm:[Resource,Notification,SNMP] Requires an IP to send SNMP traps to, and a SNMP community. Pacemaker MIB is found in _/usr/share/snmp/mibs/PCMK-MIB.txt_ .Configuring ClusterMon to send SNMP traps ===== [source,XML] ----- ----- ===== [[s-notification-email]] == Configuring Email Notifications == indexterm:[Resource,Notification,SMTP,Email] Requires a user to send mail alerts to. "Mail-From", SMTP relay and Subject prefix can also be configured. .Configuring ClusterMon to send email alerts ===== [source,XML] ----- ----- ===== [[s-notification-external]] == Configuring Notifications via External-Agent == Requires a program (external-agent) to run when resource operations take place, and an external-recipient (IP address, Email address, URI). When triggered, the external-agent is fed with dynamically filled environnement variables describing precisely the cluster event that occurred. By making smart usage of these variables in your external-agent code, you can trigger any action. .Configuring ClusterMon to execute an external-agent ===== [source,XML] ----- ----- ===== .Environment Variables Passed to the External Agent [width="95%",cols="1m,2<",options="header",align="center"] |========================================================= |Environment Variable |Description |CRM_notify_recipient | The static external-recipient from the resource definition. indexterm:[Environment Variable,CRM_notify_recipient] |CRM_notify_node | The node on which the status change happened. indexterm:[Environment Variable,CRM_notify_node] |CRM_notify_rsc | The name of the resource that changed the status. indexterm:[Environment Variable,CRM_notify_rsc] |CRM_notify_task | The operation that caused the status change. indexterm:[Environment Variable,CRM_notify_task] |CRM_notify_desc | The textual output relevant error code of the operation (if any) that caused the status change. indexterm:[Environment Variable,CRM_notify_desc] |CRM_notify_rc | The return code of the operation. indexterm:[Environment Variable,CRM_notify_rc] |CRM_notify_target_rc | The expected return code of the operation. indexterm:[Environment Variable,CRM_notify_target_rc] |CRM_notify_status | The numerical representation of the status of the operation. indexterm:[Environment Variable,CRM_notify_target_rc] |========================================================= diff --git a/doc/Pacemaker_Explained/en-US/Ch-Options.txt b/doc/Pacemaker_Explained/en-US/Ch-Options.txt index 6f9eecda05..3b99fdec52 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Options.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Options.txt @@ -1,393 +1,398 @@ = Cluster Options = -== Special Options == +== CIB Properties == -The reason for these fields to be placed at the top level instead of -with the rest of cluster options is simply a matter of parsing. These -options are used by the configuration database which is, by design, -mostly ignorant of the content it holds. So the decision was made to -place them in an easy to find location. +Certain settings are defined by CIB properties (that is, attributes of the ++cib+ tag) rather than with the rest of the cluster configuration in the ++configuration+ section. -== Configuration Version == +The reason is simply a matter of parsing. These options are used by the +configuration database which is, by design, mostly ignorant of the content it +holds. So the decision was made to place them in an easy-to-find location. -indexterm:[Configuration Version,Cluster] -indexterm:[Cluster,Option,Configuration Version] - -When a node joins the cluster, the cluster will perform a check to see -who has the best configuration based on the fields below. It then -asks the node with the highest (+admin_epoch+, +epoch+, +num_updates+) -tuple to replace the configuration on all the nodes - which makes -setting them, and setting them correctly, very important. - -.Configuration Version Properties +.CIB Properties [width="95%",cols="2m,5<",options="header",align="center"] |========================================================= |Field |Description | admin_epoch | +indexterm:[Configuration Version,Cluster] +indexterm:[Cluster,Option,Configuration Version] indexterm:[admin_epoch,Cluster Option] indexterm:[Cluster,Option,admin_epoch] -Never modified by the cluster. Use this to make the configurations on -any inactive nodes obsolete. - -_Never set this value to zero_, in such cases the cluster cannot tell -the difference between your configuration and the "empty" one used -when nothing is found on disk. +When a node joins the cluster, the cluster performs a check to see +which node has the best configuration. It asks the node with the highest +(+admin_epoch+, +epoch+, +num_updates+) tuple to replace the configuration on +all the nodes -- which makes setting them, and setting them correctly, very +important. +admin_epoch+ is never modified by the cluster; you can use this +to make the configurations on any inactive nodes obsolete. _Never set this +value to zero_. In such cases, the cluster cannot tell the difference between +your configuration and the "empty" one used when nothing is found on disk. | epoch | indexterm:[epoch,Cluster Option] indexterm:[Cluster,Option,epoch] -Incremented every time the configuration is updated (usually by the admin) +The cluster increments this every time the configuration is updated (usually by +the administrator). | num_updates | indexterm:[num_updates,Cluster Option] indexterm:[Cluster,Option,num_updates] -Incremented every time the configuration or status is updated (usually by the cluster) - -|========================================================= - -== Other Fields == -.Properties Controlling Validation -[width="95%",cols="2m,5<",options="header",align="center"] -|========================================================= -|Field |Description +The cluster increments this every time the configuration or status is updated +(usually by the cluster) and resets it to 0 when epoch changes. | validate-with | indexterm:[validate-with,Cluster Option] indexterm:[Cluster,Option,validate-with] -Determines the type of validation being done on the configuration. If -set to "none", the cluster will not verify that updates conform to the +Determines the type of XML validation that will be done on the configuration. +If set to +none+, the cluster will not verify that updates conform to the DTD (nor reject ones that don't). This option can be useful when -operating a mixed version cluster during an upgrade. - -|========================================================= - -== Fields Maintained by the Cluster == - -.Properties Maintained by the Cluster -[width="95%",cols="2m,5<",options="header",align="center"] -|========================================================= -|Field |Description +operating a mixed-version cluster during an upgrade. |cib-last-written | indexterm:[cib-last-written,Cluster Property] indexterm:[Cluster,Property,cib-last-written] -Indicates when the configuration was last written to disk. Informational purposes only. - -|dc-uuid | -indexterm:[dc-uuid,Cluster Property] -indexterm:[Cluster,Property,dc-uuid] -Indicates which cluster node is the current leader. Used by the -cluster when placing resources and determining the order of some -events. +Indicates when the configuration was last written to disk. Maintained by the +cluster; for informational purposes only. |have-quorum | indexterm:[have-quorum,Cluster Property] indexterm:[Cluster,Property,have-quorum] Indicates if the cluster has quorum. If false, this may mean that the -cluster cannot start resources or fence other nodes. See -+no-quorum-policy+ below. - -| dc-version | -indexterm:[dc-version,Cluster Property] -indexterm:[Cluster,Property,dc-version] -Version of Pacemaker on the cluster's DC. - -Often includes the hash which identifies the exact Git changeset it -was built from. Used for diagnostic purposes. - -| cluster-infrastructure | -indexterm:[cluster-infrastructure,Cluster Property] -indexterm:[Cluster,Property,cluster-infrastructure] -The messaging stack on which Pacemaker is currently running. -Used for informational and diagnostic purposes. - -| expected-quorum-votes | -indexterm:[expected-quorum-votes,Cluster Property] -indexterm:[Cluster,Property,expected-quorum-votes] -The number of nodes expected to be in the cluster +cluster cannot start resources or fence other nodes (see ++no-quorum-policy+ below). Maintained by the cluster. -Used to calculate quorum in Corosync 1.x (not CMAN) based clusters. +|dc-uuid | +indexterm:[dc-uuid,Cluster Property] +indexterm:[Cluster,Property,dc-uuid] +Indicates which cluster node is the current leader. Used by the +cluster when placing resources and determining the order of some +events. Maintained by the cluster. |========================================================= -Note that although these fields can be written to by the admin, in +=== Working with CIB Properties === + +Although these fields can be written to by the user, in most cases the cluster will overwrite any values specified by the admin with the "correct" ones. To change the +admin_epoch+, for example, one would use: ---- # cibadmin --modify --crm_xml '' ---- -A complete set of fields will look something like this: +A complete set of CIB properties will look something like this: -.An example of the fields set for a cib object +.Attributes set for a cib object ====== [source,XML] ------- - + ------- ====== == Cluster Options == Cluster options, as you might expect, control how the cluster behaves when confronted with certain situations. -They are grouped into sets and, in advanced configurations, there may -be more than one. -footnote:[This will be described later in the section on -<> where we will show how to have the cluster use -different sets of options during working hours (when downtime is -usually to be avoided at all costs) than it does during the weekends -(when resources can be moved to the their preferred hosts without -bothering end users)] -For now we will describe the simple case where each option is present at most once. - -== Available Cluster Options == +They are grouped into sets within the +crm_config+ section, and, in advanced +configurations, there may be more than one set. (This will be described later +in the section on <> where we will show how to have the cluster use +different sets of options during working hours than during weekends.) For now, +we will describe the simple case where each option is present at most once. + +You can obtain an up-to-date list of cluster options, including +their default values, by running the `man pengine` and `man crmd` commands. + .Cluster Options -[width="95%",cols="5m,2,11<",options="header",align="center"] +[width="95%",cols="5m,2,11>). -| pe-error-series-max | -1 (all) | -indexterm:[pe-error-series-max,Cluster Option] -indexterm:[Cluster,Option,pe-error-series-max] -The number of PE inputs resulting in ERRORs to save. Used when reporting problems. - -| pe-warn-series-max | -1 (all) | -indexterm:[pe-warn-series-max,Cluster Option] -indexterm:[Cluster,Option,pe-warn-series-max] -The number of PE inputs resulting in WARNINGs to save. Used when reporting problems. - -| pe-input-series-max | -1 (all) | -indexterm:[pe-input-series-max,Cluster Option] -indexterm:[Cluster,Option,pe-input-series-max] -The number of "normal" PE inputs to save. Used when reporting problems. - -|default-resource-stickiness | 0 | -indexterm:[default-resource-stickiness,Cluster Option] -indexterm:[Cluster,Option,default-resource-stickiness] -+Deprecated:+ See <> instead - -| is-managed-default | TRUE | -indexterm:[is-managed-default,Cluster Option] -indexterm:[Cluster,Option,is-managed-default] -+Deprecated:+ See <> instead +| enable-startup-probes | TRUE | +indexterm:[enable-startup-probes,Cluster Option] +indexterm:[Cluster,Option,enable-startup-probes] +Should the cluster check for active resources during startup? | maintenance-mode | FALSE | indexterm:[maintenance-mode,Cluster Option] indexterm:[Cluster,Option,maintenance-mode] -Should the cluster monitor resources and start/stop them as required +Should the cluster refrain from monitoring, starting and stopping resources? + +| stonith-enabled | TRUE | +indexterm:[stonith-enabled,Cluster Option] +indexterm:[Cluster,Option,stonith-enabled] +Should failed nodes and nodes with resources that can't be stopped be +shot? If you value your data, set up a STONITH device and enable this. + +If true, or unset, the cluster will refuse to start resources unless +one or more STONITH resources have been configured. + +| stonith-action | reboot | +indexterm:[stonith-action,Cluster Option] +indexterm:[Cluster,Option,stonith-action] +Action to send to STONITH device. Allowed values are +reboot+ and +off+. +The value +poweroff+ is also allowed, but is only used for +legacy devices. | stonith-timeout | 60s | indexterm:[stonith-timeout,Cluster Option] indexterm:[Cluster,Option,stonith-timeout] -How long to wait for the STONITH action to complete +How long to wait for STONITH actions to complete -| default-action-timeout | 20s | -indexterm:[default-action-timeout,Cluster Option] -indexterm:[Cluster,Option,default-action-timeout] -+Deprecated:+ See <> instead +| cluster-delay | 60s | +indexterm:[cluster-delay,Cluster Option] +indexterm:[Cluster,Option,cluster-delay] +Estimated maximum round-trip delay over the network (excluding action +execution). If the TE requires an action to be executed on another node, +it will consider the action failed if it does not get a response +from the other node in this time (after considering the action's +own timeout). The "correct" value will depend on the speed and load of your +network and cluster nodes. | dc-deadtime | 20s | indexterm:[dc-deadtime,Cluster Option] indexterm:[Cluster,Option,dc-deadtime] How long to wait for a response from other nodes during startup. The "correct" value will depend on the speed/load of your network and the type of switches used. | cluster-recheck-interval | 15min | indexterm:[cluster-recheck-interval,Cluster Option] indexterm:[Cluster,Option,cluster-recheck-interval] -Polling interval for time based changes to options, resource parameters and constraints. +Polling interval for time-based changes to options, resource parameters and constraints. + +The Cluster is primarily event-driven, but your configuration can have +elements that take effect based on the time of day. To ensure these changes +take effect, we can optionally poll the cluster's status for changes. A value +of 0 disables polling. Positive values are an interval (in seconds unless other +SI units are specified, e.g. 5min). -The Cluster is primarily event driven, however the configuration can have elements that change based on time. To ensure these changes take effect, we can optionally poll the cluster's status for changes. +| pe-error-series-max | -1 | +indexterm:[pe-error-series-max,Cluster Option] +indexterm:[Cluster,Option,pe-error-series-max] +The number of PE inputs resulting in ERRORs to save. Used when reporting problems. +A value of -1 means unlimited (report all). + +| pe-warn-series-max | -1 | +indexterm:[pe-warn-series-max,Cluster Option] +indexterm:[Cluster,Option,pe-warn-series-max] +The number of PE inputs resulting in WARNINGs to save. Used when reporting problems. +A value of -1 means unlimited (report all). -Allowed values: Zero disables polling. Positive values are an interval in seconds (unless other SI units are specified. eg. 5min) +| pe-input-series-max | -1 | +indexterm:[pe-input-series-max,Cluster Option] +indexterm:[Cluster,Option,pe-input-series-max] +The number of "normal" PE inputs to save. Used when reporting problems. +A value of -1 means unlimited (report all). + +| remove-after-stop | FALSE | +indexterm:[remove-after-stop,Cluster Option] +indexterm:[Cluster,Option,remove-after-stop] +_Advanced Use Only:_ Should the cluster remove resources from the LRM after +they are stopped? Values other than the default are, at best, poorly tested and +potentially dangerous. + +| startup-fencing | TRUE | +indexterm:[startup-fencing,Cluster Option] +indexterm:[Cluster,Option,startup-fencing] +_Advanced Use Only:_ Should the cluster shoot unseen nodes? +Not using the default is very unsafe! | election-timeout | 2min | indexterm:[election-timeout,Cluster Option] indexterm:[Cluster,Option,election-timeout] -+Advanced Use Only+ - -If need to adjust this value, it probably indicates the presence of a bug. +_Advanced Use Only:_ If you need to adjust this value, it probably indicates +the presence of a bug. | shutdown-escalation | 20min | indexterm:[shutdown-escalation,Cluster Option] indexterm:[Cluster,Option,shutdown-escalation] -+Advanced Use Only+ - -If need to adjust this value, it probably indicates the presence of a bug. +_Advanced Use Only:_ If you need to adjust this value, it probably indicates +the presence of a bug. | crmd-integration-timeout | 3min | indexterm:[crmd-integration-timeout,Cluster Option] indexterm:[Cluster,Option,crmd-integration-timeout] -+Advanced Use Only+ - -If need to adjust this value, it probably indicates the presence of a bug. +_Advanced Use Only:_ If you need to adjust this value, it probably indicates +the presence of a bug. | crmd-finalization-timeout | 30min | indexterm:[crmd-finalization-timeout,Cluster Option] indexterm:[Cluster,Option,crmd-finalization-timeout] -+Advanced Use Only+ +_Advanced Use Only:_ If you need to adjust this value, it probably indicates +the presence of a bug. -If need to adjust this value, it probably indicates the presence of a bug. - -| crmd-transition-delay | | +| crmd-transition-delay | 0s | indexterm:[crmd-transition-delay,Cluster Option] indexterm:[Cluster,Option,crmd-transition-delay] -+Advanced Use Only+ Enabling this option will slow down cluster recovery under all conditions. +_Advanced Use Only:_ Delay cluster recovery for the configured interval to +allow for additional/related events to occur. Useful if your configuration is +sensitive to the order in which ping updates arrive. +Enabling this option will slow down cluster recovery under +all conditions. -Delay cluster recovery for the configured interval to allow for additional/related events to occur. Useful if your configuration is sensitive to the order in which ping updates arrive. +|default-resource-stickiness | 0 | +indexterm:[default-resource-stickiness,Cluster Option] +indexterm:[Cluster,Option,default-resource-stickiness] +_Deprecated:_ See <> instead -|========================================================= +| is-managed-default | TRUE | +indexterm:[is-managed-default,Cluster Option] +indexterm:[Cluster,Option,is-managed-default] +_Deprecated:_ See <> instead -You can always obtain an up-to-date list of cluster options, including -their default values, by running the `man pengine` and `man crmd` commands. +| default-action-timeout | 20s | +indexterm:[default-action-timeout,Cluster Option] +indexterm:[Cluster,Option,default-action-timeout] +_Deprecated:_ See <> instead + +|========================================================= == Querying and Setting Cluster Options == indexterm:[Querying,Cluster Option] indexterm:[Setting,Cluster Option] indexterm:[Cluster,Querying Options] indexterm:[Cluster,Setting Options] Cluster options can be queried and modified using the `crm_attribute` tool. To get the current value of +cluster-delay+, simply use: ---- -# crm_attribute --attr-name cluster-delay --get-value +# crm_attribute --query --name cluster-delay ---- which is more simply written as ---- -# crm_attribute --get-value -n cluster-delay +# crm_attribute -G -n cluster-delay ---- If a value is found, you'll see a result like this: ---- -# crm_attribute --get-value -n cluster-delay - name=cluster-delay value=60s +# crm_attribute -G -n cluster-delay +scope=crm_config name=cluster-delay value=60s ---- However, if no value is found, the tool will display an error: ---- -# crm_attribute --get-value -n clusta-deway` -name=clusta-deway value=(null) -Error performing operation: The object/attribute does not exist +# crm_attribute -G -n clusta-deway +scope=crm_config name=clusta-deway value=(null) +Error performing operation: No such device or address ---- To use a different value, eg. +30+, simply run: ---- -# crm_attribute --attr-name cluster-delay --attr-value 30s +# crm_attribute --name cluster-delay --update 30s ---- To go back to the cluster's default value you can delete the value, for example with this command: ---- -# crm_attribute --attr-name cluster-delay --delete-attr +# crm_attribute --name cluster-delay --delete +Deleted crm_config option: id=cib-bootstrap-options-cluster-delay name=cluster-delay ---- == When Options are Listed More Than Once == If you ever see something like the following, it means that the option you're modifying is present more than once. .Deleting an option that is listed twice ======= ------ -# crm_attribute --attr-name batch-limit --delete-attr +# crm_attribute --name batch-limit --delete Multiple attributes match name=batch-limit in crm_config: Value: 50 (set=cib-bootstrap-options, id=cib-bootstrap-options-batch-limit) Value: 100 (set=custom, id=custom-batch-limit) -Please choose from one of the matches above and supply the 'id' with --attr-id +Please choose from one of the matches above and supply the 'id' with --id ------- ======= In such cases follow the on-screen instructions to perform the requested action. To determine which value is currently being used by the cluster, please refer to <>. diff --git a/doc/Pacemaker_Explained/en-US/Ch-Resources.txt b/doc/Pacemaker_Explained/en-US/Ch-Resources.txt index 784ef720ad..a40c2344f4 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Resources.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Resources.txt @@ -1,718 +1,740 @@ = Cluster Resources = == What is a Cluster Resource == indexterm:[Resource] The role of a resource agent is to abstract the service it provides and present a consistent view to the cluster, which allows the cluster to be agnostic about the resources it manages. The cluster doesn't need to understand how the resource works because it relies on the resource agent to do the right thing when given a +start+, +stop+ or +monitor+ command. For this reason it is crucial that resource agents are well tested. Typically resource agents come in the form of shell scripts, however they can be written using any technology (such as C, Python or Perl) that the author is comfortable with. [[s-resource-supported]] == Supported Resource Classes == indexterm:[Resource,class] There are six classes of agents supported by Pacemaker: * OCF * LSB * Upstart * Systemd * Fencing * Service * Nagios -indexterm:[Resource,Heartbeat] -indexterm:[Heartbeat,Resources] - -Version 1 of Heartbeat came with its own style of resource agents and -it is highly likely that many people have written their own agents -based on its conventions. footnote:[ See -http://wiki.linux-ha.org/HeartbeatResourceAgent for more information ] - -Although deprecated with the release of Heartbeat v2, they were -supported by Pacemaker up until the release of 1.1.8 to enable -administrators to continue to use these agents. - === Open Cluster Framework === indexterm:[Resource,OCF] indexterm:[OCF,Resources] indexterm:[Open Cluster Framework,Resources] The OCF standard footnote:[ http://www.opencf.org/cgi-bin/viewcvs.cgi/specs/ra/resource-agent-api.txt?rev=HEAD - at least as it relates to resource agents. ] footnote:[ The Pacemaker implementation has been somewhat extended from the OCF Specs, but none of those changes are incompatible with the original OCF specification. ] is basically an extension of the Linux Standard Base conventions for init scripts to: * support parameters, * make them self describing and * extensible OCF specs have strict definitions of the exit codes that actions must return. footnote:[ Included with the cluster is the ocf-tester script, which can be useful in this regard. ] The cluster follows these specifications exactly, and giving the wrong exit code will cause the cluster to behave in ways you will likely find puzzling and annoying. In particular, the cluster needs to distinguish a completely stopped resource from one which is in some erroneous and indeterminate state. Parameters are passed to the script as environment variables, with the special prefix +OCF_RESKEY_+. So, a parameter which the user thinks of as ip it will be passed to the script as +OCF_RESKEY_ip+. The number and purpose of the parameters is completely arbitrary, however your script should advertise any that it supports using the +meta-data+ command. The OCF class is the most preferred one as it is an industry standard, highly flexible (allowing parameters to be passed to agents in a non-positional manner) and self-describing. For more information, see the http://www.linux-ha.org/wiki/OCF_Resource_Agents[reference] and <>. === Linux Standard Base === indexterm:[Resource,LSB] indexterm:[LSB,Resources] indexterm:[Linux Standard Base,Resources] LSB resource agents are those found in '/etc/init.d'. Generally they are provided by the OS/distribution and, in order to be used with the cluster, they must conform to the LSB Spec. footnote:[ See http://refspecs.linux-foundation.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html for the LSB Spec (as it relates to init scripts). ] Many distributions claim LSB compliance but ship with broken init scripts. For details on how to check if your init script is LSB-compatible, see <>. The most common problems are: * Not implementing the status operation at all * Not observing the correct exit status codes for start/stop/status actions * Starting a started resource returns an error (this violates the LSB spec) * Stopping a stopped resource returns an error (this violates the LSB spec) === Systemd === indexterm:[Resource,Systemd] indexterm:[Systemd,Resources] Some newer distributions have replaced the old http://en.wikipedia.org/wiki/Init#SysV-style[SYS-V] style of initialization daemons (and scripts) with an alternative called http://www.freedesktop.org/wiki/Software/systemd[Systemd]. Pacemaker is able to manage these services _if they are present_. Instead of +init scripts+, systemd has +unit files+. Generally the services (or unit files) are provided by the OS/distribution but there are some instructions for converting from init scripts at: http://0pointer.de/blog/projects/systemd-for-admins-3.html [NOTE] ====== Remember to make sure the computer is +not+ configured to start any services at boot time that should be controlled by the cluster. ====== === Upstart === indexterm:[Resource,Upstart] indexterm:[Upstart,Resources] Some newer distributions have replaced the old http://en.wikipedia.org/wiki/Init#SysV-style[SYS-V] style of initialization daemons (and scripts) with an alternative called http://upstart.ubuntu.com[Upstart]. Pacemaker is able to manage these services _if they are present_. Instead of +init scripts+, upstart has +jobs+. Generally the services (or jobs) are provided by the OS/distribution. [NOTE] ====== Remember to make sure the computer is +not+ configured to start any services at boot time that should be controlled by the cluster. ====== === System Services === indexterm:[Resource,System Services] indexterm:[System Service,Resources] Since there are now many "common" types of system services (+systemd+, +upstart+, and +lsb+), Pacemaker supports a special alias which intelligently figures out which one applies to a given cluster node. This is particularly useful when the cluster contains a mix of +systemd+, +upstart+, and +lsb+. In order, Pacemaker will try to find the named service as: . an LSB (SYS-V) init script . a Systemd unit file . an Upstart job === STONITH === indexterm:[Resource,STONITH] indexterm:[STONITH,Resources] There is also an additional class, STONITH, which is used exclusively for fencing related resources. This is discussed later in <>. === Nagios Plugins === indexterm:[Resource,Nagios Plugins] indexterm:[Nagios Plugins,Resources] Nagios plugins allow us to monitor services on the remote hosts. http://nagiosplugins.org[Nagios Plugins]. Pacemaker is able to do remote monitoring with the plugins _if they are present_. -An use case is to configure them as resources belonging to a resource -container, which usually is a VM, and the container will be restarted -if any of them has failed. While they can also be configured as ordinary -resources to be just used for monitoring hosts or services via network. +A common use case is to configure them as resources belonging to a resource +container (usually a virtual machine), and the container will be restarted +if any of them has failed. Another use is to configure them as ordinary +resources to be used for monitoring hosts or services via the network. The supported parameters are same as the long options of a nagios plugin. [[primitive-resource]] == Resource Properties == These values tell the cluster which script to use for the resource, where to find that script and what standards it conforms to. .Properties of a Primitive Resource [width="95%",cols="1m,6<",options="header",align="center"] |========================================================= |Field |Description |id |Your name for the resource indexterm:[id,Resource] indexterm:[Resource,Property,id] |class -|The standard the script conforms to. Allowed values: +ocf+, - +service+, +upstart+, +systemd+, +lsb+, +stonith+ +|The standard the resource agent conforms to. Allowed values: ++lsb+, +nagios+, +ocf+, +service+, +stonith+, +systemd+, +upstart+ indexterm:[class,Resource] indexterm:[Resource,Property,class] |type -|The name of the Resource Agent you wish to use. Eg. _IPaddr_ or _Filesystem_ +|The name of the Resource Agent you wish to use. Eg. +IPaddr+ or +Filesystem+ indexterm:[type,Resource] indexterm:[Resource,Property,type] |provider |The OCF spec allows multiple vendors to supply the same - ResourceAgent. To use the OCF resource agents supplied with - Heartbeat, you should specify +heartbeat+ here. + resource agent. To use the OCF resource agents supplied by + the Heartbeat project, you would specify +heartbeat+ here. indexterm:[provider,Resource] indexterm:[Resource,Property,provider] |========================================================= Resource definitions can be queried with the `crm_resource` tool. For example ---- # crm_resource --resource Email --query-xml ---- might produce: .An example system resource ===== [source,XML] ===== [NOTE] ===== One of the main drawbacks to system services (such as LSB, Systemd and Upstart) resources is that they do not allow any parameters! ===== -.An example OCF resource +//// +See https://tools.ietf.org/html/rfc5737 for choice of example IP address +//// + +.An OCF resource definition ===== [source,XML] ------- - - + + ------- ===== [[s-resource-options]] == Resource Options == -Options are used by the cluster to decide how your resource should +Resources have two types of options: 'meta-attributes' and 'instance attributes'. +Meta-attributes apply to any type of resource, while instance attributes +are specific to each resource agent. + +=== Resource Meta-Attributes === + +Meta-attributes are used by the cluster to decide how a resource should behave and can be easily set using the `--meta` option of the `crm_resource` command. -.Options for a Primitive Resource -[width="95%",cols="1m,1,4<",options="header",align="center"] +.Meta-attributes of a Primitive Resource +[width="95%",cols="2m,2,5> resources, they will not promoted to master) - -* 'Master' - Allow the resource to be started and, if appropriate, promoted +* +master:+ Allow the resource to be started and, if appropriate, promoted indexterm:[target-role,Resource Option] indexterm:[Resource,Option,target-role] |is-managed -|+TRUE+ +|TRUE |Is the cluster allowed to start and stop the resource? Allowed values: +true+, +false+ indexterm:[is-managed,Resource Option] indexterm:[Resource,Option,is-managed] |resource-stickiness -|Calculated -|How much does the resource prefer to stay where it is? Defaults to - the value of +resource-stickiness+ in the +rsc_defaults+ section +|value of +resource-stickiness+ in the +rsc_defaults+ section +|How much does the resource prefer to stay where it is? indexterm:[resource-stickiness,Resource Option] indexterm:[Resource,Option,resource-stickiness] |requires -|Calculated -|Under what conditions can the resource be started. ('Since 1.1.8') - - Defaults to +fencing+ unless +stonith-enabled+ is 'false' or +class+ - is 'stonith' - under those conditions the default is +quorum+. - Possible values: - - * 'nothing' - can always be started - - * 'quorum' - The cluster can only start this resource if a majority of - the configured nodes are active - - * 'fencing' - The cluster can only start this resource if a majority - of the configured nodes are active _and_ any failed or unknown nodes - have been powered off. - - * 'unfencing' - The cluster can only start this resource if a majority - of the configured nodes are active _and_ any failed or unknown nodes - have been powered off _and_ only on nodes that have been 'unfenced' - indexterm: Option[requires,Resource] - indexterm:[Resource,Option,requires] +|fencing (unless +stonith-enabled+ is +false+ or +class+ is ++stonith+, in which case it defaults to quorum) +|Conditions under which the resource can be started ('Since 1.1.8') +Allowed values: + +* +nothing:+ can always be started +* +quorum:+ The cluster can only start this resource if a majority of + the configured nodes are active +* +fencing:+ The cluster can only start this resource if a majority + of the configured nodes are active _and_ any failed or unknown nodes + have been powered off +* +unfencing:+ The cluster can only start this resource if a majority + of the configured nodes are active _and_ any failed or unknown nodes + have been powered off _and_ only on nodes that have been 'unfenced' + +indexterm:[requires,Resource Option] +indexterm:[Resource,Option,requires] |migration-threshold -|+INFINITY+ (disabled) +|INFINITY |How many failures may occur for this resource on a node, before this - node is marked ineligible to host this resource. + node is marked ineligible to host this resource. A value of INFINITY + indicates that this feature is disabled. indexterm:[migration-threshold,Resource Option] indexterm:[Resource,Option,migration-threshold] |failure-timeout -|+0+ (disabled) +|0 |How many seconds to wait before acting as if the failure had not occurred, and potentially allowing the resource back to the node on - which it failed. + which it failed. A value of 0 indicates that this feature is disabled. indexterm:[failure-timeout,Resource Option] indexterm:[Resource,Option,failure-timeout] |multiple-active -|+stop_start+ +|stop_start |What should the cluster do if it ever finds the resource active on - more than one node. Allowed values: + more than one node? Allowed values: -* 'block' - mark the resource as unmanaged - -* 'stop_only' - stop all active instances and leave them that way - -* 'stop_start' - stop all active instances and start the resource in +* +block:+ mark the resource as unmanaged +* +stop_only:+ stop all active instances and leave them that way +* +stop_start:+ stop all active instances and start the resource in one location only indexterm:[multiple-active,Resource Option] indexterm:[Resource,Option,multiple-active] |remote-node -|++ (disabled) -|The name of the remote-node this resource defines. This both enables the resource as a remote-node and defines the unique name used to identify the remote-node. If no other parameters are set, this value will also be assumed as the hostname to connect to at port 3121. +WARNING+ This value cannot overlap with any resource or node IDs. +| +|The name of the remote-node this resource defines. This both enables the +resource as a remote-node and defines the unique name used to identify the +remote-node. If no other parameters are set, this value will also be assumed as +the hostname to connect to at the port specified by +remote-port+. +WARNING:+ +This value cannot overlap with any resource or node IDs. If not specified, +this feature is disabled. |remote-port -|+3121+ -|Configure a custom port to use for the guest connection to pacemaker_remote. +|3121 +|Port to use for the guest connection to pacemaker_remote |remote-addr -|+remote-node+ value used as hostname -|The ip address or hostname to connect to if remote-node's name is not the hostname of the guest. +|value of +remote-node+ +|The IP address or hostname to connect to if remote-node's name is not the +hostname of the guest. |+remote-connect-timeout+ -|+60s+ +|60s |How long before a pending guest connection will time out. |========================================================= -If you performed the following commands on the previous LSB Email resource +[NOTE] +==== +Support for remote nodes was added in pacemaker 1.1.10. If you are using an +earlier version, options related to remote nodes will not be available. +==== + +As an example of setting resource options, if you performed the following +commands on an LSB Email resource: ------- -# crm_resource --meta --resource Email --set-parameter priority --property-value 100 -# crm_resource --meta --resource Email --set-parameter multiple-active --property-value block +# crm_resource --meta --resource Email --set-parameter priority --parameter-value 100 +# crm_resource -m -r Email -p multiple-active -v block ------- -the resulting resource definition would be +the resulting resource definition might be: .An LSB resource with cluster options ===== [source,XML] ------- - - - - + + + + ------- ===== [[s-resource-defaults]] -== Setting Global Defaults for Resource Options == +=== Setting Global Defaults for Resource Meta-Attributes === To set a default value for a resource option, simply add it to the +rsc_defaults+ section with `crm_attribute`. Thus, ---- -# crm_attribute --type rsc_defaults --attr-name is-managed --attr-value false +# crm_attribute --type rsc_defaults --name is-managed --update false ---- would prevent the cluster from starting or stopping any of the resources in the configuration (unless of course the individual resources were specifically enabled and had +is-managed+ set to +true+). == Instance Attributes == The scripts of some resource classes (LSB not being one of them) can be given parameters which determine how they behave and which instance of a service they control. If your resource agent supports parameters, you can add them with the `crm_resource` command. For instance ---- -# crm_resource --resource Public-IP --set-parameter ip --property-value 1.2.3.4 +# crm_resource --resource Public-IP --set-parameter ip --parameter-value 192.0.2.2 ---- would create an entry in the resource like this: .An example OCF resource with instance attributes ===== [source,XML] ------- - + ------- ===== For an OCF resource, the result would be an environment variable -called +OCF_RESKEY_ip+ with a value of +1.2.3.4+. +called +OCF_RESKEY_ip+ with a value of +192.0.2.2+. The list of instance attributes supported by an OCF script can be found by calling the resource script with the `meta-data` command. The output contains an XML description of all the supported attributes, their purpose and default values. .Displaying the metadata for the Dummy resource agent template ===== ------- # export OCF_ROOT=/usr/lib/ocf # $OCF_ROOT/resource.d/pacemaker/Dummy meta-data ------- [source,XML] ------- - - - 1.0 - - - This is a Dummy Resource Agent. It does absolutely nothing except - keep track of whether its running or not. - Its purpose in life is for testing and to serve as a template for RA writers. - - Dummy resource agent - - - - - Location to store the resource state in. - - State file - - - - - - Dummy attribute that can be changed to cause a reload - - Dummy attribute that can be changed to cause a reload - - - - - - - - - - - - - - - + + +1.0 + + +This is a Dummy Resource Agent. It does absolutely nothing except +keep track of whether its running or not. +Its purpose in life is for testing and to serve as a template for RA writers. + +NB: Please pay attention to the timeouts specified in the actions +section below. They should be meaningful for the kind of resource +the agent manages. They should be the minimum advised timeouts, +but they shouldn't/cannot cover _all_ possible resource +instances. So, try to be neither overly generous nor too stingy, +but moderate. The minimum timeouts should never be below 10 seconds. + +Example stateless resource agent + + + + +Location to store the resource state in. + +State file + + + + + +Fake attribute that can be changed to cause a reload + +Fake attribute that can be changed to cause a reload + + + + + +Number of seconds to sleep during operations. This can be used to test how +the cluster reacts to operation timeouts. + +Operation sleep duration in seconds. + + + + + + + + + + + + + + + + ------- ===== == Resource Operations == indexterm:[Resource,Action] === Monitoring Resources for Failure === By default, the cluster will not ensure your resources are still healthy. To instruct the cluster to do this, you need to add a +monitor+ operation to the resource's definition. .An OCF resource with a recurring health check ===== [source,XML] ------- - + ------- ===== .Properties of an Operation -[width="95%",cols="1m,6<",options="header",align="center"] +[width="95%",cols="2m,3,6 - + ------- ===== -==== Multiple Monitor Operations ==== +=== Multiple Monitor Operations === Provided no two operations (for a single resource) have the same name and interval you can have as many monitor operations as you like. In this way you can do a superficial health check every minute and progressively more intense ones at higher intervals. To tell the resource agent what kind of check to perform, you need to provide each monitor with a different value for a common parameter. The OCF standard creates a special parameter called +OCF_CHECK_LEVEL+ for this purpose and dictates that it is _"made available to the resource agent without the normal +OCF_RESKEY+ prefix"_. Whatever name you choose, you can specify it by adding an +instance_attributes+ block to the op tag. Note that it is up to each resource agent to look for the parameter and decide how to use it. .An OCF resource with two recurring health checks, performing different levels of checks - specified via +OCF_CHECK_LEVEL+. ===== [source,XML] ------- - + ------- ===== -==== Disabling a Monitor Operation ==== +=== Disabling a Monitor Operation === The easiest way to stop a recurring monitor is to just delete it. However, there can be times when you only want to disable it temporarily. In such cases, simply add +enabled="false"+ to the operation's definition. .Example of an OCF resource with a disabled health check ===== [source,XML] ------- - + ------- ===== -This can be achieved from the command-line by executing +This can be achieved from the command line by executing: ---- -# cibadmin -M -X '' +# cibadmin --modify --xml-text '' ---- Once you've done whatever you needed to do, you can then re-enable it with +---- +# cibadmin --modify --xml-text '' +---- diff --git a/doc/Pacemaker_Explained/en-US/Ch-Rules.txt b/doc/Pacemaker_Explained/en-US/Ch-Rules.txt index 4f80983915..12f8eb446b 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Rules.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Rules.txt @@ -1,561 +1,566 @@ = Rules = //// -We prefer [[ch-rules]], but older versions of asciidoc dont deal well +We prefer [[ch-rules]], but older versions of asciidoc don't deal well with that construct for chapter headings //// anchor:ch-rules[Chapter 8, Rules] indexterm:[Resource,Constraint,Rule] Rules can be used to make your configuration more dynamic. One common example is to set one value for +resource-stickiness+ during working hours, to prevent resources from being moved back to their most preferred location, and another on weekends when no-one is around to notice an outage. Another use of rules might be to assign machines to different processing groups (using a node attribute) based on time and to then use that attribute when creating location constraints. Each rule can contain a number of expressions, date-expressions and even other rules. The results of the expressions are combined based on the rule's +boolean-op+ field to determine if the rule ultimately evaluates to +true+ or +false+. What happens next depends on the context in which the rule is being used. +== Rule Properties == + .Properties of a Rule -[width="95%",cols="2m,5<",options="header",align="center"] +[width="95%",cols="2m,1,5<",options="header",align="center"] |========================================================= |Field +|Default |Description |role -|Limits the rule to apply only when the resource is in that - role. Allowed values: _Started_, +Slave,+ and +Master+. NOTE: A rule - with +role="Master"+ can not determine the initial location of a - clone instance. It will only affect which of the active instances +|+started+ +|Limits the rule to apply only when the resource is in the specified + role. Allowed values are +started+, +slave+, and +master+. A rule + with +role="master"+ cannot determine the initial location of a + clone instance and will only affect which of the active instances will be promoted. indexterm:[role,Constraint Rule] indexterm:[Constraint,Rule,role] |score +| |The score to apply if the rule evaluates to +true+. Limited to use in rules that are part of location constraints. indexterm:[score,Constraint Rule] indexterm:[Constraint,Rule,score] |score-attribute +| |The node attribute to look up and use as a score if the rule evaluates to +true+. Limited to use in rules that are part of location constraints. indexterm:[score-attribute,Constraint Rule] indexterm:[Constraint,Rule,score-attribute] |boolean-op +|+and+ |How to combine the result of multiple expression objects. Allowed - values: _and_ and +or+. + values are +and+ and +or+. indexterm:[boolean-op,Constraint Rule] indexterm:[Constraint,Rule,boolean-op] |========================================================= == Node Attribute Expressions == indexterm:[Resource,Constraint,Attribute Expression] Expression objects are used to control a resource based on the attributes defined by a node or nodes. In addition to any attributes added by the administrator, each node has a built-in node attribute called +#uname+ that can also be used. .Properties of an Expression -[width="95%",cols="2m,5<",options="header",align="center"] +[width="95%",cols="1m,1,5 ---- ==== .Equivalent expression ==== [source,XML] ---- ---- ==== .9am-5pm, Mon-Friday ==== [source,XML] ------- ------- ==== Please note that the +16+ matches up to +16:59:59+, as the numeric value (hour) still matches! .9am-6pm, Mon-Friday, or all day saturday ==== [source,XML] ------- ------- ==== .9am-5pm or 9pm-12pm, Mon-Friday ==== [source,XML] ------- ------- ==== .Mondays in March 2005 ==== [source,XML] ------- ------- ==== [NOTE] ====== Because no time is specified, 00:00:00 is implied. This means that the range includes all of 2005-03-01 but none of 2005-04-01. You may wish to write +end="2005-03-31T23:59:59"+ to avoid confusion. ====== .A full moon on Friday the 13th ===== [source,XML] ------- ------- ===== == Using Rules to Determine Resource Location == indexterm:[Rule,Determine Resource Location] indexterm:[Resource,Location,Determine by Rules] If the constraint's outer-most rule evaluates to +false+, the cluster treats the constraint as if it was not there. When the rule evaluates to +true+, the node's preference for running the resource is updated with the score associated with the rule. -If this sounds familiar, its because you have been using a simplified +If this sounds familiar, it is because you have been using a simplified syntax for location constraint rules already. Consider the following location constraint: .Prevent myApacheRsc from running on c001n03 ===== [source,XML] ------- ------- ===== This constraint can be more verbosely written as: .Prevent myApacheRsc from running on c001n03 - expanded version ===== [source,XML] ------- ------- ===== The advantage of using the expanded form is that one can then add extra clauses to the rule, such as limiting the rule such that it only applies during certain times of the day or days of the week (this is discussed in subsequent sections). It also allows us to match on node properties other than its name. If we rated each machine's CPU power such that the cluster had the following nodes section: .A sample nodes section for use with score-attribute ===== [source,XML] ------- ------- ===== then we could prevent resources from running on underpowered machines with the rule [source,XML] ------- - ------- === Using +score-attribute+ Instead of +score+ === When using +score-attribute+ instead of +score+, each node matched by the rule has its score adjusted differently, according to its value for the named node attribute. Thus, in the previous example, if a rule used +score-attribute="cpu_mips"+, +c001n01+ would have its preference to run the resource increased by +1234+ whereas +c001n02+ would have its preference increased by +5678+. == Using Rules to Control Resource Options == Often some cluster nodes will be different from their peers; sometimes these differences (the location of a binary or the names of network interfaces) require resources to be configured differently depending on the machine they're hosted on. By defining multiple +instance_attributes+ objects for the resource and adding a rule to each, we can easily handle these special cases. In the example below, +mySpecialRsc+ will use eth1 and port 9999 when run on +node1+, eth2 and port 8888 on +node2+ and default to eth0 and port 9999 for all other nodes. .Defining different resource options based on the node name ===== [source,XML] ------- ------- ===== The order in which +instance_attributes+ objects are evaluated is determined by their score (highest to lowest). If not supplied, score defaults to zero and objects with an equal score are processed in listed order. If the +instance_attributes+ object does not have a +rule+ or has a +rule+ that evaluates to +true+, then for any parameter the resource does not yet have a value for, the resource will use the parameter values defined by the +instance_attributes+ object. == Using Rules to Control Cluster Options == indexterm:[Rule,Controlling Cluster Options] indexterm:[Cluster,Setting Options with Rules] Controlling cluster options is achieved in much the same manner as specifying different resource options on different nodes. The difference is that because they are cluster options, one cannot (or should not, because they won't work) use attribute based expressions. The following example illustrates how to set a different +resource-stickiness+ value during and outside of work hours. This allows resources to automatically move back to their most preferred hosts, but at a time that (in theory) does not interfere with business activities. .Change +resource-stickiness+ during working hours ===== [source,XML] ------- ------- ===== [[s-rules-recheck]] == Ensuring Time Based Rules Take Effect == A Pacemaker cluster is an event driven system. As such, it won't recalculate the best place for resources to run in unless something (like a resource failure or configuration change) happens. This can mean that a location constraint that only allows resource X to run between 9am and 5pm is not enforced. If you rely on time based rules, it is essential that you set the +cluster-recheck-interval+ option. This tells the cluster to periodically recalculate the ideal state of the cluster. For example, if you set +cluster-recheck-interval=5m+, then sometime between 9:00 and 9:05 the cluster would notice that it needs to start resource X, and between 17:00 and 17:05 it would realize that X needed to be stopped. Note that the timing of the actual start and stop actions depends on what else needs to be performed first . diff --git a/doc/Pacemaker_Explained/en-US/Ch-Stonith.txt b/doc/Pacemaker_Explained/en-US/Ch-Stonith.txt index b27524c646..ed905b826a 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Stonith.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Stonith.txt @@ -1,739 +1,807 @@ = Configure STONITH = //// -We prefer [[ch-stonith]], but older versions of asciidoc dont deal well +We prefer [[ch-stonith]], but older versions of asciidoc don't deal well with that construct for chapter headings //// anchor:ch-stonith[Chapter 13, STONITH] indexterm:[STONITH, Configuration] == What Is STONITH == STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and it protects your data from being corrupted by rogue nodes or concurrent access. Just because a node is unresponsive, this doesn't mean it isn't accessing your data. The only way to be 100% sure that your data is safe, is to use STONITH so we can be certain that the node is truly offline, before allowing the data to be accessed from another node. STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere. == What STONITH Device Should You Use == It is crucial that the STONITH device can allow the cluster to differentiate between a node failure and a network one. The biggest mistake people make in choosing a STONITH device is to -use remote power switch (such as many on-board IMPI controllers) that +use a remote power switch (such as many on-board IPMI controllers) that shares power with the node it controls. In such cases, the cluster cannot be sure if the node is really offline, or active and suffering from a network fault. Likewise, any device that relies on the machine being active (such as SSH-based "devices" used during testing) are inappropriate. == Differences of STONITH Resources == Stonith resources are somewhat special in Pacemaker. In previous versions, only "running" resources could be used by Pacemaker for fencing. This requirement has been relaxed to allow other parts of the cluster (such as resources like DRBD) to reliably initiate fencing. footnote:[Fencing a node while Pacemaker was moving stonith resources around would otherwise fail] Now all nodes have access to their definitions and instantiate them on-the-fly when needed, however preference is given to 'verified' instances which are the ones the cluster has explicitly started. In the case of a cluster split, the partition with a verified instance will have a slight advantage as stonith-ng in the other partition will have to hear from all its current peers before choosing a node to perform the fencing. [NOTE] =========== To disable a fencing device/resource, 'target-role' can be set as you would for a normal resource. =========== [NOTE] =========== To prevent a specific node from using a fencing device, location constraints will work as expected. =========== [IMPORTANT] =========== -Currently there is a limitation that fencing resources may only have a +Currently there is a limitation that fencing resources may only have one set of meta-attributes and one set of instance-attributes. This can be revisited if it becomes a significant limitation for people. =========== -.Properties of Fencing Devices -[width="95%",cols="1m,1m,1m,5<",options="header",align="center"] +.Properties of Fencing Resources +[width="95%",cols="5m,2,3,10+ . Create a file called +stonith.xml+ containing a primitive resource with a class of 'stonith', a type of and a parameter for each of the values returned in step 2. . If the device does not know how to fence nodes based on their uname, you may also need to set the special +pcmk_host_map+ parameter. See +man stonithd+ for details. . If the device does not support the list command, you may also need to set the special +pcmk_host_list+ and/or +pcmk_host_check+ parameters. See +man stonithd+ for details. . If the device does not expect the victim to be specified with the port parameter, you may also need to set the special +pcmk_host_argument+ parameter. See +man stonithd+ for details. . Upload it into the CIB using cibadmin: +cibadmin -C -o resources --xml-file stonith.xml+ . Set stonith-enabled to true. +crm_attribute -t crm_config -n stonith-enabled -v true+ . Once the stonith resource is running, you can test it by executing: +stonith_admin --reboot nodename+. Although you might want to stop the cluster on that machine first. === Example === -Assuming we have an chassis containing four nodes and an IPMI device -active on 10.0.0.1, then we would chose the fence_ipmilan driver in step -2 and obtain the following list of parameters +Assume we have an chassis containing four nodes and an IPMI device +active on 192.0.2.1. We would choose the `fence_ipmilan` driver, +and obtain the following list of parameters: .Obtaining a list of STONITH Parameters - +==== ---- # stonith_admin --metadata -a fence_ipmilan ---- [source,XML] ---- - - -fence_ipmilan is an I/O Fencing agent which can be used with machines controlled by IPMI. This agent calls support software using ipmitool (http://ipmitool.sf.net/). - -To use fence_ipmilan with HP iLO 3 you have to enable lanplus option (lanplus / -P) and increase wait after operation to 4 seconds (power_wait=4 / -T 4) - - - - - IPMI Lan Auth type (md5, password, or none) - - - - - IPMI Lan IP to talk to - - - - - Password (if required) to control power on IPMI device - - - - - Script to retrieve password (if required) - - - - - Use Lanplus - - - - - Username/Login (if required) to control power on IPMI device - - - - - Operation to perform. Valid operations: on, off, reboot, status, list, diag, monitor or metadata - - - - - Timeout (sec) for IPMI operation - - - - - Ciphersuite to use (same as ipmitool -C parameter) - - - - - Method to fence (onoff or cycle) - - - - - Wait X seconds after on/off operation - - - - - Wait X seconds before fencing is started - - - - - Verbose mode - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ---- +==== from which we would create a STONITH resource fragment that might look like this: .Sample STONITH Resource +==== [source,XML] ---- - + ---- +==== And finally, since we disabled it earlier, we need to re-enable STONITH. ---- # crm_attribute -t crm_config -n stonith-enabled -v true ---- == Advanced Fencing Configurations == Some people consider that having one fencing device is a single point of failure footnote:[Not true, since a node or resource must fail before fencing even has a chance to], others prefer removing the node from the storage and network instead of turning it off. Whatever the reason, Pacemaker supports fencing nodes with multiple devices through a feature called fencing topologies. Simply create the individual devices as you normally would and then define one or more fencing levels in the fencing-topology section in the configuration. * Each level is attempted in +ascending index+ order * If a device fails, +processing terminates+ for the current level. No further devices in that level are exercised and the next level is attempted instead. * If the operation succeeds for all the listed devices in a level, the level is deemed to have passed * The operation is finished +when a level has passed+ (success), or all levels have been attempted (failed) * If the operation failed, the next step is determined by the Policy Engine and/or crmd. Some possible uses of topologies include: * try poison-pill and fail back to power * try disk and network, and fall back to power if either fails * initiate a kdump and then poweroff the node .Properties of Fencing Levels [width="95%",cols="1m,6<",options="header",align="center"] |========================================================= |Field |Description |id |Your name for the level indexterm:[id,fencing-level] indexterm:[Fencing,fencing-level,id] |target |The node to which this level applies indexterm:[target,fencing-level] indexterm:[Fencing,fencing-level,target] |index |The order in which to attempt the levels. Levels are attempted in +ascending index+ order +until one succeeds+. indexterm:[index,fencing-level] indexterm:[Fencing,fencing-level,index] |devices -|A comma separated list of devices for which the +|A comma-separated list of devices that must all be tried for this level indexterm:[devices,fencing-level] indexterm:[Fencing,fencing-level,devices] |========================================================= === Example use of Fencing Topologies === [source,XML] ---- ... ... ---- === Example use of advanced Fencing Topologies: dual layer and dual devices === -The following example illustrates an advanced use of +fencing_topology+ in a cluster with the following properties: +The following example illustrates an advanced use of +fencing-topology+ in a cluster with the following properties: * 3 nodes (2 active prod-mysql nodes, 1 prod_mysql-rep in standby for quorum purposes) -* the active nodes have an IPMI-controlled power board reached at 10.10.10.1 and 10.10.10.2 -* the active nodes also have two independant PSUs (Power Supplu Units) connected to two independant PDUs (Power Distribution Unit) reached at 10.20.1.1 (port 10 and port 11) and 10.20.2.1 (port 10 and port 11) -* the first fencing method uses the +fence_ipmi+ agent -* the second fencing method uses the +fence_apc_snmp+ agent targetting 2 fencing devices (one per PSU, either port 10 or 11) +* the active nodes have an IPMI-controlled power board reached at 192.0.2.1 and 192.0.2.2 +* the active nodes also have two independent PSUs (Power Supply Units) + connected to two independent PDUs (Power Distribution Units) reached at + 198.51.100.1 (port 10 and port 11) and 203.0.113.1 (port 10 and port 11) +* the first fencing method uses the `fence_ipmi` agent +* the second fencing method uses the `fence_apc_snmp` agent targetting 2 fencing devices (one per PSU, either port 10 or 11) * fencing is only implemented for the active nodes and has location constraints * fencing topology is set to try IPMI fencing first then default to a "sure-kill" dual PDU fencing In a normal failure scenario, STONITH will first select +fence_ipmi+ to try and kill the faulty node. -Using a +fencing_topology+, if that first method fails, STONITH will then move on to selecting +fence_apc_snmp+ twice: +Using a fencing topology, if that first method fails, STONITH will then move on to selecting +fence_apc_snmp+ twice: * once for the first PDU * again for the second PDU The fence action is considered successful only if both PDUs report the required status. If any of them fails, STONITH loops back to the first fencing method, +fence_ipmi+, and so on until the node is fenced or fencing action is cancelled. .First fencing method: single IPMI device Each cluster node has it own dedicated IPMI channel that can be called for fencing using the following primitives: [source,XML] ---- - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + ---- .Second fencing method: dual PDU devices Each cluster node also has two distinct power channels controlled by two distinct PDUs. That means a total of 4 fencing devices configured as follows: - Node 1, PDU 1, PSU 1 @ port 10 - Node 1, PDU 2, PSU 2 @ port 10 - Node 2, PDU 1, PSU 1 @ port 11 - Node 2, PDU 2, PSU 2 @ port 11 The matching fencing agents are configured as follows: [source,XML] ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ---- .Location Constraints To prevent STONITH from running a fencing agent on the very same node it is supposed to fence, constraints are placed on all the fencing primitives: [source,XML] ---- ---- .Fencing topology Now that all the fencing resources are defined, it's time to create the right topology. We want to first fence using IPMI and if that does not work, fence both PDUs to effectively and surely kill the node. [source,XML] ---- ---- -Please note, in +fencing_topology+, the lower index value determines the priority of the first fencing method. +Please note, in +fencing-topology+, the lowest +index+ value determines the priority of the first fencing method. .Final configuration Put together, the configuration looks like this: [source,XML] ---- ... - + - + - + - + - + - + ... ---- diff --git a/doc/Pacemaker_Explained/en-US/Pacemaker_Explained.xml b/doc/Pacemaker_Explained/en-US/Pacemaker_Explained.xml index aa1eab4482..fe054f3f05 100644 --- a/doc/Pacemaker_Explained/en-US/Pacemaker_Explained.xml +++ b/doc/Pacemaker_Explained/en-US/Pacemaker_Explained.xml @@ -1,47 +1,47 @@ Further Reading - Project Website - Project Documentation + Project Website: + Project Documentation: - A comprehensive guide to cluster commands has been written by Novell + SUSE High Availibility Guide: Heartbeat configuration: Corosync Configuration: