The archive feature of Rudder allows to:
Exchange configuration between multiple Rudder instances, in particular when having distinct environments;
Keep an history of major changes.
Export the current configuration of Rudder before you begin to make any change you have to test: if anything goes wrong, you can return to this archived state.
Assuming you have multiple Rudder instances, each on dedicated for the development, qualification and production environment. You can prepare the changes on the development instance, export an archive, deploy this archive on the qualification environment, then on the production environment.
Versions of the Rudder servers
If you want to export and import configurations between environments, the version of the source and target Rudder server must be exactly the same. If the versions don’t match (even if only the minor versions are different), there is a risk that the import will break the configuration on the target Rudder server.
In the Administration → Archives section of the Rudder Server web interface, you can export and import the configuration of Rudder Groups, Directives and Rules. You can either archive the complete configuration, or only the subset dedicated to Groups, Directives or Rules.
When archiving configuration, a 'git tag' is created into
This tag is then referenced in the Rudder web interface, and available for download
as a zip file. Please note that each change in the Rudder web interface is also
committed in the repository.
Currently, Archiving also add all unstaged files in the commit in /var/rudder/configuration-repository. So it can change the Techniques used by Rudder (Rudder uses the latest commit in git as a reference). You should away ensure that there are no unstaged files before doing any Archive to avoid any side effect. In the future, Rudder will prevent any Archive in Techniques or Generic Methods are not commited.
The content of this repository can be imported into any Rudder server (with the same version).
To archive Rudder Rules, Groups, Directives, or make a global archive, you need to go to the Administration → Archives section of the Rudder Server web interface.
To perform a global archive, the steps are:
Click on Archive everything - it will update the drop down list Choose an archive with the latest data
In the drop down list Choose an archive, select the newly created archive (archives are sorted by date), for example 2015-01-08 16:39
Click on Download as zip to download an archive that will contains all elements.
On the target server, importing the configuration will "merge" them with the existing configuration: every groups, rules, directives or techniques with the same identifier will be replaced by the import, and all others will remain untouched.
To import the archive on the target Rudder server, you can follow the following steps:
Uncompress the zip archive in
If necessary, correct all files permissions:
chown -R root:rudder directives groups parameters ruleCategories rules techniquesand
chown -R ncf-api-venv:rudder ncf/50_techniques techniques/ncf_techniques
Add all files in the git repository:
git add . && git commit -am "Importing configuration"
Finally, in the Web interface, go to the Administration → Archives section, and select Latest Git commit in the drop down list in the Global archive section, and click on Restore everything to restore the configuration.
You can also perform the synchronisation from on environment to another by using git, through a unique git repository referenced on both environment.
For instance, using one unique git repository you can follow this workflow:
You can use the procedures of Archiving and Restoring configuration to deploy preconfigured instance. You would prepare first in your labs the configuration for Groups, Directives and Rules, create an Archive, and import the Archive on the new Rudder server installation
Every action happening in the Rudder web interface are logged in the PostgreSQL database. The last 1000 event log entries are displayed in the Administration → View Event Logs section of Rudder web application. Each log item is described by its 'ID', 'Date', 'Actor', and 'Event' 'Type', 'Category' and 'Description'. For the most complex events, like changes in nodes, groups, techniques, directives, deployments, more details can be displayed by clicking on the event log line.
- Event Categories
The Administration → Policy Server Management section sum-up information about Rudder policy server and its parameters.
Here you can configure the networks from which nodes are allowed to connect to Rudder policy server to get their updated rules.
You can add as many networks as you want, the expected format is:
networkip/mask, for example
Clear cached data, like node configuration. That will trigger a full redeployment, with regeneration of all policies files.
To restart the Rudder Agent, use following command on a node:
rudder agent restart
This command can take more than one minute to restart the agent daemons. This is not a bug, but an internal protection system of the agent.
You can restart all components of the Rudder Root Server at once:
service rudder-server restart
Here is the list of the components of the root server with a brief description of their role, and the command to restart them:
- Policy server
Distribute the configuration to the nodes.
service rudder-agent restart
- Web server application
Execute the web interface and the server that handles the new inventories.
service rudder-jetty restart
- Web server front-end
Handle the connection to the Web interface, the received inventories and the sharing of the UUID Rudder Root Server.
service apache2 restart
- LDAP server
Store the inventories and the Node configurations.
service rudder-slapd restart
- SQL server
Store the received reports from the nodes.
service postgresql* restart
← Reporting problem Archives →