<div dir="ltr">I tried the location -INFINITY trick and it seems to work quite well. Thanks for the advice.<div><br></div><div>It seems to me that if I am not failing over automatically, then there is no good reason to run a stonith resource. Is this correct or is it still needed for some reason?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 24, 2016 at 11:02 AM, Ken Gaillot <span dir="ltr"><<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 05/24/2016 04:13 AM, Klaus Wenninger wrote:<br>
> On 05/24/2016 09:50 AM, Jehan-Guillaume de Rorthais wrote:<br>
>> Le Tue, 24 May 2016 01:53:22 -0400,<br>
>> Digimer <<a href="mailto:lists@alteeve.ca">lists@alteeve.ca</a>> a écrit :<br>
>><br>
>>> On 23/05/16 03:03 PM, Stephano-Shachter, Dylan wrote:<br>
>>>> Hello,<br>
>>>><br>
>>>> I am using pacemaker 1.1.14 with pcs 0.9.149. I have successfully<br>
>>>> configured pacemaker for highly available nfs with drbd. Pacemaker<br>
>>>> allows me to easily failover without interrupting nfs connections. I,<br>
>>>> however, am only interested in failing over manually (currently I use<br>
>>>> "pcs resource move <drbd_rsc> <target_node> --master"). I would like for<br>
>>>> the cluster to do nothing when a node fails unexpectedly.<br>
>>>><br>
>>>> Right now the solution I am going with is to run<br>
>>>> "pcs property set is-managed-default=no"<br>
>>>> until I need to failover, at which point I set is-managed-default=yes,<br>
>>>> then failover, then set it back to no.<br>
>>>><br>
>>>> While this method works for me, it can be unpredictable if people run<br>
>>>> move commands at the wrong time.<br>
>>>><br>
>>>> Is there a way to disable automatic failover permanently while still<br>
>>>> allowing manual failover (with "pcs resource move" or with something else)?<br>
>> Try to set up your cluster without the "interval" parameter on the monitor<br>
>> action? The resource will be probed during the target-action (start/promote I<br>
>> suppose), but then it should not get monitored anymore.<br>
><br>
> Ignoring the general cluster yes/no question a simple solution would<br>
> be to bind the master-role to a node-attribute that you move around<br>
> manually.<br>
<br>
</div></div>This is the right track. There are a number of ways you could do it, but<br>
the basic idea is to use constraints to only allow the resources to run<br>
on one node. When you want to fail over, flip the constraints.<br>
<br>
I'd colocate everything with one (most basic) resource, so then all you<br>
need is one constraint for that resource to flip. It could be as simple<br>
as a -INFINITY location constraint on the node you don't want to run on.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
</div></div></blockquote></div><br></div>