[Pacemaker] Time to get ready for 1.1.11

Thu Jan 16 04:00:20 UTC 2014

Hi,

Just curious,
I found that RC4 has been branched out of the master after RC3.

What would the fixes only in the master branch be in the future?
Are they going to be merged into 1.1.12 someday and just skipping 1.1.11?
Or are they separated for the next major version such as v1.2 or v2.0?

Thanks,

2014/1/16 David Vossel <dvossel at redhat.com>:
> ----- Original Message -----
>> From: "David Vossel" <dvossel at redhat.com>
>> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
>> Sent: Tuesday, January 7, 2014 4:50:11 PM
>> Subject: Re: [Pacemaker] Time to get ready for 1.1.11
>>
>> ----- Original Message -----
>> > From: "Andrew Beekhof" <andrew at beekhof.net>
>> > To: "The Pacemaker cluster resource manager"
>> > <pacemaker at oss.clusterlabs.org>
>> > Sent: Thursday, December 19, 2013 2:25:00 PM
>> > Subject: Re: [Pacemaker] Time to get ready for 1.1.11
>> >
>> >
>> > On 20 Dec 2013, at 2:11 am, Andrew Martin <amartin at xes-inc.com> wrote:
>> >
>> > > David/Andrew,
>> > >
>> > > Once 1.1.11 final is released, is it considered the new stable series of
>> > > Pacemaker,
>> >
>> > yes
>> >
>> > > or should 1.1.10 still be used in very stable/critical production
>> > > environments?
>> > >
>> > > Thanks,
>> > >
>> > > Andrew
>> > >
>> > > ----- Original Message -----
>> > >> From: "David Vossel" <dvossel at redhat.com>
>> > >> To: "The Pacemaker cluster resource manager"
>> > >> <pacemaker at oss.clusterlabs.org>
>> > >> Sent: Wednesday, December 11, 2013 3:33:46 PM
>> > >> Subject: Re: [Pacemaker] Time to get ready for 1.1.11
>> > >>
>> > >> ----- Original Message -----
>> > >>> From: "Andrew Beekhof" <andrew at beekhof.net>
>> > >>> To: "The Pacemaker cluster resource manager"
>> > >>> <pacemaker at oss.clusterlabs.org>
>> > >>> Sent: Wednesday, November 20, 2013 9:02:40 PM
>> > >>> Subject: [Pacemaker] Time to get ready for 1.1.11
>> > >>>
>> > >>> With over 400 updates since the release of 1.1.10, its time to start
>> > >>> thinking about a new release.
>> > >>>
>> > >>> Today I have tagged release candidate 1[1].
>> > >>> The most notable fixes include:
>> > >>>
>> > >>>  + attrd: Implementation of a truely atomic attrd for use with corosync
>> > >>>  2.x
>> > >>>  + cib: Allow values to be added/updated and removed in a single update
>> > >>>  + cib: Support XML comments in diffs
>> > >>>  + Core: Allow blackbox logging to be disabled with SIGUSR2
>> > >>>  + crmd: Do not block on proxied calls from pacemaker_remoted
>> > >>>  + crmd: Enable cluster-wide throttling when the cib heavily exceeds
>> > >>>  its
>> > >>>  target load
>> > >>>  + crmd: Use the load on our peers to know how many jobs to send them
>> > >>>  + crm_mon: add --hide-headers option to hide all headers
>> > >>>  + crm_report: Collect logs directly from journald if available
>> > >>>  + Fencing: On timeout, clean up the agent's entire process group
>> > >>>  + Fencing: Support agents that need the host to be unfenced at startup
>> > >>>  + ipc: Raise the default buffer size to 128k
>> > >>>  + PE: Add a special attribute for distinguishing between real nodes
>> > >>>  and
>> > >>>  containers in constraint rules
>> > >>>  + PE: Allow location constraints to take a regex pattern to match
>> > >>>  against
>> > >>>  resource IDs
>> > >>>  + pengine: Distinguish between the agent being missing and something
>> > >>>  the
>> > >>>  agent needs being missing
>> > >>>  + remote: Properly version the remote connection protocol
>> > >>>  + services: Detect missing agents and permission errors before forking
>> > >>>  + Bug cl#5171 - pengine: Don't prevent clones from running due to
>> > >>>  dependant
>> > >>>  resources
>> > >>>  + Bug cl#5179 - Corosync: Attempt to retrieve a peer's node name if it
>> > >>>  is
>> > >>>  not already known
>> > >>>  + Bug cl#5181 - corosync: Ensure node IDs are written to the CIB as
>> > >>>  unsigned integers
>> > >>>
>> > >>> If you are a user of `pacemaker_remoted`, you should take the time to
>> > >>> read
>> > >>> about changes to the online wire protocol[2] that are present in this
>> > >>> release.
>> > >>>
>> > >>> [1]
>> > >>> https://github.com/ClusterLabs/pacemaker/releases/Pacemaker-1.1.11-rc1
>> > >>> [2]
>> > >>> http://blog.clusterlabs.org/blog/2013/changes-to-the-remote-wire-protocol/
>> > >>>
>> > >>> To build `rpm` packages for testing:
>> > >>>
>> > >>> 1. Clone the current sources:
>> > >>>
>> > >>>       # git clone --depth 0 git://github.com/ClusterLabs/pacemaker.git
>> > >>>       # cd pacemaker
>> > >>>
>> > >>> 1. If you haven't already, install Pacemaker's dependancies
>> > >>>
>> > >>>       [Fedora] # sudo yum install -y yum-utils
>> > >>>       [ALL]     # make rpm-dep
>> > >>>
>> > >>> 1. Build Pacemaker
>> > >>>
>> > >>>       # make rc
>> > >>>
>> > >>> 1. Copy the rpms and deploy as needed
>> > >>>
>> > >>
>> > >> A new release candidate, Pacemaker-1.1.11-rc2, is ready for testing.
>> > >> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.11-rc2
>> > >>
>> > >> Assuming no major regressions are encountered during testing, this tag
>> > >> will
>> > >> become the final Pacemaker-1.1.11 release a week from today.
>> > >>
>> > >> -- Vossel
>>
>> Alright, New RC time. Pacemaker-1.1.11-rc3.
>>
>> If no regressions are encountered, rc3 will become the 1.1.11 final release a
>> week from today.
>>
>> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.11-rc3
>>
>> CHANGES RC2 vs RC3
>> Fix: ipc: fix memory leak for failed ipc client connections.
>> Fix: pengine: Fixes memory leak in regex pattern matching code for
>> constraints.
>> Low: Avoid potentially misleading and inaccurate compression time log msg
>> Fix: crm_report: Suppress logging errors after the target directory has been
>> compressed
>> Fix: crm_attribute: Do not swallow hostname lookup failures
>> Fix: crmd: Avoid deleting the 'shutdown' attribute
>> Log: attrd: Quote attribute names
>> Doc: Pacemaker_Explained: Fix formatting
>>
>
> A new release candidate for pacemaker 1.1.11 is now available, pacemaker-1.1.11-rc4.
>
> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.11-rc4
>
> The lrmd crash has finally been resolved. That was the last fix we were waiting on before officially releasing Pacemaker v1.1.11.  RC4 is likely going to be the 1.1.11 final release. Please test and report any regressions as soon as possible.  1.1.11 will be released mid next week if no major issues are encountered.
>
> CHANGES RC3 to RC4
> Fix: stonith_admin: Ensure pointers passed to sscanf() are properly initialized
> Fix: Prevent potential use-of-NULL
> Fix: upstart: Allow comilation with glib versions older than 2.28
> Fix: services: Fixes segfault associated with cancelling in-flight recurring operations.
> Low: crmd: Change the default value of node-action-limit
>
> Thanks,
> -- Vossel
>
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-- 
Keisuke MORI