Installation of the Rudder Agent

Static files

At installation of the Rudder Agent, files and directories are created in following places:

Scripts to integrate Rudder Agent in the system (init, cron).
Initialization promises for the Rudder Agent. These promises are used until the Node has been validated in Rudder. They are kept available at this place afterwards.
The FusionInventory Inventory tool and its Perl dependencies.
Wrapper script to launch the inventory.
Binaries for CFEngine Community.
This is the working directory for CFEngine Community.

Generated files

At the end of installation, the CFEngine Community working directory is populated for first use, and unique identifiers for the Node are generated.

CFEngine Community binaries are copied there.
Contains the actual working CFEngine Community promises. Initial promises are copied here at installation. After validation of the Node, Applied Policies, which are the CFEngine promises generated by Rudder for this particular Node, will be stored here.
An unique SSL key generated for the Node at installation time.
An unique identifier for the Node is generated into this file.


After all of these files are in place, the CFEngine Community daemons are launched:

This CFEngine Community daemon is launching the CFEngine Community Agent cf-agent every 5 minutes.
This CFEngine Community daemon is listening on the network on Rudder Root and Relay servers, serving policies and files to Rudder Nodes.


At this point, you should configure the Rudder Agent to actually enable the contact with the server. Type in the IP address of the Rudder Root Server in the following file:

echo *root_server_IP_address* > /var/rudder/cfengine-community/policy_server.dat