Editing Dynamic CFEngine3 (section)

== How does it work? ==
Dynamic CFEngine extends on convergence because it provides the promises to the system in a convergent way, not all the promises are available as of the bootstrap of the host. The Webhuis example setup is structured:
* A host belongs to a domain
* A host has a role
In the example the host, domain and role bundles contain data that drive the common logic in the common bundles. When the host is bootstrapped to the CFEngine Master Hub it starts configuring itself by pulling the host and domain bundles from the hub. The host bundles file contains the role information, which convergently is being pulled from the hub in a subsequent iteration.<br/>
=== The host ===
Each host requires a file ${uqhost}.cf in this example.<br/>
In small operations this is not a problem and is the set of host files to maintain easily. Smaller operations in general will have hosts that have common names.<br/>
The downside of this approach is that a big data center will have hundreds, if not thousands of host.cf files. In a situation like that it probably is the better option to have a host naming convention, so that the host name contains the role name and for instance an instance number. Big operations in general will have a host naming convention in place.

=== The role ===
The role the host has in crucial in this concept, because the role defines the machine and the software that has to be installed and configured.<br/>
If the role is defined by a host naming convention then a regular expression is applied to fetch the role name from the host name.