[Pacemaker] Xen live migrate if destination IP != uname -n

[Martin Gombač]

I did that, but it didn't work. At least i fought it didn't, 'cause i 
used host command "host ibm1.test.net". Host still resolves to external 
IP honoring what servers from /etc/resolv.conf have to say.

But when pinging the ibm1.test.net and after you told me to use hosts 
again, now i understand that testing shouldn't be done with host 
command. :-)

I guess Xen OCF script will also honor /etc/hosts as ping did. :-)

[root at ibm1 etc]# ping ibm1.test.net
PING ibm1.test.net (192.168.0.1) 56(84) bytes of data.

Thanks Lars and sorry for wasting your time,
M.

Lars Ellenberg wrote:
> 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
>>     
>
>