[Pacemaker] Stoping clone on one node

[Vladislav Bogdanov]

Hi,

17.10.2013 12:46, Dejan Muhamedagic wrote:
> Hi,
> 
> On Thu, Oct 17, 2013 at 11:36:51AM +0200, Andreas Mock wrote:
>> Hi all,
>>
>> probably a totally stupid question:
>>
>> But how can I stop a clone resource on one
>> node? Is there a way with crm?
>>
>> The only thing which comes to my mind is
>> creating a -inf location contraint temporarily.
> 
> Yes, I think that's the only way.

It would be useful if you can extend 'move' syntax to f.e.

crm resource move <rsc> [!]<node>

Thus we can use +inf #uname eq <node> and -inf #uname eq node

Or even (just an expansion to the different use-case)
crm resource move <rsc> [soft|hard] [!]<node>

This leads to four different possible type of constraints

* 'soft' with <node> - +inf #uname eq <node>
* 'soft' with !<node> - +inf #uname ne <node>
* 'hard' with <node> - -inf #uname ne <node>
* 'hard' with !<node> - -inf #uname eq <node>

All of them are useful from my POV, I had to create each of them
manually at least once.

Originally requested one may be created with
===
crm resource move <clone> hard !<node>
===
then.

Best,
Vladislav