[ClusterLabs] Pacemaker 1.1.13 Release cycle begins!

Andrei Borzenkov arvidjaar at gmail.com
Fri Mar 27 04:37:56 EDT 2015

В Fri, 27 Mar 2015 16:18:38 +1100
Andrew Beekhof <andrew at beekhof.net> пишет:

> I know I've been threatening this for a while, but I'm pleased to report that the release cycle for 1.1.13 has finally begun.
> The full changelog is rather long and available at:
>    https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.13-rc1
> but the highlights are:
> - Allow fail-counts to be removed en-mass when the new attrd is in operation
> - attrd_updater: Allow attributes to be set for other nodes
> - attrd_updater: support --query and --all options
> - attrd_updater: support private attributes
> - crmd: If configured, trigger the watchdog immediately if we loose quorum and no-quorum-policy=suicide
> - crm_resource: Implement an intelligent restart capability
> - crm_resource: Implement a --wait option for scripts to block with until the changes take place 
> - Fencing: Allow the cluster to recover resources if the watchdog is in use
> - fencing: cl#5134 - Support random fencing delay to avoid double fencing
> - mcp: Turn on sbd integration if pacemakerd finds it running
> - penigne: Allow natural ordering of colocation sets
> - pengine: Per-node control over resource discovery
> - pengine: Support non-actionable degraded mode for OCF

Is it possible for a single resource agent to support both old and new
version? Or any agent willing to optionally support degraded mode will
have hard requirement for 1.1.13 version?

> - Support machine panics for some kinds of errors (via sbd if available)
> - ipc: use server enforced buffer during ipc client send
> At this stage integration testing results are pretty solid but any testing feedback would be welcome.
> In particular though we need testing of:
> - sbd integration
> - private attrd attributes (attributes not written to the cib)
> - crm_resource --restart and --wait
> - the resource-discovery capabilities
> With the release cycle underway, anything intended for the release needs to be a pull request against the 1.1 branch.
> Features and low-priority changes can still be submitted against master.
> -- Andrew
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

More information about the Users mailing list