[Pacemaker] Move DRBD master

Vadym Chepkov vchepkov at gmail.com
Tue Oct 19 10:34:11 EDT 2010


On Oct 19, 2010, at 9:18 AM, Dan Frincu wrote:

> 
> 
> Vadym Chepkov wrote:
>> 
>> 
>> On Oct 19, 2010, at 3:42 AM, Pavlos Parissis wrote:
>> 
>>> 
>>> 
>>> On 19 October 2010 01:18, Vadym Chepkov <vchepkov at gmail.com> wrote:
>>> Hi,
>>> 
>>> What is the crm shell command to move drbd master to a different node?
>>> 
>>> 
>>> take a look at this 
>>> http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg06300.html
>>> _______________________________________________
>> 
>> Wow, not the friendliest command I would say. Maybe "move" command can be enhanced to provide something similar?
>> 
>> Thanks,
>> Vadym
> The crm resource move/migrate <rsc> provides/creates the location constraint within the crm shell. 
> 
> In the example I gave:
> 
> crm resource migrate ms_drbd_storage
> 
> WARNING: Creating rsc_location constraint 'cli-standby-ms_drbd_storage' with a score of -INFINITY for resource ms_drbd_storage on cluster1.
>       This will prevent ms_drbd_storage from running on cluster1 until the constraint is removed using the 'crm_resource -U' command or manually with cibadmin
>       This will be the case even if cluster1 is the last node in the cluster
>       This message can be disabled with -Q
> 
> The warning message appears in the console after executing the command in the crm shell, running a crm configure show reveals the following:
> 
> location cli-standby-ms_drbd_storage ms_drbd_storage \
>         rule $id="cli-standby-rule-ms_drbd_storage" -inf: #uname eq cluster1
> 
> The example in the UEL above has been done manually to (probably) provide an advisory placement constraint, the one set by crm resource move <rsc> is a mandatory placement constraint.
> 


It misses $role=Master and doesn't work because of that.

Vadym

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101019/0b025f10/attachment-0002.html>


More information about the Pacemaker mailing list