Mailing List Archive: Announcing crmsh release 2.1.7

Announcing crmsh release 2.1.7

Sep 1, 2016, 12:01 AM

Post #1 of 4 (2658 views)

Hello everyone!

Today I are proud to announce the release of `crmsh` version 2.1.7!
The major new thing in this release is a backports of the events-based
alerts support from the 2.3 branch.

Big thanks to Hideo Yamauchi for his patience and testing of the
alerts backport.

This time, the list of changes is small enough that I can add it right
here:

- high: parse: Backport of event-driven alerts parser (#150)
- high: hb_report: Don't collect logs from journalctl if -M is set (bsc#990025)
- high: hb_report: Skip lines without timestamps in log correctly (bsc#989810)
- high: constants: Add maintenance to set of known attributes (bsc#981659)
- high: utils: Avoid deadlock if DC changes during idle wait (bsc#978480)
- medium: scripts: no-quorum-policy=ignore is deprecated (bsc#981056)
- low: cibconfig: Don't mix up CLI name with XML tag

You can also get the list of changes from the changelog:

* https://github.com/ClusterLabs/crmsh/blob/2.1.7/ChangeLog

Right now, I don't have a set of pre-built rpm packages for Linux
distributions ready, but I am going to make this available soon. This
is in particular for centOS 6.x which still relies on Python 2.6
support which makes running the later releases there more
difficult. These packages will most likely appear as a subrepository
here (more details coming soon):

* http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/

Archives of the tagged release:

* https://github.com/ClusterLabs/crmsh/archive/2.1.7.tar.gz
* https://github.com/ClusterLabs/crmsh/archive/2.1.7.zip

Thank you,

Kristoffer

--
// Kristoffer GrÃ¶nlund
// kgronlund@suse.com
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Re: Announcing crmsh release 2.1.7 [ In reply to ]

darrent at akurit

Sep 1, 2016, 12:07 AM

Post #2 of 4 (2649 views)

Permalink

Team

good work on the new version, appreciated.

Just a quick question:

If "scripts: no-quorum-policy=ignore" is becoming depreciated, how are we
to manage two node (e.g. test) clusters that require this work around since
quorum state on a single node is an odd state.

Regards

Darren Thompson

Professional Services Engineer / Consultant

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent@akurit.com.au <steve@akurit.com.au>
Web: www.akurit.com.au

On 1 September 2016 at 17:01, Kristoffer GrÃ¶nlund <kgronlund@suse.com>
wrote:

> Hello everyone!
>
> Today I are proud to announce the release of `crmsh` version 2.1.7!
> The major new thing in this release is a backports of the events-based
> alerts support from the 2.3 branch.
>
> Big thanks to Hideo Yamauchi for his patience and testing of the
> alerts backport.
>
> This time, the list of changes is small enough that I can add it right
> here:
>
> - high: parse: Backport of event-driven alerts parser (#150)
> - high: hb_report: Don't collect logs from journalctl if -M is set
> (bsc#990025)
> - high: hb_report: Skip lines without timestamps in log correctly
> (bsc#989810)
> - high: constants: Add maintenance to set of known attributes (bsc#981659)
> - high: utils: Avoid deadlock if DC changes during idle wait (bsc#978480)
> - medium: scripts: no-quorum-policy=ignore is deprecated (bsc#981056)
> - low: cibconfig: Don't mix up CLI name with XML tag
>
> You can also get the list of changes from the changelog:
>
> * https://github.com/ClusterLabs/crmsh/blob/2.1.7/ChangeLog
>
> Right now, I don't have a set of pre-built rpm packages for Linux
> distributions ready, but I am going to make this available soon. This
> is in particular for centOS 6.x which still relies on Python 2.6
> support which makes running the later releases there more
> difficult. These packages will most likely appear as a subrepository
> here (more details coming soon):
>
> * http://download.opensuse.org/repositories/network:/ha-
> clustering:/Stable/
>
> Archives of the tagged release:
>
> * https://github.com/ClusterLabs/crmsh/archive/2.1.7.tar.gz
> * https://github.com/ClusterLabs/crmsh/archive/2.1.7.zip
>
>
> Thank you,
>
> Kristoffer
>
> --
> // Kristoffer GrÃ¶nlund
> // kgronlund@suse.com
> _______________________________________________________
> Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/
>

Re: Announcing crmsh release 2.1.7 [ In reply to ]

kgronlund at suse

Sep 1, 2016, 1:27 AM

Post #3 of 4 (2647 views)

Permalink

Darren Thompson <darrent@akurit.com.au> writes:

> Just a quick question:
>
> If "scripts: no-quorum-policy=ignore" is becoming depreciated, how are we
> to manage two node (e.g. test) clusters that require this work around since
> quorum state on a single node is an odd state.
>

Hi Darren,

There are better mechanisms in corosync and Pacemaker for handling two
node clusters now while still maintaining quorum.

In corosync 2, we have the two_node: 1 setting for votequorum, which
ensures that a two node cluster doesn't suffer split brain (fencing is
required for this to work properly).

There is an explanation for how this works here:

http://people.redhat.com/ccaulfie/docs/Votequorum_Intro.pdf

Somewhat related, there used to be the start-delay meta parameter which
could be set for example for sbd stonith resources, to make a
double-fencing scenario less likely. This has now been replaced by the
pcmk_delay_max parameter. For an example of how to use this, see this
pull request for sbd:

https://github.com/ClusterLabs/sbd/pull/15/commits/ca2fba836eab169f0c8cacf7f3757c0485bcfef8

Cheers,
Kristoffer

--
// Kristoffer GrÃ¶nlund
// kgronlund@suse.com
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Re: Announcing crmsh release 2.1.7 [ In reply to ]

darrent at akurit

Sep 1, 2016, 1:31 AM

Post #4 of 4 (2650 views)

Permalink

Thank you.

Comprehensively answered.

On 1 Sep 2016 6:27 PM, "Kristoffer GrÃ¶nlund" <kgronlund@suse.com> wrote:

> Darren Thompson <darrent@akurit.com.au> writes:
>
> > Just a quick question:
> >
> > If "scripts: no-quorum-policy=ignore" is becoming depreciated, how are we
> > to manage two node (e.g. test) clusters that require this work around
> since
> > quorum state on a single node is an odd state.
> >
>
> Hi Darren,
>
> There are better mechanisms in corosync and Pacemaker for handling two
> node clusters now while still maintaining quorum.
>
> In corosync 2, we have the two_node: 1 setting for votequorum, which
> ensures that a two node cluster doesn't suffer split brain (fencing is
> required for this to work properly).
>
> There is an explanation for how this works here:
>
> http://people.redhat.com/ccaulfie/docs/Votequorum_Intro.pdf
>
> Somewhat related, there used to be the start-delay meta parameter which
> could be set for example for sbd stonith resources, to make a
> double-fencing scenario less likely. This has now been replaced by the
> pcmk_delay_max parameter. For an example of how to use this, see this
> pull request for sbd:
>
> https://github.com/ClusterLabs/sbd/pull/15/commits/
> ca2fba836eab169f0c8cacf7f3757c0485bcfef8
>
> Cheers,
> Kristoffer
>
> --
> // Kristoffer GrÃ¶nlund
> // kgronlund@suse.com
>

Mailing List Archive

Mailing List Archive

Attached Files: