[ClusterLabs] Q: "migrating a clone" with crm shell

[Kristoffer Grönlund]

Ulrich Windl <Ulrich.Windl at rz.uni-regensburg.de> writes:

> Hi!
>
> I have a globally-unique="false" interleave="true"  clone running on two nodes. For a software upgrade I want to disable the rsource on the node to be updated. There fore I tried "crm resource migrate my_clone PT10M", which did not work:
>
> --
> Resource 'my_clone' not moved: active in 2 locations.
> You can prevent 'my_clone' from running on a specific location with: --ban --host <name>
> Error performing operation: Invalid argument
> --
>
> I couldn't quite find out what the right command should be, especially as the "help migrate" says:
> --
> crm(live)resource# help migrate
>
> Migrate a resource to a different node. If node is left out, the
> resource is migrated by creating a constraint which prevents it from
> running on the current node. Additionally, you may specify a
> lifetime for the constraint---once it expires, the location
> constraint will no longer be active.
>
> Usage:
> ...............
>         migrate <rsc> [<node>] [<lifetime>] [force]
> ...............
> --
>
> I tried " crm resource migrate --ban --host active_node_name my_clone PT10M", but that triggers a syntax error:
> --
> usage: migrate <rsc> [<node>] [<lifetime>] [force]
> --
>
> How should I "temporarily shutdown" the resource of the clone on one node?

The crm resource migrate command is not compatible with migrating
clones.

How about creating a temporary constraint to force the clone off the
particular node?

crm configure location ban my_clone -inf: PT10M

Then once finished, remove the constraint.

>
> Regards,
> Ulrich
>
>
>
> _______________________________________________
> Users mailing list: Users at 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
>

-- 
// Kristoffer Grönlund
// kgronlund at suse.com