Change Details

Currently, `rule` elements beneath a location constraint can have a `role` attribute. However, the role does not affect rule evaluation in any way, but rather changes the constraint's role filter. The location constraint itself has a `role` attribute for that purpose, but it is ignored (and disallowed by the schema) if the constraint has a rule. If a rule in a location constraint has subrules, their role attributes are ignored, which is unexpected behavior. Deprecate `role` in rules, change the schema to allow `role` in location constraints with rules, and honor a location constraint's explicit role over a rule's.

Currently, `rule` elements beneath a location constraint can have a `role` attribute. However, the role does not affect rule evaluation in any way, but rather changes the constraint's role filter. The location constraint itself has a `role` attribute for that purpose, but it is ignored (and disallowed by the schema) if the constraint has a rule. If a rule in a location constraint has subrules, their role attributes are ignored, which is unexpected behavior. `score` behaves simlarly. `score-attribute` can currently only be used on `rule`, not `rsc_location`, but non-rule location constraints could and should support it as well. Implement `score-attribute` for location constraints without rules, deprecate all three attributes for `rule`, change the schema to allow them on `rsc_location` even if it has a rule, and have any attribute set on `rsc_location` take precedence over the same attribute set on its rule.

Currently, `rule` elements beneath a location constraint can have a `role` attribute. However, the role does not affect rule evaluation in any way, but rather changes the constraint's role filter. The location constraint itself has a `role` attribute for that purpose, but it is ignored (and disallowed by the schema) if the constraint has a rule. If a rule in a location constraint has subrules, their role attributes are ignored, which is unexpected behavior. Deprecate `role` in rules`score` behaves simlarly. `score-attribute` can currently only be used on `rule`, not `rsc_location`, but non-rule location constraints could and should support it as well. Implement `score-attribute` for location constraints without rules, deprecate all three attributes for `rule`, change the schema to allow `role` in them on `rsc_location constraints with` even if it has a rules, and honor a location constraint's explicit rolave any attribute set on `rsc_location` take precedence over a rule'sthe same attribute set on its rule.