Re: [ClusterLabs] Pacemaker 1.1.16 released
On Fri, 2 Dec 2016 13:44:59 -0600 Ken Gaillotwrote: > On 12/01/2016 11:58 AM, Jehan-Guillaume de Rorthais wrote: > > > > > > Le 1 décembre 2016 17:39:45 GMT+01:00, Ken Gaillot a > > écrit : > >> On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: > >>> On Wed, 30 Nov 2016 14:05:19 -0600 > >>> Ken Gaillot wrote: > >>> > ClusterLabs is proud to announce the latest release of the Pacemaker > cluster resource manager, version 1.1.15. > >>> > >>> 1.1.6 I guess ;) > >> > >> Whoops! > >> > >> Well now I don't feel so bad since the correction is wrong too ;) > > > > Argh !! :-D > > > > What about my questions bellow BTW ? :-P > > > >>> But congrats anyway ! > >>> > * 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.) > >>> > >>> * how could we get the "CRM feature set" version from the RA? > > it's passed as an environment variable > > >>> * when this "CRM feature set" has been introduced in Pacemaker? > > always, see http://wiki.clusterlabs.org/wiki/ReleaseCalendar Thank you for the answers! Regards, ___ 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
Re: [ClusterLabs] Pacemaker 1.1.16 released
On 12/01/2016 11:58 AM, Jehan-Guillaume de Rorthais wrote: > > > Le 1 décembre 2016 17:39:45 GMT+01:00, Ken Gaillota > écrit : >> On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: >>> On Wed, 30 Nov 2016 14:05:19 -0600 >>> Ken Gaillot wrote: >>> ClusterLabs is proud to announce the latest release of the Pacemaker cluster resource manager, version 1.1.15. >>> >>> 1.1.6 I guess ;) >> >> Whoops! >> >> Well now I don't feel so bad since the correction is wrong too ;) > > Argh !! :-D > > What about my questions bellow BTW ? :-P > >>> But congrats anyway ! >>> * 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.) >>> >>> * how could we get the "CRM feature set" version from the RA? it's passed as an environment variable >>> * when this "CRM feature set" has been introduced in Pacemaker? always, see http://wiki.clusterlabs.org/wiki/ReleaseCalendar ___ 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
Re: [ClusterLabs] Pacemaker 1.1.16 released
Le 1 décembre 2016 17:39:45 GMT+01:00, Ken Gaillota écrit : >On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: >> On Wed, 30 Nov 2016 14:05:19 -0600 >> Ken Gaillot wrote: >> >>> ClusterLabs is proud to announce the latest release of the Pacemaker >>> cluster resource manager, version 1.1.15. >> >> 1.1.6 I guess ;) > >Whoops! > >Well now I don't feel so bad since the correction is wrong too ;) Argh !! :-D What about my questions bellow BTW ? :-P >> But congrats anyway ! >> >>> * 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.) >> >> * how could we get the "CRM feature set" version from the RA? >> * when this "CRM feature set" has been introduced in Pacemaker? >> >> Regards, >> -- Sent from my phone ___ 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
Re: [ClusterLabs] Pacemaker 1.1.16 released
On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: > On Wed, 30 Nov 2016 14:05:19 -0600 > Ken Gaillotwrote: > >> ClusterLabs is proud to announce the latest release of the Pacemaker >> cluster resource manager, version 1.1.15. > > 1.1.6 I guess ;) Whoops! Well now I don't feel so bad since the correction is wrong too ;) > But congrats anyway ! > >> * 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.) > > * how could we get the "CRM feature set" version from the RA? > * when this "CRM feature set" has been introduced in Pacemaker? > > Regards, > ___ 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
Re: [ClusterLabs] Pacemaker 1.1.16 released
On Wed, 30 Nov 2016 14:05:19 -0600 Ken Gaillotwrote: > ClusterLabs is proud to announce the latest release of the Pacemaker > cluster resource manager, version 1.1.15. 1.1.6 I guess ;) But congrats anyway ! > * 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.) * how could we get the "CRM feature set" version from the RA? * when this "CRM feature set" has been introduced in Pacemaker? Regards, -- Jehan-Guillaume de Rorthais Dalibo ___ 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
[ClusterLabs] Pacemaker 1.1.16 released
ClusterLabs is proud to announce the latest release of the Pacemaker cluster resource manager, version 1.1.15. The source code is available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.16 The most significant enhancements in this release are: * rsc-pattern may now be used instead of rsc in location constraints, to allow a single location constraint to apply to all resources whose names match a regular expression. Sed-like %0 - %9 backreferences let submatches be used in node attribute names in rules. * The new ocf:pacemaker:attribute resource agent sets a node attribute according to whether the resource is running or stopped. This may be useful in combination with attribute-based rules to model dependencies that simple constraints can't handle. * Pacemaker's existing "node health" feature allows resources to move off nodes that become unhealthy. Now, when using node-health-strategy=progressive, a new cluster property node-health-base will be used as the initial health score of newly joined nodes (defaulting to 0, which is the previous behavior). This allows a node to be treated as "healthy" even if it has some "yellow" health attributes, which can be useful to allow clones to run on such nodes. * 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.) * Watchdog-based fencing using sbd now works better on remote nodes. This capability still likely has some limitations, however. * The build process now takes advantage of various compiler features (RELRO, PIE, as-needed linking, etc.) that enhance security and start-up performance. See the "Hardening flags" comments in the configure.ac file for more details. * Python 3 compatibility: The Pacemaker project now targets compatibility with both python 2 (versions 2.6 and later) and python 3 (versions 3.2 and later). All of the project's python code now meets this target, with the exception of CTS, which is still python 2 only. * The Pacemaker coding guidelines have been replaced by a more comprehensive addition to the documentation set, "Pacemaker Development". It is intended for developers working on the Pacemaker code base itself, rather than external code such as resource agents. A copy is viewable at http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Development/ As usual, the release includes many bugfixes, including a fix for a serious security vulnerability (CVE-2016-7035). For a more detailed list of changes, see the change log: https://github.com/ClusterLabs/pacemaker/blob/1.1/ChangeLog Many thanks to all contributors of source code to this release, including Andrew Beekhof, Bin Liu, Christian Schneider, Christoph Berg, David Shane Holden, Ferenc Wágner, Yan Gao, Hideo Yamauchi, Jan Pokorný, Ken Gaillot, Klaus Wenninger, Kostiantyn Ponomarenko, Kristoffer Grönlund, Lars Ellenberg, Masatake Yamato, Michal Koutný, Nakahira Kazutomo, Nate Clark, Nishanth Aravamudan, Oyvind Albrigtsen, Ruben Kerkhof, Tim Bishop, Vladislav Bogdanov and Yusuke Iida. Apologies if I have overlooked anyone. -- Ken Gaillot___ 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