[Pacemaker] Xen live migrate if destination IP != uname -n
Lars Ellenberg
lars.ellenberg at linbit.com
Wed Dec 23 05:25:12 EST 2009
On Wed, Dec 23, 2009 at 09:58:25AM +0100, Martin Gombač wrote:
> Hi guys,
>
> i cannot believe no one else has this problem with Xen OCF live
> migration script.
> I guess i have to solve it myself. Is there a meta parameter for Xen
> resources something like: migrate-target?
> I'll try that, if not i'll just statically set target_node in Xen OCF.
>
> Regards,
> M.
>
> Martin Gombač wrote:
>> Hi,
>>
>> i've used meta attribute allow-migrate for Xen OCF script. Now cluster
>> attempts to live migrate a node, but fails because node name (uname -n)
>> resolves to public IP, while xen is configured to listen only on local
>> network for migration.
Why not simply add an /etc/hosts entry?
>> Is there a way to tell OCF Xen script, to use IP from local network
>> instead of node name?
>>
>> --
>> Xen_Migrate_To() {
>> target_node="$OCF_RESKEY_CRM_meta_migrate_target"
>> --
>>
>> Thank you.
>> Regards,
>> M.
>>
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
More information about the Pacemaker
mailing list