Rudder - Management
Policy server settings

Configure policy server(s).

Client-server communication

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".


Delete Allowed network
[error]


Security



[messages]

Configure change messages

If enabled, prompt users to enter a message explaining the reason for each configuration change they make.





[messages]
Configure Change Requests (validation workflow)

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.





[messages]
Clear deployment caches

Clear cached data. This will trigger a full redeployment, and regenerate all promise files.


[error]
Manage dynamic groups

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).


[error]
Manage Technique library

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).


[messages]