Re: [ClusterLabs] New status reporting for starting/stopping resources in 1.1.19-8.el7

2019-09-03 Thread Ken Gaillot
On Sat, 2019-08-31 at 03:39 +, Chris Walker wrote:
> Hello,
> The 1.1.19-8 EL7 version of Pacemaker contains a commit ‘Feature:
> crmd: default record-pending to TRUE’ that is not in the ClusterLabs
> Github repo.  This commit changes the reporting for resources that
> are in the process of starting and stopping for (at least) crm_mon
> and crm_resource
> crm_mon
> Resources that are in the process of
> starting
> Old reporting:
> Stopped
> New reporting:
> Starting
> Resources that are in the process of
> stopping
> Old reporting:
> Started
> New reporting:
> Stopping
>  
> crm_resource -r  -W
> Resources that are in the process of
> starting
> Old reporting:
> resource  is NOT running
> New reporting:
> resource  is running on: 
> Resources that are in the process of
> stopping
> Old reporting:
> resource  is running on: 
> New reporting:
> resource  is NOT running
>  
> The change to crm_mon is helpful and accurately reflects the current
> state of the resource, but the new reporting from crm_resource seems
> somewhat misleading.  Was this the intended reporting?  Regardless, 

Interesting, I never looked at how crm_resource showed pending actions.
That should definitely be improved.

The record-pending option itself has been around forever, and so has
this behavior when it is set to true. The only difference is that it
now defaults to true.

> the fact that this commit is not in the upstream ClusterLab repo
> makes me wonder whether this will be the default status reporting
> going forward (I will try the 2.0 branch soon).

It indeed was changed in the 2.0.0 release. RHEL 7 backported the
change from there.

>  
> Thanks,
> Chris
-- 
Ken Gaillot 

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] New status reporting for starting/stopping resources in 1.1.19-8.el7

2019-08-30 Thread Andrei Borzenkov
31.08.2019 6:39, Chris Walker пишет:
> Hello,
> The 1.1.19-8 EL7 version of Pacemaker contains a commit ‘Feature: crmd: 
> default record-pending to TRUE’ that is not in the ClusterLabs Github repo. 

commit b48ceeb041cee65a9b93b9b76235e475fa1a128f
Author: Ken Gaillot 
Date:   Mon Oct 16 09:45:18 2017 -0500

Feature: crmd: default record-pending to TRUE

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

[ClusterLabs] New status reporting for starting/stopping resources in 1.1.19-8.el7

2019-08-30 Thread Chris Walker
Hello,
The 1.1.19-8 EL7 version of Pacemaker contains a commit ‘Feature: crmd: default 
record-pending to TRUE’ that is not in the ClusterLabs Github repo.  This 
commit changes the reporting for resources that are in the process of starting 
and stopping for (at least) crm_mon and crm_resource

crm_mon
Resources that are in the process of starting
Old reporting: Stopped
New reporting: Starting
Resources that are in the process of stopping
Old reporting: Started
New reporting: Stopping

crm_resource -r  -W
Resources that are in the process of starting
Old reporting: resource 
 is NOT running
New reporting: resource 
 is running on: 
Resources that are in the process of stopping
Old reporting: resource 
 is running on: 
New reporting: resource 
 is NOT running

The change to crm_mon is helpful and accurately reflects the current state of 
the resource, but the new reporting from crm_resource seems somewhat 
misleading.  Was this the intended reporting?  Regardless, the fact that this 
commit is not in the upstream ClusterLab repo makes me wonder whether this will 
be the default status reporting going forward (I will try the 2.0 branch soon).

Thanks,
Chris
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/