I suspect no-one is using this, since time-based expressions can be included in the regular sets of constraint rules.
For example:
<rsc_location id="cli-prefer-rsc_pcmk-1" rsc="rsc_pcmk-1">
<lifetime>
<rule id="cli-lifetime-rule-rsc_pcmk-1" score="INFINITY">
<date_expression id="cli-prefer-lifetime-end-rsc_pcmk-1" operation="lt"
end="2010-04-11 13:22:39Z" />
</rule>
</lifetime>
<rule id="cli-prefer-rule-rsc_pcmk-1" score="INFINITY">
<expression id="cli-prefer-expr-rsc_pcmk-1" attribute="#uname"
operation="eq" value="pcmk-2" type="string" />
</rule>
</rsc_location>
Is normally written as:
<rsc_location id="cli-prefer-rsc_pcmk-1" rsc="rsc_pcmk-1">
<rule id="cli-prefer-rule-rsc_pcmk-1" score="INFINITY" boolean-op="and" >
<expression id="cli-prefer-expr-rsc_pcmk-1" attribute="#uname"
operation="eq" value="pcmk-2" type="string" />
<date_expression id="cli-prefer-lifetime-end-rsc_pcmk-1" operation="lt"
end="2010-04-11 13:22:39Z" />
</rule>
</rsc_location>
For this reason I'm considering removing support for the <lifetime> tag in 1.1.
Please speak up if you're using this functionality and want to keep it.
-- Andrew
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
