Page History

...

• The policy consists of any number of  rules.
  The rules are evaluated in order of their numeric key; fractional numbers are supported to simplify insertion.
  Only the first matching rule is applied.
• Each rule must express what changes to systemHealth should be made.
  The changes are expressed as a list of systemHealth section name plus the desired activation state (true or false).
  systemHealth sections not named are not modified and there for therefor default to True or on (so check the default section for what would otherwise be disabled).
• Each rule may include any number of filter expressions, which determine whether the rule should be applied to a particular node.
  All given filter expressions must match simultaneously for the rule to be considered a match.
  A filter expression defines a node property or configuration setting to be compared against an explicit list of acceptable values, or a regular expression.
  Node properties are given as node.<propname>, and for configuration settings you'd use conf.<configsetting>.
• All configuration settings are available, using the prefix conf. and the same names as seen in conf/Config.nmis.
• The available node properties are: the static ones from the node configuration, plus the more dynamic ones from the system section in the  node's "node info" file (var/<nodename>-node.json).
• A Model Policy document may also include an extra section named _display, which controls in what order the default policy's entries should be shown in the Configuration GUI.
  See the default policy for an example.

...