[ClusterLabs] Final Pacemaker 2.0.3 release now available

[Ken Gaillot]

On Mon, 2019-11-25 at 23:02 -0500, Digimer wrote:
> Congrats!
> 
> Can I ask, when might fencing become required? Is that still in the
> works, or has it been shelved?
> 
> digimer

tl;dr shelved

The original plan for 2.0.0 was to get rid of the stonith-enabled flag,
but still allow disabling stonith via "requires=quorum" in
rsc_defaults.

Certain resources, such as stonith devices themselves or simple nagios
checks, can be immediately started elsewhere even if their original
node needs to be fenced. requires=quorum was designed for such
resources. Setting that for all resources would make fencing largely
irrelevant.

That was shelved when I realized the code would have to be considerably
more complicated to go that route. Also, someone could theoretically
want "requires=quorum" for all resources while still wanting nodes to
be fenced if they are lost.

> On 2019-11-25 9:32 p.m., Ken Gaillot wrote:
> > Hi all,
> > 
> > The final release of Pacemaker version 2.0.3 is now available at:
> > 
> > https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.3
> > 
> > Highlights include:
> > 
> > * A dynamic cluster recheck interval (you don't have to care about
> > changing cluster-recheck-interval when using failure-timeout or
> > most
> > rules)
> > 
> > * Pacemaker Remote options for security hardening (listen address
> > and
> > TLS priorities)
> > 
> > * crm_mon supports the --output-as/--output-to options, has some
> > tweaks
> > to text and HTML output that will hopefully make it easier to read,
> > has
> > a correct count of disabled and blocked resources, and supports an
> > option to set a stylesheet for HTML output
> > 
> > * A new fence-reaction cluster option controls whether the local
> > node
> > stops pacemaker or panics the local host when notified of its own
> > fencing (which can happen with fabric fencing agents such as
> > fence_scsi)
> > 
> > * Documentation improvements include a new chapter about ACLs
> > (replacing an outdated text file) in "Pacemaker Explained" and
> > another
> > one about the command-line tools in "Pacemaker Administration":
> > 
> > https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemaker_Explained/index.html#idm47160746093920
> > 
> > https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemaker_Administration/index.html#idm47051359032720
> > 
> > As usual, there were bug fixes and log message improvements as
> > well.
> > Most significantly, a regression introduced in 2.0.2 that
> > effectively
> > disabled concurrent-fencing has been fixed, and an invalid
> > transition
> > (blocking all further resource actions) has been fixed when both a
> > guest node or bundle and the host running it needs to be fenced,
> > but
> > can't (due to quorum loss, for example).
> > 
> > For more details about changes in this release, see:
> > 
> > https://github.com/ClusterLabs/pacemaker/blob/2.0/ChangeLog
> > 
> > Many thanks to all contributors of source code to this release,
> > including Aleksei Burlakov, Chris Lumens, Gao,Yan, Hideo Yamauchi,
> > Jan
> > Pokorný, John Eckersberg, Kazunori INOUE, Ken Gaillot, Klaus
> > Wenninger,
> > Konstantin Kharlamov, Munenari, Roger Zhou, S. Schuberth, Tomas
> > Jelinek, and Yuusuke Iida.
> > 
> > Version 1.1.22, with selected backports from this release, will
> > also be
> > released soon.
> > 
> 
> 
-- 
Ken Gaillot <kgaillot at redhat.com>