From Ken Gaillot:
I plan to rebase pacemaker in 6.8 in another week or so, which means
that it will have everything that went into 7.2, so you can reuse those
It will be based on pacemaker 1.1.14, which has these new features
(which I think are all in 7.2 already):
If you have any questions, don't hesitate to ask.
Just to put the info here (with comments). I will send a separate email to Ken Gaillot with these questions...
* 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.
COMMENT: Not sure this affects the doc -- no change to the interface. Need to check with Ken.
* Fencing topology levels can now be applied to all nodes whose name
matches a configurable pattern, or that have a configurable node attribute.
COMMENT: I don't think I documented this for RHEL 7.2. I need to send the section on Configuring Fencing Levels to Ken for an example. For RHEL 7 it is this:
For RHEL 6 it is this:
* When a fencing topology level has multiple devices, reboots are now
automatically mapped to all-off-then-all-on, allowing much simplified
configuration of redundant power supplies.
I think this is the section we added for RHEL 7.2 that we need to add for RHEL 6.8:
* Guest nodes can now be included in groups, which simplifies the common
Pacemaker Remote use case of a grouping a storage device, filesystem and VM.
I will wholly replace the Pacemaker remote section with the 7.3 draft. I will add a sentence after the instructions for creating a guest node resource
"As of Red Hat Enterprise Linux 7.3, you can include guest nodes in groups,
which allows you to group a storage device, file system, and VM." For 6.8, I will note 6.8.
* Clone resources have 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.
We don't currently document any metadata options for clone resources. I will ask Ken about this.
This update has been on the Portal since RHEL 6.8 so I am closing this BZ.