On 2011-01-03 10:07, Simon Jansen wrote: > Hi, > > I have got some multistate resources running. This resources should > start after the resources resIP (IPaddr2) and resFSys (Filesystem). > So to accomplish this requirement I defined the following constraints. > colocation colFSysNTP inf: msNTP:Master resFSys > colocation colIPNTP inf: msNTP:Master resIP > order orderFSysNTP inf: resFSys msNTP:promote > order orderIPNTP inf: resIP msNTP:promote > > The multistate resource is defined as follows: > primitive resNTP ocf:T-Systems:ntp \ > params master_config="/mnt/DRBD/drbd1/ntp/cnf/ntp_master.conf" > slave_config="/etc/ntp.conf" \ > op monitor interval="10" role="Master" timeout="30" \ > op monitor interval="12" timeout="31" \ > op start interval="0" timeout="120" \ > op stop interval="0" timeout="120" > ms msNTP resNTP > > The problem is that the multistate resource msNTP tries to promote > anyways even if the resources resIP and resFSys are not running on a > cluster node. So the constraints do not take effect at all. > Is there a solution to control the promotion of multistate resources > with constraints?
It would help if you shared your ntp resource agent so we can understand how it updates its master preference. See also: http://www.linux-ha.org/doc/dev-guides/_specifying_a_master_preference.html Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org 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
