[ClusterLabs] Pacemaker 2.0.0-rc1 now available

Ken Gaillot kgaillot at redhat.com
Fri Feb 16 16:06:06 EST 2018

Source code for the first release candidate for Pacemaker version 2.0.0
is now available at:


The main goal of the change from Pacemaker 1 to 2 is to drop support
for deprecated legacy usage, in order to make the code base more
maintainable going into the future. As such, this release involves a
net drop of more than 20,000 lines of code!

Rolling (live) upgrades are possible only from Pacemaker 1.1.11 or
later, on top of corosync 2. Other setups can be upgraded with the
cluster stopped.

It is recommended to run "cibadmin --upgrade" (or the equivalent in
your higher-level tool of choice) both before and after the upgrade.

The final 2.0.0 release will automatically transform most of the
dropped older syntax to the newer form. However, this functionality is
not yet complete in rc1.

The most significant changes in this release include:

* Support has been dropped for heartbeat and corosync 1 (whether using
CMAN or plugin), and many legacy aliases for cluster options (including
default-resource-stickiness, which should be set as resource-stickiness 
in rsc_defaults instead).

* The default location of the Pacemaker detail log is now
/var/log/pacemaker/pacemaker.log, and Pacemaker will no longer use
Corosync's logging preferences. Options are available in the configure
script to change the default log locations.

* The master XML tag is deprecated (though still supported) in favor of
using the standard clone tag with a new "promotable" meta-attribute set
to true. The "master-max" and "master-node-max" master meta-attributes
are deprecated in favor of new "promoted-max" and "promoted-node-max"
clone meta-attributes. Documentation now refers to these as promotable
clones rather than master/slave, stateful or multistate clones.

* The record-pending option now defaults to true, which means pending
actions will be shown in status displays.

* Three minor regressions introduced in 1.1.18, and one introduced in
1.1.17, have been fixed.

More details are available in the change log:


and in a special wiki page for the 2.0 release:


Everyone is encouraged to download, compile and test the new release.
We do many regression tests and simulations, but we can't cover all
possible use cases, so your feedback is important and appreciated.

Many thanks to all contributors of source code to this release,
Ken Gaillot <kgaillot at redhat.com>

More information about the Users mailing list