[ClusterLabs] [Linux-ha-dev] Announcing crmsh release 2.1.7

[Ken Gaillot]

On 09/23/2016 06:59 AM, Kostiantyn Ponomarenko wrote:
>>> Out of curiosity: What do you use it for, where the two_node option
> is not sufficient?
> 
> Alongside with starting the cluster with two nodes I need that
> possibility of starting the cluster with only one node.
> "two_node" option doesn't provide that.

Actually it can, if you use "two_node: 1" with "wait_for_all: 0".

The risk with that configuration is that both nodes can start without
seeing each other, and both start resources.

> 
> Thank you,
> Kostia
> 
> On Fri, Sep 2, 2016 at 11:33 AM, Kristoffer Grönlund <kgronlund at suse.com
> <mailto:kgronlund at suse.com>> wrote:
> 
>     Kostiantyn Ponomarenko <konstantin.ponomarenko at gmail.com
>     <mailto:konstantin.ponomarenko at gmail.com>> writes:
> 
>     > Hi,
>     >
>     >>> If "scripts: no-quorum-policy=ignore" is becoming depreciated
>     > Are there any plans to get rid of this option?
>     > Am I missing something?
> 
>     The above is talking about crmsh cluster configuration scripts, not core
>     Pacemaker. As far as I know, no-quorum-policy=ignore is not being
>     deprecated in Pacemaker.
> 
>     However, it is no longer the recommended configuration for two node
>     clusters.
> 
>     >
>     > PS: this option is very useful (vital) to me. And "two_node" option won't
>     > replace it.
>     >
> 
>     Out of curiosity: What do you use it for, where the two_node option is
>     not sufficient?
> 
>     Cheers,
>     Kristoffer
> 
>     --
>     // Kristoffer Grönlund
>     // kgronlund at suse.com <mailto:kgronlund at suse.com>