New Pacemaker features
The Red Hat Enterprise Linux 6.8 release supports the following Pacemaker features:
* You can now use the "pcs resource relocate run" command to move a resource to its preferred node, as determined by current cluster status, constraints, location of resources and other settings.
* When configuring fencing for redundant power supplies, you now are only required to define each device once and to specify that both devices are required to fence the node.
* The new `resource-discovery` location constraint option allows you to indicate whether Pacemaker should perform resource discovery on a node for a specified resource.
* Resources will now start as soon as their state has been confirmed on all nodes and all dependencies have been satisfied, rather than waiting for the state of all resources to be confirmed. This allows for faster startup of some services, and more even startup load.
* Clone resources support a new `clone-min` metadata option, specifying that a certain number of instances must be running before any dependent resources can run. This is particularly useful for services behind a virtual IP and haproxy, as is often done with OpenStack.
These features are documented in "Configuring the Red Hat High Availability Add-On with Pacemaker", available at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/index.html.