Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker

2016-07-13 Thread Jan Pokorný
On 13/07/16 12:50 +0200, emmanuel segura wrote: > using pcs resource unmanage leave the monitoring resource actived, I > usually set the monitor interval=0 :) Some time ago, I've filed a bug against pcs for it to perform these two steps in one go: https://bugzilla.redhat.com/1303969 This slowly

Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker

2016-07-13 Thread Ken Gaillot
On 07/13/2016 09:56 AM, emmanuel segura wrote: > enabled=false works with every pacemaker versions? It was introduced in Pacemaker 1.0.2, so realistically, yes :) > 2016-07-13 16:48 GMT+02:00 Ken Gaillot : >> On 07/13/2016 05:50 AM, emmanuel segura wrote: >>> using pcs

Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker

2016-07-13 Thread Ken Gaillot
On 07/13/2016 05:50 AM, emmanuel segura wrote: > using pcs resource unmanage leave the monitoring resource actived, I > usually set the monitor interval=0 :) Yep :) An easier way is to set "enabled=false" on the monitor, so you don't have to remember what your interval was later. You can set it

Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker

2016-07-13 Thread emmanuel segura
using pcs resource unmanage leave the monitoring resource actived, I usually set the monitor interval=0 :) 2016-07-11 10:43 GMT+02:00 Tomas Jelinek : > Dne 9.7.2016 v 06:39 jaspal singla napsal(a): >> >> Hello Everyone, >> >> I need little help, if anyone can give some

Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker

2016-07-11 Thread Tomas Jelinek
Dne 9.7.2016 v 06:39 jaspal singla napsal(a): Hello Everyone, I need little help, if anyone can give some pointers, it would help me a lot. In RHEL-7.x: There is concept of pacemaker and when I use the below command to freeze my resource group operation, it actually stops all of the resources