diff --git a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.txt b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.txt
index d0aba3914f..d55c257e1b 100644
--- a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.txt
+++ b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Options.txt
@@ -1,729 +1,758 @@
 :compat-mode: legacy
 = Advanced Configuration =
 
 [[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 in the middle of the business day -- hardly
 desirable.
 
 To specify a date and 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, its 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
 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]
 <op id="my-weekly-action" name="custom-action" interval="P7D" interval-origin="2009-W01-1"/> 
 =====
 
 [[s-failure-handling]]
 == Handling Resource Failure ==
 
 By default, Pacemaker will attempt to recover failed resources by restarting
 them. However, failure recovery is highly configurable.
 
 === Failure Counts ===
 
 Pacemaker tracks resource failures for each combination of node, resource, and
 operation (start, stop, monitor, etc.).
 
 You can query the fail count for a particular node, resource, and/or operation
 using the `crm_failcount` command. For example, to see how many times the
 10-second monitor for +myrsc+ has failed on +node1+, run:
 
 ----
 # crm_failcount --query -r myrsc -N node1 -n monitor -I 10s
 ----
 
 If you omit the node, `crm_failcount` will use the local node. If you omit the
 operation and interval, `crm_failcount` will display the sum of the fail counts
 for all operations on the resource.
 
 You can use `crm_resource --cleanup` or `crm_failcount --delete` to clear
 fail counts. For example, to clear the above monitor failures, run:
 
 ----
 # crm_resource --cleanup -r myrsc -N node1 -n monitor -I 10s
 ----
 
 If you omit the resource, `crm_resource --cleanup` will clear failures for all
 resources. If you omit the node, it will clear failures on all nodes. If you
 omit the operation and interval, it will clear the failures for all operations
 on the resource.
 
 [NOTE]
 ====
 Even when cleaning up only a single operation, all failed operations will
 disappear from the status display. This allows us to trigger a re-check of the
 resource's current status.
 ====
 
 Higher-level tools may provide other commands for querying and clearing
 fail counts.
 
 The `crm_mon` tool shows the current cluster status, including any failed
 operations. To see the current fail counts for any failed resources, call
 `crm_mon` with the `--failcounts` option. This shows the fail counts per
 resource (that is, the sum of any operation fail counts for the resource).
 
 === Failure Response ===
 
 Normally, if a running resource fails, pacemaker will try to stop it and start
 it again. Pacemaker will choose the best location to start it each time, which
 may be the same node that it failed on.
 
 However, if a resource fails repeatedly, it is possible that there is an
 underlying problem on that node, and you might desire trying a different node
 in such a case. Pacemaker allows you to set your preference via the
 +migration-threshold+ resource meta-attribute.
 footnote:[
 The naming of this option was perhaps unfortunate as it is easily
 confused with live 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.
 ]
 
 If you define +migration-threshold=pass:[<replaceable>N</replaceable>]+ for a
 resource, it will be banned from the original node after 'N' failures.
 
 [NOTE]
 ====
 The +migration-threshold+ is per 'resource', even though fail counts are
 tracked per 'operation'. The operation fail counts are added together
 to compare against the +migration-threshold+.
 ====
 
 By default, fail counts remain until manually cleared by an administrator
 using `crm_resource --cleanup` or `crm_failcount --delete` (hopefully after
 first fixing the failure's cause). It is possible to have fail counts expire
 automatically by setting the +failure-timeout+ resource meta-attribute.
 
 [IMPORTANT]
 ====
 A successful operation does not clear past failures. If a recurring monitor
 operation fails once, succeeds many times, then fails again days later, its
 fail count is 2. Fail counts are cleared only by manual intervention or
 falure timeout.
 ====
 
 For example, 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 stickiness and constraint scores) after one
 minute.
 
 [NOTE]
 ====
 +failure-timeout+ is measured since the most recent failure. That is, older
 failures do not individually time out and lower the fail count. Instead, all
 failures are timed out simultaneously (and the fail count is reset to 0) if
 there is no new failure for the timeout period.
 ====
 
 There are two exceptions to the migration threshold concept:
 when a resource either fails to start or fails to stop.
 
 If the cluster property +start-failure-is-fatal+ is set to +true+ (which is the
 default), start failures cause the fail count 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 <<s-rules-recheck>> to understand how timeouts work
 before configuring a +failure-timeout+.
 
 == Moving Resources ==
 indexterm:[Moving,Resources] 
 indexterm:[Resource,Moving]
 
 === Moving Resources Manually ===
 
 There are primarily two occasions when you would want to move a
 resource from its current location: when the whole node is under
 maintenance, and when a single resource needs to be moved.
 
 ==== Standby Mode ====
 
 Since everything eventually comes down to a score, you could create
 constraints for every resource to prevent them from running on one
 node.  While pacemaker 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, run:
 
 ----
 # crm_standby -G
 ----
 
 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` option:
 
 ----
 # crm_standby -G --node sles-2
 ----
 
 To change the current node's standby status, use `-v` instead of `-G`:
 
 ----
 # crm_standby -v on
 ----
 
 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 could 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+ 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]
 <rsc_location rsc="Email" node="sles-2" score="INFINITY"/>
 
 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:
 
 ----
 # crm_resource -B -r Email
 ----
 
 Which will instead create a negative constraint, like
 
 [source,XML]
 <rsc_location rsc="Email" node="sles-1" score="-INFINITY"/>
 
 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 <<node-score-equal>>.  The tool can detect
 some of these cases and deals with them by creating both
 positive and negative constraints. E.g.
 
 +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.
 
 === Moving Resources Due to Connectivity Changes ===
 
 You can configure the cluster to move resources when external connectivity is
 lost in two steps.
 
 ==== Tell Pacemaker to Monitor Connectivity ====
 
 First, add an *ocf:pacemaker:ping* resource to the cluster.  The
 *ping* resource uses the system utility of the same name to a test whether
 list of machines (specified by DNS hostname or IPv4/IPv6 address) are
 reachable and uses the results to maintain a node attribute called +pingd+
 by default.
 footnote:[
 The attribute name is customizable, in order to allow multiple ping groups to be defined.
 ]
 
 [NOTE]
 ===========
 Older versions of Pacemaker used a different agent *ocf:pacemaker:pingd* which
 is now deprecated in favor of *ping*. If your version of Pacemaker does not
 contain the *ping* resource agent, download the latest version from
 https://github.com/ClusterLabs/pacemaker/tree/master/extra/resources/ping
 ===========
 
 Normally, the ping resource should 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]
 ------------
 <clone id="Connected">
    <primitive id="ping" provider="pacemaker" class="ocf" type="ping">
     <instance_attributes id="ping-attrs">
       <nvpair id="pingd-dampen" name="dampen" value="5s"/>
       <nvpair id="pingd-multiplier" name="multiplier" value="1000"/>
       <nvpair id="pingd-hosts" name="host_list" value="my.gateway.com www.bigcorp.com"/>
     </instance_attributes>
     <operations>
       <op id="ping-monitor-60s" interval="60s" name="monitor"/>
     </operations>
    </primitive>
 </clone>
 ------------
 =====
 
 [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 ====
 
 [IMPORTANT]
 ======
 Before attempting the following, make sure you understand
 <<ch-rules>>.
 ======
 
 There are a number of ways to use the connectivity data.
 
 The most common setup is for people to have a single ping
 target (e.g. the service network's default gateway), to prevent the cluster
 from running a resource on any unconnected node.
 
 .Don't run a resource on unconnected nodes
 =====
 [source,XML]
 -------
 <rsc_location id="WebServer-no-connectivity" rsc="Webserver">
    <rule id="ping-exclude-rule" score="-INFINITY" >
     <expression id="ping-exclude" attribute="pingd" operation="not_defined"/>
    </rule>
 </rsc_location>
 -------
 =====
 
 A more complex setup is to have a number of ping targets 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 targets.
 =====
 [source,XML]
 -------
 <primitive id="ping" provider="pacemaker" class="ocf" type="ping">
 ... <!-- omitting some configuration to highlight important parts -->
       <nvpair id="pingd-multiplier" name="multiplier" value="1000"/>
 ...
 </primitive>
 ...
 <rsc_location id="WebServer-connectivity" rsc="Webserver">
    <rule id="ping-prefer-rule" score="-INFINITY" >
       <expression id="ping-prefer" attribute="pingd" operation="lt" value="3000"/>
    </rule>
 </rsc_location>
 -------
 =====
 
 Alternatively, 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]
 -------
 <rsc_location id="WebServer-connectivity" rsc="Webserver">
    <rule id="ping-prefer-rule" score-attribute="pingd" >
     <expression id="ping-prefer" attribute="pingd" operation="defined"/>
    </rule>
 </rsc_location>
 -------
 =====
 
 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 five ping nodes but *sles-2* is only
 connected to two, then it would be as if you instead had the following
 constraints in your configuration:
 
 .How the cluster translates the above location constraint
 =====
 [source,XML]
 -------
 <rsc_location id="ping-1" rsc="Webserver" node="sles-1" score="5000"/>
 <rsc_location id="ping-2" rsc="Webserver" node="sles-2" score="2000"/>
 -------
 =====
 
 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]
 -------
 <rsc_location id="WebServer-connectivity" rsc="Webserver">
    <rule id="ping-exclude-rule" score="-INFINITY" >
     <expression id="ping-exclude" attribute="pingd" operation="lt" value="3000"/>
    </rule>
    <rule id="ping-prefer-rule" score-attribute="pingd" >
     <expression id="ping-prefer" attribute="pingd" operation="defined"/>
    </rule>
 </rsc_location>
 -------
 =====
 
 [[s-migrating-resources]]
 === Migrating Resources ===
 
 Normally, when the cluster needs to move a resource, it fully restarts
 the resource (i.e. stops the resource on the current node
 and starts it on the new node).
 
 However, some types of resources, such as Xen virtual guests, are able to move to
 another location without loss of state (often referred to as live migration
 or hot migration). In pacemaker, this is called resource migration.
 Pacemaker can be configured to migrate a resource when moving it,
 rather than restarting it.
 
 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; and
 * 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 special 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 for a resource agent to implement migration,
 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 agent must support +migrate_to+ and
   +migrate_from+ actions, and advertise them in its metadata.
 * The resource must have the +allow-migrate+ meta-attribute set to
   +true+ (which is not the default).
 
 If an otherwise migratable resource depends on another resource
 via an ordering constraint, there are special situations in which it will be
 restarted rather than migrated.
 
 For example, if the resource depends on a clone, and at the time the resource
 needs to be moved, the clone has instances that are stopping and instances
 that are starting, then the resource will be restarted. The scheduler is not
 yet able to model this situation correctly and so takes the safer (if less
 optimal) path.
 
 Also, if a migratable resource depends on a non-migratable resource, and both
 need to be moved, the migratable resource will be restarted.
 
 [[s-node-health]]
 == Tracking Node Health ==
 
 A node may be functioning adequately as far as cluster membership is concerned,
 and yet be "unhealthy" in some respect that makes it an undesirable location
 for resources. For example, a disk drive may be reporting SMART errors, or the
 CPU may be highly loaded.
 
 Pacemaker offers a way to automatically move resources off unhealthy nodes.
 
 === Node Health Attributes ===
 
 Pacemaker will treat any node attribute whose name starts with +#health+ as an
 indicator of node health. Node health attributes may have one of the following
 values:
 
 .Allowed Values for Node Health Attributes
 [width="95%",cols="1,<3",options="header",align="center"]
 |=========================================================
 
 |Value
 |Intended significance
 
 |+red+
 |This indicator is unhealthy
  indexterm:[Node health,red]
 
 |+yellow+
 |This indicator is becoming unhealthy
  indexterm:[Node health,yellow]
 
 |+green+
 |This indicator is healthy
  indexterm:[Node health,green]
 
 |'integer'
 |A numeric score to apply to all resources on this node
  (0 or positive is healthy, negative is unhealthy)
  indexterm:[Node health,score]
 
 |=========================================================
 
 === Node Health Strategy ===
 
 Pacemaker assigns a node health score to each node, as the sum of the values of
 all its node health attributes. This score will be used as a location
 constraint applied to this node for all resources.
 
 The +node-health-strategy+ cluster option controls how Pacemaker responds to
 changes in node health attributes, and how it translates +red+, +yellow+, and
 +green+ to scores.
 
 Allowed values are:
 
 .Node Health Strategies
 [width="95%",cols="1m,<3",options="header",align="center"]
 |=========================================================
 
 |Value
 |Effect
 
 |none
 |Do not track node health attributes at all.
  indexterm:[Node health,none]
 
 |migrate-on-red
 |Assign the value of +-INFINITY+ to +red+, and 0 to +yellow+ and +green+.
  This will cause all resources to move off the node if any attribute is +red+.
  indexterm:[Node health,migrate-on-red]
 
 |only-green
 |Assign the value of +-INFINITY+ to +red+ and +yellow+, and 0 to +green+.
  This will cause all resources to move off the node if any attribute is +red+
  or +yellow+.
  indexterm:[Node health,only-green]
 
 |progressive
 |Assign the value of the +node-health-red+ cluster option to +red+, the value
  of +node-health-yellow+ to +yellow+, and the value of +node-health-green+ to
  +green+. Each node is additionally assigned a score of +node-health-base+
  (this allows resources to start even if some attributes are +yellow+). This
  strategy gives the administrator finer control over how important each value
  is.
  indexterm:[Node health,progressive]
 
 |custom
 |Track node health attributes using the same values as +progressive+ for
  +red+, +yellow+, and +green+, but do not take them into account.
  The administrator is expected to implement a policy by defining rules
  (see <<ch-rules>>) referencing node health attributes.
  indexterm:[Node health,custom]
 
 |=========================================================
 
 === Measuring Node Health ===
 
 Since Pacemaker calculates node health based on node attributes,
 any method that sets node attributes may be used to measure node
 health. The most common ways are resource agents or separate daemons.
 
 Pacemaker provides examples that can be used directly or as a basis for
 custom code. The +ocf:pacemaker:HealthCPU+ and +ocf:pacemaker:HealthSMART+
 resource agents set node health attributes based on CPU and disk parameters.
 The +ipmiservicelogd+ daemon sets node health attributes based on IPMI
 values (the +ocf:pacemaker:SystemHealth+ resource agent can be used to manage
 the daemon as a cluster resource).
 
+In order to take advantage of this feature - firstly add the resource to your cluster, preferably as a cloned resource to constantly measure health on all nodes:
+
+=====
+[source,XML]
+------------
+<clone id="resHealthIOWait-clone">
+  <primitive class="ocf" id="HealthIOWait" provider="pacemaker" type="HealthIOWait">
+    <instance_attributes id="resHealthIOWait-instance_attributes">
+      <nvpair id="resHealthIOWait-instance_attributes-red_limit" name="red_limit" value="30"/>
+      <nvpair id="resHealthIOWait-instance_attributes-yellow_limit" name="yellow_limit" value="10"/>
+    </instance_attributes>
+    <operations>
+      <op id="resHealthIOWait-monitor-interval-5" interval="5" name="monitor" timeout="5"/>
+      <op id="resHealthIOWait-start-interval-0s" interval="0s" name="start" timeout="10s"/>
+      <op id="resHealthIOWait-stop-interval-0s" interval="0s" name="stop" timeout="10s"/>
+    </operations>
+  </primitive>
+</clone>
+------------
+=====
+
+This way attrd_updater will set proper status for each node running this resource. Any attribute matching "#health-[a-zA-z]+" will force cluster to migrate all resources from unhealthy node and place it on other nodes according to all constraints defined in your cluster.
+
+When the node is no longer faulty you can force the cluster to restart the cloned resource on faulty node and make it available to take resources, in this case since we are using HealthIOWait provider:
+
+----
+# attrd_updater -n "#health-iowait" -U "green" --node="<nodename>" -d "60s"
+----
+
 == Reloading Services After a Definition Change ==
 
 The cluster automatically detects changes to the definition of
 services it manages.  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, the resource agent must:
 
 . Accept the +reload+ operation and perform any required actions.
   _The actions here depend completely on your application!_
 +
 .The DRBD agent's logic for supporting +reload+
 =====
 [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]
 -------
 <?xml version="1.0"?>
   <!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd">
   <resource-agent name="drbd">
     <version>1.1</version>
     
     <longdesc lang="en">
       Master/Slave OCF Resource Agent for DRBD
     </longdesc>
     
     ...
     
     <actions>
       <action name="start"   timeout="240" />
       <action name="reload"  timeout="240" />
       <action name="promote" timeout="90" />
       <action name="demote"  timeout="90" />
       <action name="notify"  timeout="90" />
       <action name="stop"    timeout="100" />
       <action name="meta-data"    timeout="5" />
       <action name="validate-all" timeout="30" />
     </actions>
   </resource-agent>
 -------
 =====
 . 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]
 -------
 <parameter name="drbdconf" unique="0">
     <longdesc lang="en">Full path to the drbd.conf file.</longdesc>
     <shortdesc lang="en">Path to drbd.conf</shortdesc>
     <content type="string" default="${OCF_RESKEY_drbdconf_default}"/>
 </parameter>
 -------
 =====
 
 Once these requirements are satisfied, the cluster will automatically
 know to reload the resource (instead of restarting) when a non-unique
 field changes.
       
 [NOTE]
 ======
 Metadata will not be re-read unless the resource needs to be 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/pot/Ch-Advanced-Options.pot b/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot
index 8dc7e1bec7..af2d20d8b8 100644
--- a/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot
+++ b/doc/Pacemaker_Explained/pot/Ch-Advanced-Options.pot
@@ -1,976 +1,981 @@
 # 
 # AUTHOR <EMAIL@ADDRESS>, YEAR.
 #
 msgid ""
 msgstr ""
 "Project-Id-Version: 0\n"
 "POT-Creation-Date: 2018-05-14 18:03-0500\n"
 "PO-Revision-Date: 2018-05-14 18:03-0500\n"
 "Last-Translator: Automatically generated\n"
 "Language-Team: None\n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-publican; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
 #. Tag: title
 #, no-c-format
 msgid "Advanced Configuration"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Specifying When Recurring Actions are Performed"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "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 in the middle of the business day — hardly desirable."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "To specify a date and time that the operation should be relative to, set the operation’s <literal>interval-origin</literal>. The cluster uses this point to calculate the correct <literal>start-delay</literal> such that the operation will occur at <emphasis>origin + (interval * N)</emphasis>."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "So, if the operation’s interval is 24h, its 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 cancelled."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The value specified for <literal>interval</literal> and <literal>interval-origin</literal> can be any date/time conforming to the <ulink url=\"http://en.wikipedia.org/wiki/ISO_8601\">ISO8601 standard</ulink>. 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:"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Specifying a Base for Recurring Action Intervals"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;op id=\"my-weekly-action\" name=\"custom-action\" interval=\"P7D\" interval-origin=\"2009-W01-1\"/&gt;"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Handling Resource Failure"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "By default, Pacemaker will attempt to recover failed resources by restarting them. However, failure recovery is highly configurable."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Failure Counts"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Pacemaker tracks resource failures for each combination of node, resource, and operation (start, stop, monitor, etc.)."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "You can query the fail count for a particular node, resource, and/or operation using the <literal>crm_failcount</literal> command. For example, to see how many times the 10-second monitor for <literal>myrsc</literal> has failed on <literal>node1</literal>, run:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_failcount --query -r myrsc -N node1 -n monitor -I 10s"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "If you omit the node, <literal>crm_failcount</literal> will use the local node. If you omit the operation and interval, <literal>crm_failcount</literal> will display the sum of the fail counts for all operations on the resource."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "You can use <literal>crm_resource --cleanup</literal> or <literal>crm_failcount --delete</literal> to clear fail counts. For example, to clear the above monitor failures, run:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_resource --cleanup -r myrsc -N node1 -n monitor -I 10s"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "If you omit the resource, <literal>crm_resource --cleanup</literal> will clear failures for all resources. If you omit the node, it will clear failures on all nodes. If you omit the operation and interval, it will clear the failures for all operations on the resource."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Even when cleaning up only a single operation, all failed operations will disappear from the status display. This allows us to trigger a re-check of the resource’s current status."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Higher-level tools may provide other commands for querying and clearing fail counts."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The <literal>crm_mon</literal> tool shows the current cluster status, including any failed operations. To see the current fail counts for any failed resources, call <literal>crm_mon</literal> with the <literal>--failcounts</literal> option. This shows the fail counts per resource (that is, the sum of any operation fail counts for the resource)."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Failure Response"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Normally, if a running resource fails, pacemaker will try to stop it and start it again. Pacemaker will choose the best location to start it each time, which may be the same node that it failed on."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "However, if a resource fails repeatedly, it is possible that there is an underlying problem on that node, and you might desire trying a different node in such a case. Pacemaker allows you to set your preference via the <literal>migration-threshold</literal> resource meta-attribute. <footnote><para> The naming of this option was perhaps unfortunate as it is easily confused with live 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. </para></footnote>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "If you define <literal>migration-threshold=<replaceable>N</replaceable></literal> for a resource, it will be banned from the original node after <emphasis>N</emphasis> failures."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The <literal>migration-threshold</literal> is per <emphasis>resource</emphasis>, even though fail counts are tracked per <emphasis>operation</emphasis>. The operation fail counts are added together to compare against the <literal>migration-threshold</literal>."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "By default, fail counts remain until manually cleared by an administrator using <literal>crm_resource --cleanup</literal> or <literal>crm_failcount --delete</literal> (hopefully after first fixing the failure’s cause). It is possible to have fail counts expire automatically by setting the <literal>failure-timeout</literal> resource meta-attribute."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "A successful operation does not clear past failures. If a recurring monitor operation fails once, succeeds many times, then fails again days later, its fail count is 2. Fail counts are cleared only by manual intervention or falure timeout."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "For example, a setting of <literal>migration-threshold=2</literal> and <literal>failure-timeout=60s</literal> would cause the resource to move to a new node after 2 failures, and allow it to move back (depending on stickiness and constraint scores) after one minute."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>failure-timeout</literal> is measured since the most recent failure. That is, older failures do not individually time out and lower the fail count. Instead, all failures are timed out simultaneously (and the fail count is reset to 0) if there is no new failure for the timeout period."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "There are two exceptions to the migration threshold concept: when a resource either fails to start or fails to stop."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "If the cluster property <literal>start-failure-is-fatal</literal> is set to <literal>true</literal> (which is the default), start failures cause the fail count to be set to <literal>INFINITY</literal> and thus always cause the resource to move immediately."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "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."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Please read <xref linkend=\"s-rules-recheck\" /> to understand how timeouts work before configuring a <literal>failure-timeout</literal>."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Moving Resources"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<indexterm> <primary>Moving</primary><secondary>Resources</secondary> </indexterm> <indexterm> <primary>Resources</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Moving</secondary> </indexterm> <indexterm> <primary>Moving</primary> </indexterm>"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Moving Resources Manually"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "There are primarily two occasions when you would want to move a resource from its current location: when the whole node is under maintenance, and when a single resource needs to be moved."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Standby Mode"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Since everything eventually comes down to a score, you could create constraints for every resource to prevent them from running on one node. While pacemaker configuration can seem convoluted at times, not even we would require this of administrators."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "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 <literal>crm_standby</literal>. To check the standby status of the current machine, run:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_standby -G"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "A value of <literal>on</literal> indicates that the node is <emphasis>not</emphasis> able to host any resources, while a value of <literal>off</literal> says that it <emphasis>can</emphasis>."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "You can also check the status of other nodes in the cluster by specifying the <literal>--node</literal> option:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_standby -G --node sles-2"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "To change the current node’s standby status, use <literal>-v</literal> instead of <literal>-G</literal>:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_standby -v on"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Again, you can change another host’s value by supplying a hostname with <literal>--node</literal>."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Moving One Resource"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "When only one resource is required to move, we could do this by creating location constraints. However, once again we provide a user-friendly shortcut as part of the <literal>crm_resource</literal> command, which creates and modifies the extra constraints for you. If <literal>Email</literal> were running on <literal>sles-1</literal> and you wanted it moved to a specific location, the command would look something like:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_resource -M -r Email -H sles-2"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Behind the scenes, the tool will create the following location constraint:"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;rsc_location rsc=\"Email\" node=\"sles-2\" score=\"INFINITY\"/&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "It is important to note that subsequent invocations of <literal>crm_resource -M</literal> are not cumulative. So, if you ran these commands"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_resource -M -r Email -H sles-2\n"
 "# crm_resource -M -r Email -H sles-3"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "then it is as if you had never performed the first command."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "To allow the resource to move back again, use:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_resource -U -r Email"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Note the use of the word <emphasis>allow</emphasis>. The resource can move back to its original location but, depending on <literal>resource-stickiness</literal>, it might stay where it is. To be absolutely certain that it moves back to <literal>sles-1</literal>, move it there before issuing the call to <literal>crm_resource -U</literal>:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_resource -M -r Email -H sles-1\n"
 "# crm_resource -U -r Email"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Alternatively, if you only care that the resource should be moved from its current location, try:"
 msgstr ""
 
 #. Tag: screen
 #, no-c-format
 msgid "# crm_resource -B -r Email"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Which will instead create a negative constraint, like"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;rsc_location rsc=\"Email\" node=\"sles-1\" score=\"-INFINITY\"/&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "This will achieve the desired effect, but will also have long-term consequences. As the tool will warn you, the creation of a <literal>-INFINITY</literal> constraint will prevent the resource from running on that node until <literal>crm_resource -U</literal> is used. This includes the situation where every other cluster node is no longer available!"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "In some cases, such as when <literal>resource-stickiness</literal> is set to <literal>INFINITY</literal>, it is possible that you will end up with the problem described in <xref linkend=\"node-score-equal\" />. The tool can detect some of these cases and deals with them by creating both positive and negative constraints. E.g."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>Email</literal> prefers <literal>sles-1</literal> with a score of <literal>-INFINITY</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>Email</literal> prefers <literal>sles-2</literal> with a score of <literal>INFINITY</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "which has the same long-term consequences as discussed earlier."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Moving Resources Due to Connectivity Changes"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "You can configure the cluster to move resources when external connectivity is lost in two steps."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Tell Pacemaker to Monitor Connectivity"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "First, add an <emphasis role=\"strong\">ocf:pacemaker:ping</emphasis> resource to the cluster. The <emphasis role=\"strong\">ping</emphasis> resource uses the system utility of the same name to a test whether list of machines (specified by DNS hostname or IPv4/IPv6 address) are reachable and uses the results to maintain a node attribute called <literal>pingd</literal> by default. <footnote><para> The attribute name is customizable, in order to allow multiple ping groups to be defined. </para></footnote>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Older versions of Pacemaker used a different agent <emphasis role=\"strong\">ocf:pacemaker:pingd</emphasis> which is now deprecated in favor of <emphasis role=\"strong\">ping</emphasis>. If your version of Pacemaker does not contain the <emphasis role=\"strong\">ping</emphasis> resource agent, download the latest version from <ulink url=\"https://github.com/ClusterLabs/pacemaker/tree/master/extra/resources/ping\">https://github.com/ClusterLabs/pacemaker/tree/master/extra/resources/ping</ulink>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Normally, the ping resource should 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."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Common Options for a <emphasis>ping</emphasis> Resource"
 msgstr ""
 
 #. Tag: entry
 #, no-c-format
 msgid "Field"
 msgstr ""
 
 #. Tag: entry
 #, no-c-format
 msgid "Description"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>dampen</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "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> <primary>dampen</primary><secondary>Ping Resource Option</secondary> </indexterm> <indexterm> <primary>Ping Resource Option</primary> </indexterm> <indexterm> <primary>Ping Resource</primary><secondary>Option</secondary><tertiary>dampen</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>dampen</secondary> </indexterm> <indexterm> <primary>dampen</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>multiplier</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The number of connected ping nodes gets multiplied by this value to get a score. Useful when there are multiple ping nodes configured. <indexterm> <primary>multiplier</primary><secondary>Ping Resource Option</secondary> </indexterm> <indexterm> <primary>Ping Resource Option</primary> </indexterm> <indexterm> <primary>Ping Resource</primary><secondary>Option</secondary><tertiary>multiplier</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>multiplier</secondary> </indexterm> <indexterm> <primary>multiplier</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>host_list</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The machines to contact in order to determine the current connectivity status. Allowed values include resolvable DNS host names, IPv4 and IPv6 addresses. <indexterm> <primary>host_list</primary><secondary>Ping Resource Option</secondary> </indexterm> <indexterm> <primary>Ping Resource Option</primary> </indexterm> <indexterm> <primary>Ping Resource</primary><secondary>Option</secondary><tertiary>host_list</tertiary> </indexterm> <indexterm> <primary>Option</primary><secondary>host_list</secondary> </indexterm> <indexterm> <primary>host_list</primary> </indexterm>"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "An example ping cluster resource that checks node connectivity once every minute"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;clone id=\"Connected\"&gt;\n"
 "   &lt;primitive id=\"ping\" provider=\"pacemaker\" class=\"ocf\" type=\"ping\"&gt;\n"
 "    &lt;instance_attributes id=\"ping-attrs\"&gt;\n"
 "      &lt;nvpair id=\"pingd-dampen\" name=\"dampen\" value=\"5s\"/&gt;\n"
 "      &lt;nvpair id=\"pingd-multiplier\" name=\"multiplier\" value=\"1000\"/&gt;\n"
 "      &lt;nvpair id=\"pingd-hosts\" name=\"host_list\" value=\"my.gateway.com www.bigcorp.com\"/&gt;\n"
 "    &lt;/instance_attributes&gt;\n"
 "    &lt;operations&gt;\n"
 "      &lt;op id=\"ping-monitor-60s\" interval=\"60s\" name=\"monitor\"/&gt;\n"
 "    &lt;/operations&gt;\n"
 "   &lt;/primitive&gt;\n"
 "&lt;/clone&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "You’re only half done. The next section deals with telling Pacemaker how to deal with the connectivity status that <literal>ocf:pacemaker:ping</literal> is recording."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Tell Pacemaker How to Interpret the Connectivity Data"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Before attempting the following, make sure you understand <xref linkend=\"ch-rules\" />."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "There are a number of ways to use the connectivity data."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The most common setup is for people to have a single ping target (e.g. the service network’s default gateway), to prevent the cluster from running a resource on any unconnected node."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Don’t run a resource on unconnected nodes"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;rsc_location id=\"WebServer-no-connectivity\" rsc=\"Webserver\"&gt;\n"
 "   &lt;rule id=\"ping-exclude-rule\" score=\"-INFINITY\" &gt;\n"
 "    &lt;expression id=\"ping-exclude\" attribute=\"pingd\" operation=\"not_defined\"/&gt;\n"
 "   &lt;/rule&gt;\n"
 "&lt;/rsc_location&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "A more complex setup is to have a number of ping targets configured. You can require the cluster to only run resources on nodes that can connect to all (or a minimum subset) of them."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Run only on nodes connected to three or more ping targets."
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;primitive id=\"ping\" provider=\"pacemaker\" class=\"ocf\" type=\"ping\"&gt;\n"
 "... &lt;!-- omitting some configuration to highlight important parts --&gt;\n"
 "      &lt;nvpair id=\"pingd-multiplier\" name=\"multiplier\" value=\"1000\"/&gt;\n"
 "...\n"
 "&lt;/primitive&gt;\n"
 "...\n"
 "&lt;rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\"&gt;\n"
 "   &lt;rule id=\"ping-prefer-rule\" score=\"-INFINITY\" &gt;\n"
 "      &lt;expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"lt\" value=\"3000\"/&gt;\n"
 "   &lt;/rule&gt;\n"
 "&lt;/rsc_location&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Alternatively, you can tell the cluster only to <emphasis>prefer</emphasis> nodes with the best connectivity. Just be sure to set <literal>multiplier</literal> to a value higher than that of <literal>resource-stickiness</literal> (and don’t set either of them to <literal>INFINITY</literal>)."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Prefer the node with the most connected ping nodes"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\"&gt;\n"
 "   &lt;rule id=\"ping-prefer-rule\" score-attribute=\"pingd\" &gt;\n"
 "    &lt;expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"defined\"/&gt;\n"
 "   &lt;/rule&gt;\n"
 "&lt;/rsc_location&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "It is perhaps easier to think of this in terms of the simple constraints that the cluster translates it into. For example, if <emphasis role=\"strong\">sles-1</emphasis> is connected to all five ping nodes but <emphasis role=\"strong\">sles-2</emphasis> is only connected to two, then it would be as if you instead had the following constraints in your configuration:"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "How the cluster translates the above location constraint"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;rsc_location id=\"ping-1\" rsc=\"Webserver\" node=\"sles-1\" score=\"5000\"/&gt;\n"
 "&lt;rsc_location id=\"ping-2\" rsc=\"Webserver\" node=\"sles-2\" score=\"2000\"/&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The advantage is that you don’t have to manually update any constraints whenever your network connectivity changes."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "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 <literal>multiplier</literal> is set to 1000)."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "A more complex example of choosing a location based on connectivity"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\"&gt;\n"
 "   &lt;rule id=\"ping-exclude-rule\" score=\"-INFINITY\" &gt;\n"
 "    &lt;expression id=\"ping-exclude\" attribute=\"pingd\" operation=\"lt\" value=\"3000\"/&gt;\n"
 "   &lt;/rule&gt;\n"
 "   &lt;rule id=\"ping-prefer-rule\" score-attribute=\"pingd\" &gt;\n"
 "    &lt;expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"defined\"/&gt;\n"
 "   &lt;/rule&gt;\n"
 "&lt;/rsc_location&gt;"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Migrating Resources"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Normally, when the cluster needs to move a resource, it fully restarts the resource (i.e. stops the resource on the current node and starts it on the new node)."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "However, some types of resources, such as Xen virtual guests, are able to move to another location without loss of state (often referred to as live migration or hot migration). In pacemaker, this is called resource migration. Pacemaker can be configured to migrate a resource when moving it, rather than restarting it."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "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:"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The resource must be active and healthy at the old location; and"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "everything required for the resource to run must be available on both the old and new locations."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The cluster is able to accommodate both <emphasis>push</emphasis> and <emphasis>pull</emphasis> migration models by requiring the resource agent to support two special actions: <literal>migrate_to</literal> (performed on the current location) and <literal>migrate_from</literal> (performed on the destination)."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "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 <literal>migrate_to</literal> action and, if anything, the activation would occur during <literal>migrate_from</literal>."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Conversely for pull, the <literal>migrate_to</literal> action is practically empty and <literal>migrate_from</literal> does most of the work, extracting the relevant resource state from the old location and activating it."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "There is no wrong or right way for a resource agent to implement migration, as long as it works."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Migration Checklist"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The resource may not be a clone."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The resource must use an OCF style agent."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The resource must not be in a failed or degraded state."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The resource agent must support <literal>migrate_to</literal> and <literal>migrate_from</literal> actions, and advertise them in its metadata."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The resource must have the <literal>allow-migrate</literal> meta-attribute set to <literal>true</literal> (which is not the default)."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "If an otherwise migratable resource depends on another resource via an ordering constraint, there are special situations in which it will be restarted rather than migrated."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "For example, if the resource depends on a clone, and at the time the resource needs to be moved, the clone has instances that are stopping and instances that are starting, then the resource will be restarted. The scheduler is not yet able to model this situation correctly and so takes the safer (if less optimal) path."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Also, if a migratable resource depends on a non-migratable resource, and both need to be moved, the migratable resource will be restarted."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Tracking Node Health"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "A node may be functioning adequately as far as cluster membership is concerned, and yet be \"unhealthy\" in some respect that makes it an undesirable location for resources. For example, a disk drive may be reporting SMART errors, or the CPU may be highly loaded."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Pacemaker offers a way to automatically move resources off unhealthy nodes."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Node Health Attributes"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Pacemaker will treat any node attribute whose name starts with <literal>#health</literal> as an indicator of node health. Node health attributes may have one of the following values:"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Allowed Values for Node Health Attributes"
 msgstr ""
 
 #. Tag: entry
 #, no-c-format
 msgid "Value"
 msgstr ""
 
 #. Tag: entry
 #, no-c-format
 msgid "Intended significance"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>red</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "This indicator is unhealthy <indexterm> <primary>Node health</primary><secondary>red</secondary> </indexterm> <indexterm> <primary>red</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>yellow</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "This indicator is becoming unhealthy <indexterm> <primary>Node health</primary><secondary>yellow</secondary> </indexterm> <indexterm> <primary>yellow</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>green</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "This indicator is healthy <indexterm> <primary>Node health</primary><secondary>green</secondary> </indexterm> <indexterm> <primary>green</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<emphasis>integer</emphasis>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "A numeric score to apply to all resources on this node (0 or positive is healthy, negative is unhealthy) <indexterm> <primary>Node health</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Node Health Strategy"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Pacemaker assigns a node health score to each node, as the sum of the values of all its node health attributes. This score will be used as a location constraint applied to this node for all resources."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The <literal>node-health-strategy</literal> cluster option controls how Pacemaker responds to changes in node health attributes, and how it translates <literal>red</literal>, <literal>yellow</literal>, and <literal>green</literal> to scores."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Allowed values are:"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Node Health Strategies"
 msgstr ""
 
 #. Tag: entry
 #, no-c-format
 msgid "Effect"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>none</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Do not track node health attributes at all. <indexterm> <primary>Node health</primary><secondary>none</secondary> </indexterm> <indexterm> <primary>none</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>migrate-on-red</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Assign the value of <literal>-INFINITY</literal> to <literal>red</literal>, and 0 to <literal>yellow</literal> and <literal>green</literal>. This will cause all resources to move off the node if any attribute is <literal>red</literal>. <indexterm> <primary>Node health</primary><secondary>migrate-on-red</secondary> </indexterm> <indexterm> <primary>migrate-on-red</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>only-green</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Assign the value of <literal>-INFINITY</literal> to <literal>red</literal> and <literal>yellow</literal>, and 0 to <literal>green</literal>. This will cause all resources to move off the node if any attribute is <literal>red</literal> or <literal>yellow</literal>. <indexterm> <primary>Node health</primary><secondary>only-green</secondary> </indexterm> <indexterm> <primary>only-green</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>progressive</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Assign the value of the <literal>node-health-red</literal> cluster option to <literal>red</literal>, the value of <literal>node-health-yellow</literal> to <literal>yellow</literal>, and the value of <literal>node-health-green</literal> to <literal>green</literal>. Each node is additionally assigned a score of <literal>node-health-base</literal> (this allows resources to start even if some attributes are <literal>yellow</literal>). This strategy gives the administrator finer control over how important each value is. <indexterm> <primary>Node health</primary><secondary>progressive</secondary> </indexterm> <indexterm> <primary>progressive</primary> </indexterm>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "<literal>custom</literal>"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Track node health attributes using the same values as <literal>progressive</literal> for <literal>red</literal>, <literal>yellow</literal>, and <literal>green</literal>, but do not take them into account. The administrator is expected to implement a policy by defining rules (see <xref linkend=\"ch-rules\" />) referencing node health attributes. <indexterm> <primary>Node health</primary><secondary>custom</secondary> </indexterm> <indexterm> <primary>custom</primary> </indexterm>"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Measuring Node Health"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Since Pacemaker calculates node health based on node attributes, any method that sets node attributes may be used to measure node health. The most common ways are resource agents or separate daemons."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
-msgid "Pacemaker provides examples that can be used directly or as a basis for custom code. The <literal>ocf:pacemaker:HealthCPU</literal> and <literal>ocf:pacemaker:HealthSMART</literal> resource agents set node health attributes based on CPU and disk parameters. The <literal>ipmiservicelogd</literal> daemon sets node health attributes based on IPMI values (the <literal>ocf:pacemaker:SystemHealth</literal> resource agent can be used to manage the daemon as a cluster resource)."
+msgid "Pacemaker provides examples that can be used directly or as a basis for custom code. The <literal>ocf:pacemaker:HealthCPU</literal> and <literal>ocf:pacemaker:HealthSMART</literal> resource agents set node health attributes based on CPU and disk parameters. The <literal>ipmiservicelogd</literal> daemon sets node health attributes based on IPMI values (the <literal>ocf:pacemaker:SystemHealth</literal> resource agent can be used to manage the daemon as a cluster resource). In order to take advantage of this feature - firstly add the resource to your cluster, preferably as a cloned resource to constatnly measure health on all nodes:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This way <literal>attrd_updater</literal> will set proper status for each node running this resource. Any attribute matching <literal>#health-[a-zA-z]+</literal> will force cluster to migrate all resources from unhealthy node and place it on other nodes according to all constraints defined in your cluster. When the node is no longer faulty you can force the cluster to restart the cloned resource on faulty node and make it available to take resources, in this case since we are using HealthIOWait provider:"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Reloading Services After a Definition Change"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "The cluster automatically detects changes to the definition of services it manages. 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."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "To take advantage of this capability, the resource agent must:"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Accept the <literal>reload</literal> operation and perform any required actions. <emphasis>The actions here depend completely on your application!</emphasis>"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "The DRBD agent’s logic for supporting <literal>reload</literal>"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "case $1 in\n"
 "    start)\n"
 "        drbd_start\n"
 "        ;;\n"
 "    stop)\n"
 "        drbd_stop\n"
 "        ;;\n"
 "    reload)\n"
 "        drbd_reload\n"
 "        ;;\n"
 "    monitor)\n"
 "        drbd_monitor\n"
 "        ;;\n"
 "    *)\n"
 "        drbd_usage\n"
 "        exit $OCF_ERR_UNIMPLEMENTED\n"
 "        ;;\n"
 "esac\n"
 "exit $?"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Advertise the <literal>reload</literal> operation in the <literal>actions</literal> section of its metadata"
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "The DRBD Agent Advertising Support for the <literal>reload</literal> Operation"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;?xml version=\"1.0\"?&gt;\n"
 "  &lt;!DOCTYPE resource-agent SYSTEM \"ra-api-1.dtd\"&gt;\n"
 "  &lt;resource-agent name=\"drbd\"&gt;\n"
 "    &lt;version&gt;1.1&lt;/version&gt;\n"
 "\n"
 "    &lt;longdesc&gt;\n"
 "      Master/Slave OCF Resource Agent for DRBD\n"
 "    &lt;/longdesc&gt;\n"
 "\n"
 "    ...\n"
 "\n"
 "    &lt;actions&gt;\n"
 "      &lt;action name=\"start\"   timeout=\"240\" /&gt;\n"
 "      &lt;action name=\"reload\"  timeout=\"240\" /&gt;\n"
 "      &lt;action name=\"promote\" timeout=\"90\" /&gt;\n"
 "      &lt;action name=\"demote\"  timeout=\"90\" /&gt;\n"
 "      &lt;action name=\"notify\"  timeout=\"90\" /&gt;\n"
 "      &lt;action name=\"stop\"    timeout=\"100\" /&gt;\n"
 "      &lt;action name=\"meta-data\"    timeout=\"5\" /&gt;\n"
 "      &lt;action name=\"validate-all\" timeout=\"30\" /&gt;\n"
 "    &lt;/actions&gt;\n"
 "  &lt;/resource-agent&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Advertise one or more parameters that can take effect using <literal>reload</literal>."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Any parameter with the <literal>unique</literal> set to 0 is eligible to be used in this way."
 msgstr ""
 
 #. Tag: title
 #, no-c-format
 msgid "Parameter that can be changed using reload"
 msgstr ""
 
 #. Tag: programlisting
 #, no-c-format
 msgid "&lt;parameter name=\"drbdconf\" unique=\"0\"&gt;\n"
 "    &lt;longdesc&gt;Full path to the drbd.conf file.&lt;/longdesc&gt;\n"
 "    &lt;shortdesc&gt;Path to drbd.conf&lt;/shortdesc&gt;\n"
 "    &lt;content type=\"string\" default=\"${OCF_RESKEY_drbdconf_default}\"/&gt;\n"
 "&lt;/parameter&gt;"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Once these requirements are satisfied, the cluster will automatically know to reload the resource (instead of restarting) when a non-unique field changes."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "Metadata will not be re-read unless the resource needs to be started. This may mean that the resource will be restarted the first time, even though you changed a parameter with <literal>unique=0</literal>."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid "If both a unique and non-unique field are changed simultaneously, the resource will still be restarted."
 msgstr ""
 
diff --git a/extra/resources/HealthIOWait b/extra/resources/HealthIOWait
new file mode 100755
index 0000000000..0d350af58d
--- /dev/null
+++ b/extra/resources/HealthIOWait
@@ -0,0 +1,177 @@
+#!/bin/sh
+#
+# IOWait RA
+# Measures CPU iowait % via top and writes #health-iowait status into the CIB
+#
+# Originally based on ocf:pacemaker:HealthCPU RA
+# Copyright 2004-2009 SUSE LINUX AG, Lars Marowsky-Brée. All Rights Reserved.
+#
+# Later changes copyright 2009-2018 Michael Schwartzkopff
+# in collaboration with the Bull company. Merci! All Rights Reserved.
+#
+# Later changes copyright 2018 Maciej Sobkowiak <asm@egnyte.com>
+#
+# This source code is licensed under the GNU General Public License version 2
+# (GPLv2) WITHOUT ANY WARRANTY.
+#
+#######################################################################
+# Initialization:
+
+: ${OCF_FUNCTIONS=${OCF_ROOT}/resource.d/heartbeat/.ocf-shellfuncs}
+. ${OCF_FUNCTIONS}
+: ${__OCF_ACTION=$1}
+
+#######################################################################
+
+meta_data() {
+        cat <<END
+<?xml version="1.0"?>
+<!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd">
+<resource-agent name="HealthIOWait" version="1.0">
+<version>1.0</version>
+
+<longdesc lang="en">
+Systhem health agent that measures the CPU iowait via top and updates the #health-iowait attribute.
+</longdesc>
+<shortdesc lang="en">System health based on CPU iowait measurement</shortdesc>
+
+<parameters>
+<parameter name="state" unique="1">
+<longdesc lang="en">
+Location to store the resource state in.
+</longdesc>
+<shortdesc lang="en">State file</shortdesc>
+<content type="string" default="${HA_VARRUN%%/}/health-iowait-${OCF_RESOURCE_INSTANCE}.state" />
+</parameter>
+
+<parameter name="yellow_limit" unique="0">
+<longdesc lang="en">
+Upper limit of iowait percentage to switch the health attribute to yellow. I.e.
+the #health-iowait will go yellow if the %iowait of the CPU gets higher than 10%.
+</longdesc>
+<shortdesc lang="en">Upper limit for yellow health attribute</shortdesc>
+<content type="string" default="10"/>
+</parameter>
+
+<parameter name="red_limit" unique="0">
+<longdesc lang="en">
+Upper limit of iowait percentage to switch the health attribute to red. I.e.
+the #health-iowait will go red if the %iowait of the CPU get higher than 15%.
+</longdesc>
+<shortdesc lang="en">Upper limit for red health attribute</shortdesc>
+<content type="string" default="15"/>
+</parameter>
+
+</parameters>
+
+<actions>
+<action name="start"        timeout="10s" />
+<action name="stop"         timeout="10s" />
+<action name="monitor"      timeout="10s" interval="10s" start-delay="0s" />
+<action name="meta-data"    timeout="5s" />
+<action name="validate-all" timeout="10s" />
+</actions>
+</resource-agent>
+END
+}
+
+#######################################################################
+
+agent_usage() {
+        cat <<END
+usage: $0 {start|stop|monitor|validate-all|meta-data}
+
+Expects to have a fully populated OCF RA-compliant environment set.
+END
+}
+
+agent_start() {
+    agent_monitor
+    if [ $? =  $OCF_SUCCESS ]; then
+      return $OCF_SUCCESS
+    fi
+    touch "${OCF_RESKEY_state}"
+}
+
+agent_stop() {
+    agent_monitor
+    if [ $? =  $OCF_SUCCESS ]; then
+        rm ${OCF_RESKEY_state}
+    fi
+    return $OCF_SUCCESS
+}
+
+agent_monitor() {
+        # Monitor _MUST!_ differentiate correctly between running
+        # (SUCCESS), failed (ERROR) or _cleanly_ stopped (NOT RUNNING).
+        # That is THREE states, not just yes/no.
+        if [ -f ${OCF_RESKEY_state} ]; then
+          WAIT=`top -b -n2 | grep Cpu | tail -1 | awk -F",|.[0-9][ %]wa" '{ print $5 }'`
+          # echo "System iowait: " $WAIT
+          # echo $OCF_RESKEY_yellow_limit
+          if [ $WAIT -gt ${OCF_RESKEY_red_limit} ] ; then
+            # echo "System state RED!"
+            attrd_updater -n "#health-iowait" -U "red" -d "5s"
+            return $OCF_SUCCESS
+          fi
+
+          if [ $WAIT -gt ${OCF_RESKEY_yellow_limit} ] ; then
+            # echo "System state yellow."
+            attrd_updater -n "#health-iowait" -U "yellow" -d "5s"
+          else
+            # echo "System state green."
+            attrd_updater -n "#health-iowait" -U "green" -d "5s"
+          fi
+          return $OCF_SUCCESS
+        fi
+        return $OCF_NOT_RUNNING
+}
+
+agent_validate() {
+    # Is the state directory writable?
+    state_dir=`dirname "$OCF_RESKEY_state"`
+    if [ -d "$state_dir" ] && [ -w "$state_dir" ] && [ -x "$state_dir" ]; then
+      return $OCF_ERR_ARGS
+    fi
+    return $OCF_SUCCESS
+}
+
+: ${OCF_RESKEY_CRM_meta_interval=0}
+: ${OCF_RESKEY_CRM_meta_globally_unique:="false"}
+
+if [ "x$OCF_RESKEY_state" = "x" ]; then
+    if [ ${OCF_RESKEY_CRM_meta_globally_unique} = "false" ]; then
+      state="${HA_VARRUN%%/}/HealthIoWait-${OCF_RESOURCE_INSTANCE}.state"
+      #Strip off the trailing clone marker
+      OCF_RESKEY_state=`echo $state | sed s/:[0-9][0-9]*\.state/.state/`
+    else
+      OCF_RESKEY_state="${HA_VARRUN%%/}/HealthIoWait-${OCF_RESOURCE_INSTANCE}.state"
+    fi
+fi
+
+if [ "x${OCF_RESKEY_red_limit}" = "x" ] ; then
+  OCF_RESKEY_red_limit=15
+fi
+
+if [ "x${OCF_RESKEY_yellow_limit}" = "x" ] ; then
+  OCF_RESKEY_yellow_limit=10
+fi
+
+case $__OCF_ACTION in
+meta-data)      meta_data
+                exit $OCF_SUCCESS
+                ;;
+start)          agent_start;;
+stop)           agent_stop;;
+monitor)        agent_monitor;;
+validate-all)   agent_validate;;
+usage|help)     agent_usage
+                exit $OCF_SUCCESS
+                ;;
+*)              agent_usage
+                exit $OCF_ERR_UNIMPLEMENTED
+                ;;
+esac
+rc=$?
+ocf_log debug "${OCF_RESOURCE_INSTANCE} $__OCF_ACTION : $rc"
+exit $rc
diff --git a/extra/resources/Makefile.am b/extra/resources/Makefile.am
index be2b54d42e..bf45015f18 100644
--- a/extra/resources/Makefile.am
+++ b/extra/resources/Makefile.am
@@ -1,54 +1,55 @@
 # Makefile.am for OCF RAs
 #
 # Author: Andrew Beekhof
 # Copyright (C) 2008 Andrew Beekhof
 #
 # This program is free software; you can redistribute it and/or
 # modify it under the terms of the GNU General Public License
 # as published by the Free Software Foundation; either version 2
 # of the License, or (at your option) any later version.
 # 
 # This program is distributed in the hope that it will be useful,
 # but WITHOUT ANY WARRANTY; without even the implied warranty of
 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 # GNU General Public License for more details.
 # 
 # You should have received a copy of the GNU General Public License
 # along with this program; if not, write to the Free Software
 # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.
 #
 include $(top_srcdir)/Makefile.common
 
 EXTRA_DIST		= $(ocf_SCRIPTS)
 
 
 ocfdir		    = @OCF_RA_DIR@/pacemaker
 
 ocf_SCRIPTS	     =  ClusterMon 	\
 			controld	\
 			Dummy		\
 			HealthCPU	\
+                        HealthIOWait    \
 			HealthSMART	\
 			ifspeed		\
 			o2cb		\
 			ping		\
 			pingd		\
 			Stateful	\
 			SysInfo		\
 			SystemHealth \
 			attribute	\
 			remote
 
 if BUILD_XML_HELP
 
 man7_MANS = $(ocf_SCRIPTS:%=ocf_pacemaker_%.7)
 DBOOK_OPTS = --stringparam command.prefix ocf_pacemaker_ --stringparam variable.prefix OCF_RESKEY_ --param man.vol 7
 
 ocf_pacemaker_%.xml:  %
 	$(AM_V_GEN)OCF_FUNCTIONS=/dev/null OCF_ROOT=$(OCF_ROOT_DIR) $(abs_builddir)/$< meta-data > $@
 
 endif
 
 clean-generic:
 	rm -f $(man7_MANS) $(ocf_SCRIPTS:%=%.xml) *~