Difference between revisions of "Dynamic Cfengine2"
(→How does it work?) |
|||
| Line 1: | Line 1: | ||
Dynamic CFEngine is the Webhuis way of providing a taylor made set of promises to each and every node. Webhuis offers Dynamic CFEngine under GPL-2 as its contribution to the community. |
Dynamic CFEngine is the Webhuis way of providing a taylor made set of promises to each and every node. Webhuis offers Dynamic CFEngine under GPL-2 as its contribution to the community. |
||
= How does it work? = |
= How does it work? = |
||
| − | Dynamic CFEngine extends on convergence because it provides the promises to the system |
+ | Dynamic CFEngine extends on convergence because it provides the promises to the system. 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. |
||
Revision as of 22:10, 17 May 2014
Dynamic CFEngine is the Webhuis way of providing a taylor made set of promises to each and every node. Webhuis offers Dynamic CFEngine under GPL-2 as its contribution to the community.
How does it work?
Dynamic CFEngine extends on convergence because it provides the promises to the system. 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.
