On Thu, Oct 21, 2010 at 7:43 PM, Jean-Francois Malouin <[email protected]> wrote: > 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?
yes > (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 no, only colocation constraints count as "dependent" > through the > location statement so no go for live migration? > > thanks, > jf > > _______________________________________________ > Pacemaker mailing list: [email protected] > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > _______________________________________________ Pacemaker mailing list: [email protected] http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
