[ClusterLabs] Preventing Cluster from moving resources

Michael Schwartzkopff ms at sys4.de
Wed May 13 10:15:51 EDT 2015


Am Mittwoch, 13. Mai 2015, 16:10:02 schrieb Peter Albrecht:
> Hello,
> 
> I have configured a two-node RHEL 6.6 cluster with Pacemaker.
> 
> Whenever I create a new resource (actually it's resource groups I am
> creating using a script), the resource group is started on one of the
> hosts.
> 
> Two questions:
> 
> 1. Is there a way to create a resource / resource group without starting it
>    immediately? Currently, after creating all my resource groups I disable
>    them in order to prevent the cluster from starting them.

target-role="Stopped"
What do you mean by "disable"?

> 2. When disabling or deleting resources / resource groups, the other
>    resources are moved around between the nodes. Is there a way to prevent
>    this? Of course I can set location constraints (which I already do for
>    some of them). I thought there might be some parameter in the properties
>    but I did not find any.

Resource stickiness makes started tick to the node they are running on until a 
"better" node becomes available. See the configuration of rsc_default.
 
> In case you are wondering: It's a customer request to have all the resource
> groups created now but they want to decide on a case-by-case basis when
> and where to start the resource groups.

Yes. Customers requests can realy ruin a nice project sometimes.


Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20150513/7ad52d2d/attachment-0003.sig>


More information about the Users mailing list