[ClusterLabs] Pacemaker 2.0.3-rc3 now available

[Ken Gaillot]

The third, and possibly final, release candidate for Pacemaker 2.0.3 is
now available at:

https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.3-rc3

If there are no serious issues found in this release, I will release it
as the final 2.0.3 in another week or so.

This fixes some more minor regressions in crm_mon introduced in rc1.
Additionally, after feedback from this list, the new output format
options were shortened. The help is now:

Output Options:
  --output-as=FORMAT       Specify output format as one of: console (default), html, text, xml
  --output-to=DEST         Specify file name for output (or "-" for stdout)
  --html-cgi               Add CGI headers (requires --output-as=html)
  --html-stylesheet=URI    Link to an external stylesheet (requires --output-as=html)
  --html-title=TITLE       Specify a page title (requires --output-as=html)
  --text-fancy             Use more highly formatted output (requires --output-as=text)

A longstanding display issue in crm_mon has been fixed. The disabled
and blocked resources count was previously incorrect. The new, accurate
count changes the text from "resources" to "resource instances",
because individual instances of a cloned or bundled resource can be
blocked. For example, if you have one regular resource, and a cloned
resource running on three nodes, it would count as 4 resource
instances.

A longstanding pain point in the logs has been improved. Whenever the
scheduler processes resource history, it logs a warning for any
failures it finds, regardless of whether they are new or old, which can
confuse anyone reading the logs. Now, the log will contain the time of
the failure, so it's obvious whether you're seeing the same event or
not. The log will also contain the exit reason if one was provided by
the resource agent, for easier troubleshooting.

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.
-- 
Ken Gaillot <kgaillot at redhat.com>