On 2007-06-11T17:38:13, Stefano Harding <[EMAIL PROTECTED]> wrote:
> Upon some close investigation it looks like crm_resource only issues a
> stop on the node that is running the Xen guest and then a start on the
> destination host. I can hack the Xen OCF resource script to make live
> migration work but this does not look like the right way to do it. How
> can I get crm_resource to actually make a migrate_to call?
crm_resource doesn't directly make that call.
The CRM sees the request to move the resource from node A to B, looks at
the allow migrate flag and then decides whether it can migrate or needs
to stop/start. So, if you've got allow_migrate set correctly, and the
resource is healthy and both nodes are as well, it should perform a
migration.
If you look at the relevant logs for that transition, you'll find a line
which says "pengine ... input written to /var/lib/heartbeat/pengine/".
That's the policy engine input which was used as the basis for that
transition, and includes all relevant state.
Post it here as an attachment, or maybe the logs are already helpful
enough for you to figure out what's going on?
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
