CFEngine tip #004: How to bootstrap a CFEngine clientSep 25, 2012 · 3 minute read · Comments
My apologies for the long delay since the last tip! Today we come back with a simple tip: how to bootstrap a CFEngine client.
First, some background
CFEngine is designed to operate in a fully distributed fashion – each CFEngine client (i.e. a machine running
cf-agent) can operate fully autonomously, using only the policy files stored locally. For regular operation,
cf-agent does not require any type of network connectivity.
In real deployments, of course, maintaining each machine’s policy independently would be impractical, so CFEngine has the concept of a policy hub. In CFEngine Community, the policy hub is simply a file server, a machine from which others can download policy files. This allows having a single point of distribution, so that changes made there can be distributed to a large number of clients. In CFEngine Enterprise, the hub has a more complex role, acting also as an aggregator of data from the clients, for the purposes of reporting and analysis.
All CFEngine clients will copy to their local
/var/cfengine/inputs/ directory the contents of
/var/cfengine/masterfiles/ in the policy hub, so that is where you should make any changes that you want distributed to all the machines.
When a new client is installed, it needs to be told which machine is the policy hub to which it should connect. This is done using the following command:
# cf-agent --bootstrap --policy-server=10.0.2.15
You should, of course, replace 10.0.2.15 with the actual IP address of the hub to which you want to bootstrap. The first machine you install will be the policy hub itself, and it should bootstrap to itself. In this case, you have to use its own external IP address, and not “localhost” or 127.0.0.1.
When you issue this command on the policy hub, you will see a message like this, that indicates the host recognizes itself as a policy hub:
# cf-agent --bootstrap --policy-server=10.0.2.15 ** CFEngine BOOTSTRAP probe initiated @@@ @@@ CFEngine @ @@@ @ CFEngine Core 3.3.5 @ @@@ @ @ @@@ @ @ @ @@@ @ @ @ @ @ @ Copyright (C) CFEngine AS 2008-2012 See Licensing at http://cfengine.com/3rdpartylicenses -> This host is: precise32 -> Operating System Type is linux -> Operating System Release is 3.2.0-23-generic-pae -> Architecture = i686 -> Internal soft-class is linux -> No previous policy has been cached on this host -> Assuming the policy distribution point at: 10.0.2.15:/var/cfengine/masterfiles -> Attempting to initiate promised autonomous services... ** This host recognizes itself as a CFEngine Policy Hub, with policy distribution and knowledge base. -> The system is now converging. Full initialisation and self-analysis could take up to 30 minutes R: This host assumes the role of policy distribution host R: -> Updated local policy from policy server R: -> Started the server R: -> Started the scheduler -> Bootstrap to 10.0.2.15 completed successfully
If you issue it on a client, you will see a similar message, but indicating that it is bootstrapping from a different machine.
Regardless of what you use, after bootstrap you should see
/var/cfengine/inputs/ populated with the default set of policy files, and both
cf-serverd should be running:
# ps axw | grep [c]f- 16099 ? Ss 0:00 /var/cfengine/bin/cf-execd 16102 ? Ss 0:00 /var/cfengine/bin/cf-serverd
Once this has been done, CFEngine will start running every 5 minutes, updating its policy files from the hub, and executing them afterwards.