We don't want 800 servers updating within the same ten minutes.
The primary reason for using both is to engage cfengine's logging system.
In this article, I focus on a make-it-so-and-keep-it-so approach.
Let's consider a small hosting company configuration, with three administrators and two data centers (Figure 1).
This also could be written as: This brings us to an important topic in building a cfengine implementation: groups.
There is a groups command that can be used to assign hosts to groups based on various criteria.
Each administrator can use a Subversion/CVS sandbox to hold repositories for each data center.