Configure the networks from which nodes are allowed to connect to the Rudder policy servers to get their updated configuration policy.
You can add as many networks as you want, the expected format is: NetworkIP/mask, for example "42.42.0.0/16".
If enabled, prompt users to enter a message explaining the reason for each configuration change they make.
These messages will be stored in each Event log and as the commit message for the underlying git repository in
If enabled, all changes to configuration (Directives, Rules, Groups and Parameters) will be submitted for validation via a Change Request.
A new Change Request will enter the "Pending validation" status, then can be moved to "Pending deployment" (approved but not yet deployed) or "Deployed" (approved and deployed) statuses.
Only users with the "validator" or "deployer" roles are authorized to perform these steps (see /opt/rudder/etc/rudder-users.xml).
If disabled, all changes to configuration will be immediately deployed.
Every time Rudder modifies a file (by file editing or copying from a remote source), a copy of the overwritten file is kept under /var/rudder/modified-files/.
Also, the full output from each agent run is stored in a file under /var/rudder/cfengine-community/outputs/.
These files are automatically removed to save on disk space. You can configure the retention time (Time To Live) they are kept for here.
All nodes in Rudder send reports via syslog to this Rudder root server. These logs are stored in an SQL database in order to determine compliance information displayed in this web interface. However, it can be useful to also store this information in a plain text log file, for example for statistics or debugging purposes. The option below enables this.
API response used to send data that may not be sent back to the API for modification. Parameter to enable a directive is 'enabled', but API response was using 'isEnabled' for that parameter, so you had to handle this case before sending data. We have harmonized response and parameters (in this ). But if you had script based on malformed response, you can enable this option.
Clear cached data. This will trigger a full policy update, and regenerate all promise files.
Groups in Rudder can be static (fixed list of nodes) or dynamic (the list of nodes is built from a search query).
To take into account new nodes and changes to their inventory, dynamic groups must be reloaded regularly.
Currently, Rudder will automatically do this reload every 5 minutes (see /opt/rudder/etc/rudder-web.properties).
Techniques in Rudder are read from the filesystem (in /var/rudder/configuration-repository/techniques).
To take into account new Techniques and changes, the Technique library must be updated regularly.
Currently, Rudder will automatically do this update every 5 minutes (see /opt/rudder/etc/rudder-web.properties).