[Pacemaker] resource migration check list question

[Jean-Francois Malouin]

Hi,

Pardon the naive question but it's not clear to me. Can the following
be used if I want resXen1 to live migrate when losing network connectivity?
(op start/stop/monitor etc omitted):

primitive resXen1 ocf:heartbeat:Xen \
    params xmfile="/xen/xen1.cfg" \
    meta allow-migrate="true"
primitive resPing ocf:pacemaker:ping \
    host_list="xxx.xxx.xxx.xxx" 
clone cloPing resPing \
    meta globally-unique="false"
location locPing resXen1 \
    rule $id="locPing-rule" -inf: not_defined pingd or pingd lte 0

http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/index.html
section 9.3.4.1. Migration Checklist says:

"The resource must not, directly or indirectly, depend on any primitive or group resources."

Is resXen1 dependent on the resPing in the snippet above through the
location statement so no go for live migration?

thanks,
jf