Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker
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 associated under the resource group. # pcs cluster standby # pcs cluster unstandby Result: This actually stops all of the resource group in that node (ctm_service is one of the resource group, which gets stop including database as well, it goes to MOUNT mode) Hello Jaspal, that's what it's supposed to do. Putting a node into standby means the node cannot host any resources. However; through clusvcadm command on RHEL-6.x, it doesn't stop the ctm_service there and my database is in RW mode. # clusvcadm -Z ctm_service # clusvcadm -U ctm_service So my concern here is - Freezing/unfreezing should not affect the status of the group. Is there any way around to achieve the same in RHEL-7.x as well, that was done with clusvcadm on RHEL 6? Maybe you are looking for # pcs resource unmanage and # pcs resource manage Regards, Tomas Thanks Jaspal ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker
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 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 >> associated under the resource group. >> >> # pcs cluster standby >> >> # pcs cluster unstandby >> >> Result: This actually stops all of the resource group in that node >> (ctm_service is one of the resource group, which gets stop including >> database as well, it goes to MOUNT mode) > > > Hello Jaspal, > > that's what it's supposed to do. Putting a node into standby means the node > cannot host any resources. > >> >> However; through clusvcadm command on RHEL-6.x, it doesn't stop the >> ctm_service there and my database is in RW mode. >> >> # clusvcadm -Z ctm_service >> >> # clusvcadm -U ctm_service >> >> So my concern here is - Freezing/unfreezing should not affect the status >> of the group. Is there any way around to achieve the same in RHEL-7.x as >> well, that was done with clusvcadm on RHEL 6? > > > Maybe you are looking for > # pcs resource unmanage > and > # pcs resource manage > > Regards, > Tomas > >> >> Thanks >> >> Jaspal >> >> >> >> >> ___ >> Users mailing list: Users@clusterlabs.org >> http://clusterlabs.org/mailman/listinfo/users >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> > > ___ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org -- .~. /V\ // \\ /( )\ ^`~'^ ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker
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 in the op_defaults section to disable all operations at once (assuming no operation has "enabled=true" explicitly set). Similarly, you can set is_managed=false in rsc_defaults to unmanage all resources (that don't have "is_managed=true" explicitly set). > 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 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 >>> associated under the resource group. >>> >>> # pcs cluster standby >>> >>> # pcs cluster unstandby >>> >>> Result: This actually stops all of the resource group in that node >>> (ctm_service is one of the resource group, which gets stop including >>> database as well, it goes to MOUNT mode) >> >> >> Hello Jaspal, >> >> that's what it's supposed to do. Putting a node into standby means the node >> cannot host any resources. >> >>> >>> However; through clusvcadm command on RHEL-6.x, it doesn't stop the >>> ctm_service there and my database is in RW mode. >>> >>> # clusvcadm -Z ctm_service >>> >>> # clusvcadm -U ctm_service >>> >>> So my concern here is - Freezing/unfreezing should not affect the status >>> of the group. Is there any way around to achieve the same in RHEL-7.x as >>> well, that was done with clusvcadm on RHEL 6? >> >> >> Maybe you are looking for >> # pcs resource unmanage >> and >> # pcs resource manage >> >> Regards, >> Tomas >> >>> >>> Thanks >>> >>> Jaspal ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker
enabled=false works with every pacemaker versions? 2016-07-13 16:48 GMT+02:00 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 in the > op_defaults section to disable all operations at once (assuming no > operation has "enabled=true" explicitly set). > > Similarly, you can set is_managed=false in rsc_defaults to unmanage all > resources (that don't have "is_managed=true" explicitly set). > >> 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 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 associated under the resource group. # pcs cluster standby # pcs cluster unstandby Result: This actually stops all of the resource group in that node (ctm_service is one of the resource group, which gets stop including database as well, it goes to MOUNT mode) >>> >>> >>> Hello Jaspal, >>> >>> that's what it's supposed to do. Putting a node into standby means the node >>> cannot host any resources. >>> However; through clusvcadm command on RHEL-6.x, it doesn't stop the ctm_service there and my database is in RW mode. # clusvcadm -Z ctm_service # clusvcadm -U ctm_service So my concern here is - Freezing/unfreezing should not affect the status of the group. Is there any way around to achieve the same in RHEL-7.x as well, that was done with clusvcadm on RHEL 6? >>> >>> >>> Maybe you are looking for >>> # pcs resource unmanage >>> and >>> # pcs resource manage >>> >>> Regards, >>> Tomas >>> Thanks Jaspal > > ___ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org -- .~. /V\ // \\ /( )\ ^`~'^ ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker
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 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 in the >> op_defaults section to disable all operations at once (assuming no >> operation has "enabled=true" explicitly set). >> >> Similarly, you can set is_managed=false in rsc_defaults to unmanage all >> resources (that don't have "is_managed=true" explicitly set). >> >>> 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 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 > associated under the resource group. > > # pcs cluster standby > > # pcs cluster unstandby > > Result: This actually stops all of the resource group in that node > (ctm_service is one of the resource group, which gets stop including > database as well, it goes to MOUNT mode) Hello Jaspal, that's what it's supposed to do. Putting a node into standby means the node cannot host any resources. > > However; through clusvcadm command on RHEL-6.x, it doesn't stop the > ctm_service there and my database is in RW mode. > > # clusvcadm -Z ctm_service > > # clusvcadm -U ctm_service > > So my concern here is - Freezing/unfreezing should not affect the status > of the group. Is there any way around to achieve the same in RHEL-7.x as > well, that was done with clusvcadm on RHEL 6? Maybe you are looking for # pcs resource unmanage and # pcs resource manage Regards, Tomas > > Thanks > > Jaspal >> >> ___ >> Users mailing list: Users@clusterlabs.org >> http://clusterlabs.org/mailman/listinfo/users >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org > > > ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker
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 becomes a recurring topic. -- Jan (Poki) pgpvGdACfO7fy.pgp Description: PGP signature ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
