On Jan 6, 2008, at 6:49 PM, Maxim Veksler wrote:
Hi,
I have a resource which I would like to run only at 19:00, during 1
hour and then stop.
I've tried the following options:
#1
-----------------------------------------------------------------------------------------
<primitive class="ocf" provider="ML" type="plumber_exe"
id="rsc_plumber"/>
...
<rsc_location id="loc_plumber" rsc="rsc_plumber">
<rule id="plumber_loc_time_constraint" score="1000">
<date_expression id="rsc_plumber_run_timeperiod"
operation="date_spec" start="19:00">
<duration id="rsc_plumber_run_hours" hours="1"/>
</date_expression>
</rule>
</rsc_location>
----------------------------------------------------------------------------------------------
#2
-----------------------------------------------------------------------------------------
<primitive class="ocf" provider="ML" type="plumber_exe"
id="rsc_plumber">
<instance_attributes id="rsc_plumber_inst_attr">
<rule id="plumber_loc_time_constraint" score="1000">
<date_expression id="rsc_plumber_run_timeperiod"
operation="date_spec">
<date_spec id="test_failback_spec" hours="19-20"/>
</date_expression>
</rule>
<attributes/>
</instance_attributes>
</primitive>
</resources>
----------------------------------------------------------------------------------------------
#3
-----------------------------------------------------------------------------------------
<primitive class="ocf" provider="ML" type="plumber_exe"
id="rsc_plumber">
<instance_attributes id="rsc_plumber_inst_attr">
<rule id="plumber_loc_time_constraint" score="1000">
<date_expression id="rsc_plumber_run_timeperiod"
operation="date_spec" start="19:00">
<duration id="rsc_plumber_run_hours" hours="1"/>
</date_expression>
</rule>
<attributes/>
</instance_attributes>
</primitive>
----------------------------------------------------------------------------------------------
I see that heartbeat sends monitor and then tries to start the
resource, ignoring my time constraints.
Why is that ?
Try:
#4
-----------------------------------------------------------------------------------------
<primitive class="ocf" provider="ML" type="plumber_exe"
id="rsc_plumber"/>
...
<rsc_location id="loc_plumber" rsc="rsc_plumber">
<rule id="plumber_loc_time_constraint" score="1000">
<date_expression id="rsc_plumber_run_timeperiod"
operation="date_spec">
<date_spec id="test_failback_spec" hours="19-20"/>
</date_expression>
</rule>
</rsc_location>
----------------------------------------------------------------------------------------------
This should work unless resources are allowed to run everywhere in
your cluster by default (most people do this and it is the default).
If that is the case, then try:
#5
-----------------------------------------------------------------------------------------
<primitive class="ocf" provider="ML" type="plumber_exe"
id="rsc_plumber"/>
...
<rsc_location id="loc_plumber" rsc="rsc_plumber">
<rule id="plumber_loc_time_constraint-1" score="-1000">
<date_expression id="rsc_plumber_run_timeperiod-1"
operation="date_spec">
<date_spec id="test_failback_spec-1" hours="0-18"/>
</date_expression>
</rule>
<rule id="plumber_loc_time_constraint-2" score="-1000">
<date_expression id="rsc_plumber_run_timeperiod-2"
operation="date_spec">
<date_spec id="test_failback_spec-2" hours="20-23"/>
</date_expression>
</rule>
</rsc_location>
----------------------------------------------------------------------------------------------
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
