[Pacemaker] Resource stickiness during working hours

[Johan Verrept]

Hi Dejan,

On Wed, 2009-10-07 at 17:06 +0200, Dejan Muhamedagic wrote:
> Yes, that's no problem, it's just that I'm not sure about how to
> design it since the language is, well, rather flat.

Might it be possible to at least let crm recognise the configuration as
valid or ignore it even if it isn't possible to configure it?

An error each time crm is started is rather annoying, especially one
that doesn't make much sense... (not to me, anyway). It's also rather
hard to filter out when scripting.

Thanks for considering it,

	Johan

# crm configure
original: <meta_attributes id="core-hours" score="2">
        <rule id="core-hour-rule" score="1">
                <date_expression id="nine-to-five-Mon-to-Fri"
operation="date_spec">
                        <date_spec hours="9-17"
id="nine-to-five-Mon-to-Fri-spec" weekdays="1-5"/>
                </date_expression>
        </rule>
        <nvpair id="core-stickiness" name="resource-stickiness"
value="2"/>
</meta_attributes>

processed: <meta_attributes id="core-hours">
        <nvpair id="core-hours-" name="" value="None"/>
        <nvpair id="core-stickiness" name="resource-stickiness"
value="2"/>
</meta_attributes>

original: <meta_attributes id="after-hours" score="1">
        <nvpair id="after-stickiness" name="resource-stickiness"
value="0"/>
</meta_attributes>

processed: <meta_attributes id="after-hours">
        <nvpair id="core-stickiness" name="resource-stickiness"
value="0"/>
</meta_attributes>

crm(live)configure#