On Thu, Aug 13, 2009 at 10:39 PM, Dan Urist<dur...@ucar.edu> wrote: > This example from page 36 of "Configuration Explained 1.0" fails > validation with several errors: > >> <rsc_defaults> >> <meta_attributes id=”core-hours” score=”2”> >> <rule id="core-hour-rule"> >> <date_expression id="9to5_Mon2Fri" operation="date_spec"> >> <date_spec hours="9-17" days="1-5"/> >> </date_expression> >> </rule> >> <nvpair id="core-stickiness" name="resource-stickiness" value="INFINITY"/> >> </meta_attributes> >> <meta_attributes id=”after-hours” score=”1” > >> <nvpair id="after-stickiness" name="resource-stickiness" value="0"/> >> </instance_attributes> >> </primitive> > > > This passes, though I haven't tested yet to see if it actually works.
Thanks, I've updated the docs locally. > I'm not sure if the "core-hours" meta-attributes also needs to contain a > score? It does. In this context, the higher score ensures that it is processed first. Without it, the resource-stickiness would always be 0. > >> <rsc_defaults> >> <meta_attributes id="core-hours"> >> <rule id="core-hour-rule" score="2"> >> <date_expression id="work-hours" operation="date_spec"> >> <date_spec id="work-hours-spec" weekdays="1-5" hours="9-17" /> >> </date_expression> >> </rule> >> <nvpair id="core-stickiness" name="resource-stickiness" >> value="INFINITY" /> >> </meta_attributes> >> <meta_attributes id="after-hours" score="1"> >> <nvpair id="after-stickiness" name="resource-stickiness" value="0" /> >> </meta_attributes> >> </rsc_defaults> > > -- > Dan Urist > dur...@ucar.edu > 303-497-2459 (office) > 303-961-2675 (cell) > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
