Dynamic Cfengine2 - Revision history

Martin at 16:56, 8 July 2025

2025-07-08T16:56:06Z

← Older revision		Revision as of 16:56, 8 July 2025
Line 18:		Line 18:
	== Step by step ==		== Step by step ==
	In the first iteration almost everything fails, the bundles g, update and the bundlesequence in @(webhuis_common) will execute but will not fulfill all the promises.		In the first iteration almost everything fails, the bundles g, update and the bundlesequence in @(webhuis_common) will execute but will not fulfill all the promises.
			<hr>
			Return to: [[CFEngine]]

2014-05-17T22:37:56Z

The structure

← Older revision		Revision as of 22:37, 17 May 2014
Line 8:		Line 8:
	== The structure ==		== The structure ==
	The bundlesequence in promises.cf is as follows:		The bundlesequence in promises.cf is as follows:
	"role"		"role"<br/>
	"g"		"g"<br/>
	"update"		"update"<br/>
	"@(webhuis_common)"		"@(webhuis_common)"<br/>
	"${g.class_domain}"		"${g.class_domain}"<br/>
	"${g.class_host}"		"${g.class_host}"<br/>
	"${role.role}"		"${role.role}"<br/>

	== Step by step ==		== Step by step ==
	In the first iteration almost everything fails, the bundles g, update and the bundlesequence in @(webhuis_common) will execute but will not fulfill all the promises.		In the first iteration almost everything fails, the bundles g, update and the bundlesequence in @(webhuis_common) will execute but will not fulfill all the promises.

2014-05-17T22:37:15Z

@@ 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 [http://webhuis.nl/GPL-license GPL-2] as its contribution to the community.
 = How does it work? =
@@ Line 5: / Line 6: @@
 * 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.

2014-05-17T22:14:46Z

← Older revision		Revision as of 22:14, 17 May 2014
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 [http://webhuis.nl/GPL-license 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. The Webhuis example setup is structured:		Dynamic CFEngine extends on convergence because it provides the promises to the system. The Webhuis example setup is structured:

2014-05-17T22:10:41Z

How does it work?

← Older revision		Revision as of 22:10, 17 May 2014
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.

2014-05-17T20:28:25Z

← Older revision		Revision as of 20:28, 17 May 2014
Line 1:		Line 1:
	Dynamic CFEngine is the Webhuis way of providing a taylor made set of promises to each and every node.		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

2014-05-17T19:30:44Z

New page: Dynamic CFEngine is the Webhuis way of providing a taylor made set of promises to each and every node.

New page

Dynamic CFEngine is the Webhuis way of providing a taylor made set of promises to each and every node.