[ClusterLabs] Changes coming in Pacemaker 2.0.0

[Jehan-Guillaume de Rorthais]

On Mon, 15 Jan 2018 11:05:52 -0600
Ken Gaillot <kgaillot at redhat.com> wrote:

> On Thu, 2018-01-11 at 10:24 -0600, Ken Gaillot wrote:
> > On Thu, 2018-01-11 at 01:21 +0100, Jehan-Guillaume de Rorthais wrote:  
> > > On Wed, 10 Jan 2018 16:10:50 -0600
> > > Ken Gaillot <kgaillot at redhat.com> wrote:
> > >   
> > > > Pacemaker 2.0 will be a major update whose main goal is to remove
> > > > support for deprecated, legacy syntax, in order to make the code
> > > > base
> > > > more maintainable into the future. There will also be some
> > > > changes
> > > > to
> > > > default configuration behavior, and the command-line tools.
> > > > 
> > > > I'm hoping to release the first release candidate in the next
> > > > couple of
> > > > weeks.  
> > > 
> > > Great news! Congrats.
> > >   
> > > > We'll have a longer than usual rc phase to allow for plenty of
> > > > testing.
> > > > 
> > > > A thoroughly detailed list of changes will be maintained on the
> > > > ClusterLabs wiki:
> > > > 
> > > >   https://wiki.clusterlabs.org/wiki/Pacemaker_2.0_Changes
> > > > 
> > > > These changes are not final, and we can restore functionality if
> > > > there
> > > > is a strong need for it. Most user-visible changes are complete
> > > > (in
> > > > the
> > > > 2.0 branch on github); major changes are still expected, but
> > > > primarily
> > > > to the C API.
> > > > 
> > > > Some highlights:
> > > > 
> > > > * Only Corosync version 2 will be supported as the underlying
> > > > cluster
> > > > layer. Support for Heartbeat and Corosync 1 is removed. (Support
> > > > for
> > > > the new kronosnet layer will be added in a future version.)  
> > > 
> > > I thought (according to some conference slides from sept 2017) knet
> > > was mostly
> > > related to corosync directly? Is there some visible impact on
> > > Pacemaker too?  
> > 
> > You're right -- it's more accurate to say that corosync 3 will
> > support
> > knet, and I'm not yet aware whether the corosync 3 API will require
> > any
> > changes in Pacemaker.  
> 
> Good news! The corosync developers say that knet support will be
> completely transparent to pacemaker, so pacemaker already supports
> corosync 3. :-)

Perfect!

Thanks for the confirmation and feedback :)

++