On 11/04/2016 02:53 AM, Jan Pokorný wrote: > On 04/11/16 08:29 +0100, Ulrich Windl wrote: >> Ken Gaillot <kgail...@redhat.com> schrieb am 03.11.2016 um 17:08 in >> Nachricht <8af2ff98-05fd-a2c7-f670-58d0ff68e...@redhat.com>: >>> ClusterLabs is happy to announce the first release candidate for >>> Pacemaker version 1.1.16. Source code is available at: >>> >>> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.16-rc1 >>> >>> The most significant enhancements in this release are: >>> >>> [...] >>> >>> * Previously, the OCF_RESKEY_CRM_meta_notify_active_* variables were not >>> properly passed to multistate resources with notification enabled. This >>> has been fixed. To help resource agents detect when the fix is >>> available, the CRM feature set has been incremented. (Whenever the >>> feature set changes, mixed-version clusters are supported only during >>> rolling upgrades -- nodes with an older version will not be allowed to >>> rejoin once they shut down.) >> >> Where can I find a description of current "CRM feature sets"? > > It's originally internal-only versioning for cluster to know which > node has the oldest software and hence is predestined to be DC > (in rolling update scenario). > > Ken recently mapped these versions (together with LRMD protocol > versions relevant in the context of pacemaker remote communication) > to proper release versions: http://clusterlabs.org/wiki/ReleaseCalendar
There is also a description of how the cluster uses the CRM feature set in the new upgrade documentation: http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#_rolling_node_by_node _______________________________________________ Users mailing list: Users@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