[Pacemaker] Proper way to migrate multistate resource?

Rasto Levrinc rasto.levrinc at gmail.com
Thu Feb 9 10:31:28 EST 2012

On Thu, Feb 9, 2012 at 4:18 PM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> Hi,
> On Tue, Feb 07, 2012 at 01:54:44PM +0100, Lars Ellenberg wrote:
>> On Mon, Feb 06, 2012 at 04:48:26PM -0800, Chet Burgess wrote:
>> > Greetings,
>> >
>> > I'm some what new to pacemaker and have been playing around with a
>> > number of configurations in a lab. Most recently I've been testing a
>> > multistate resource using the ofc:pacemaker:Stateful example RA.
>> >
>> > While I've gotten the agent to work and notice that if I shutdown or
>> > kill a node the resources migrate I can't seem to figure out the
>> > proper way to migrate the resource between nodes when they are both
>> > up.
>> >
>> > For regular resources I've used "crm resource migrate <rsc>" without
>> > issue. However when I try this with a multistate resource it doesn't
>> > seem to work. When I run the command it just puts the slave node into
>> > a stopped state. If I try and tell it to migrate specifically to the
>> > slave node it claims to already be running their (which I suppose in a
>> > sense it is).
>> the crm shell does not support roles for the "move" or "migrate" command
>> (yet; maybe in newer versions. Dejan?).
> No, it doesn't. The crm resource commands rely on the underlying
> tools (crm_resource, et al). crm_resource is probably the right
> place to implement such a functionality, then we can easily add
> support to the shell as well. Patches accepted :)

Another place is the GUI, that already has this functionality. :)


Dipl.-Ing. Rastislav Levrinc
rasto.levrinc at gmail.com
Linux Cluster Management Console

More information about the Pacemaker mailing list