[ClusterLabs] Coming in Pacemaker 2.0.3: of interest to packagers and users who compile their own builds

Ken Gaillot kgaillot at redhat.com
Fri Oct 11 21:56:25 EDT 2019

Hi all,

The following build-related changes arriving in Pacemaker 2.0.3 are
minor and unlikely to affect anyone, but may be of interest to
distribution packagers and users who compile pacemaker themselves.

The configure script now has options to override the default values of
pretty much everything in a pacemaker install that requires root
privileges. These include (shown with their usual values):

  --with-runstatedir           /run or /var/run
  --with-systemdsystemunitdir  /usr/lib/systemd/system
  --with-ocfdir                /usr/lib/ocf
  --with-daemon-user           hacluster
  --with-daemon-group          haclient

Changing these may result in non-functional binaries unless all other
relevant software has been built with the same values, but it allows
non-root sandbox builds of pacemaker for testing purposes.

The configure script options --with-pkgname and --with-pkg-name have
long been unused. They are now officially deprecated and will be
removed in a future version of pacemaker.

The basic process for building pacemaker has been "./autogen.sh;
./configure; make". Now, if you don't need to change any defaults, you
can just run "make" in a clean source tree and it will run autogen.sh
and/or configure if needed.

"make export", "make dist", "make distcheck", and VPATH builds (i.e.
different source and build trees) should now all work as intended, and
pacemaker should build correctly in a source distribution (as opposed
to a git checkout).

The concurrent-fencing cluster property currently defaults to false. We
plan to change the default to true in a future version of pacemaker
(whenever the next minor version bump will be). Anyone who wants the
new default earlier can set "-DDEFAULT_CONCURRENT_FENCING_TRUE" in
CPPFLAGS before building.

When building RPM packages with "make rpm", pacemaker previously put
the RPM sources, spec file, and source rpm in the top-level build
directory, letting everything else (such as binary rpms) use the system
defaults (typically beneath the user's home directory). That will
remain the default behavior, but the new option "make RPMDEST=subtree
rpm" will put the RPM sources in the top-level build directory and
everything else in a dedicated "rpm" subdirectory of the build tree.
This keeps everything self-contained, which may be useful in certain
Ken Gaillot <kgaillot at redhat.com>

More information about the Users mailing list