Policy setup and structure - Revision history

Martin: /* Pool of profiles, components, bundles and templates */

2025-07-23T19:12:37Z

Pool of profiles, components, bundles and templates

← Older revision		Revision as of 19:12, 23 July 2025
Line 34:		Line 34:
	├ \|── debian12		├ \|── debian12
	│ ├ \| \|── bundles		│ ├ \| \|── bundles
			│ ├ \| \|── cfeh
⚫	│ │ \| │ ├── cfe_hub.cf -> ../../bundles/cfe_hub.cf
			\| │ ├ \| \|── bundles
		⚫	│ \| │ \| │ ├── cfe_hub.cf -> ../../../../../bundles/cfe_hub.cf
	│ ├ \| \|── templates		│ ├ \| \|── templates
	│ ├── templates		│ ├── templates

Martin: /* Pool of profile, bundles and templates */

2025-07-23T18:42:55Z

Pool of profile, bundles and templates

← Older revision		Revision as of 18:42, 23 July 2025
Line 26:		Line 26:
	== Implementation ==		== Implementation ==
	The identified elements of the standard support role profile reside in the policies tree in the subdirectory 'pool' under roadshow_polies, the policies in bundles and templates in templates, These bundles and templates are very common and are thus available to other roles through role_profile. The profile definitions reside in the profiles directory, per role. Each role contains a bundles and a template direcotry, which in this case, only contain symbolic links to file in the subsequent pool subdirectories bundles and templates.		The identified elements of the standard support role profile reside in the policies tree in the subdirectory 'pool' under roadshow_polies, the policies in bundles and templates in templates, These bundles and templates are very common and are thus available to other roles through role_profile. The profile definitions reside in the profiles directory, per role. Each role contains a bundles and a template direcotry, which in this case, only contain symbolic links to file in the subsequent pool subdirectories bundles and templates.
	=== Pool of ~~profile~~, bundles and templates ===		=== Pool of profiles, components, bundles and templates ===
	<pre>		<pre>
	└── roadshow_policies		└── roadshow_policies

Martin: /* Pool of profile, bundles and templates */

2025-07-23T18:40:29Z

Pool of profile, bundles and templates

← Older revision		Revision as of 18:40, 23 July 2025
Line 31:		Line 31:
	├── components		├── components
	│ ├── bundles		│ ├── bundles
	│ │ ├── ~~resolv_conf~~.cf		│ │ ├── cfe_hub.cf
			├ \|── debian12
			│ ├ \| \|── bundles
			│ │ \| │ ├── cfe_hub.cf -> ../../bundles/cfe_hub.cf
			│ ├ \| \|── templates
			│ ├── templates
	├── pool		├── pool
	│ ├── bundles		│ ├── bundles
Line 37:		Line 42:
	│ ├── profiles		│ ├── profiles
	│ │ └── std_sup		│ │ └── std_sup
	│ │ ├── bundles		│ │ \| ├── bundles
	│ │ │ ├── resolv_conf.cf -> ../../../bundles/resolv_conf.cf		│ │ \| │ ├── resolv_conf.cf -> ../../../bundles/resolv_conf.cf
	│ │ └── templates		│ │ \| └── templates
	│ │ ├── resolv.conf.tmpl -> ../../../templates/resolv.conf.tmpl		│ │ \| ├── resolv.conf.tmpl -> ../../../templates/resolv.conf.tmpl
	│ │ ├── templates		│ │ ├── templates
	│ │ │ ├── resolv.conf.tmpl		│ │ │ ├── resolv.conf.tmpl

Martin: /* Pool of profile, bundles and templates */

2025-07-23T18:34:03Z

Pool of profile, bundles and templates

← Older revision		Revision as of 18:34, 23 July 2025
Line 29:		Line 29:
	<pre>		<pre>
	└── roadshow_policies		└── roadshow_policies
			├── components
			│ ├── bundles
			│ │ ├── resolv_conf.cf
	├── pool		├── pool
	│ ├── bundles		│ ├── bundles

Martin: /* The policy matrix */

2025-07-09T20:44:16Z

The policy matrix

← Older revision		Revision as of 20:44, 9 July 2025
Line 7:		Line 7:
	Many roles look similar when it comes to many configuration aspects, but there always are those little differences. Those differences prevent the definition of a generic policy and provide redundancy in policies at best. Large parts of the role redundantly define the promises.		Many roles look similar when it comes to many configuration aspects, but there always are those little differences. Those differences prevent the definition of a generic policy and provide redundancy in policies at best. Large parts of the role redundantly define the promises.
	== The policy matrix ==		== The policy matrix ==
			The bundles containing the policies tend to get large and complex, because of the need to find taylor made solutions for generic problems in different environments and software components that appear in versions that at times are hampered by fundamental change.

	== The need to improve [[Dynamic_CFEngine3\|Dynamic CFEngine]] ==		== The need to improve [[Dynamic_CFEngine3\|Dynamic CFEngine]] ==
	Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />		Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />

Martin at 20:32, 9 July 2025

2025-07-09T20:32:58Z

← Older revision		Revision as of 20:32, 9 July 2025
Line 1:		Line 1:
	The current version of the Webhuis CFEngine policies are an evolution of [[Dynamic_CFEngine3\|Dynamic CFEngine]].		The current version of the Webhuis CFEngine policies are an evolution of [[Dynamic_CFEngine3\|Dynamic CFEngine]].
	= More on Roles =		= More on Roles =
			The concept of roles is at the heart of the Webhuis show case solution.
	The role defines the system in every aspect.		The role defines the system in every aspect.
	* The hardware it has available		* The hardware it has available
	* The software it autonomously installs, configures and runs		* The software it autonomously installs, configures and runs
	Many roles look similar when it comes to many configuration aspects, but there always are those little differences. Those differences prevent the definition of a generic policy and provide redundancy in policies at best. Large parts of the role redundantly define the promises.~~<br /><br />~~		Many roles look similar when it comes to many configuration aspects, but there always are those little differences. Those differences prevent the definition of a generic policy and provide redundancy in policies at best. Large parts of the role redundantly define the promises.
			== The policy matrix ==
	== The need to improve [[Dynamic_CFEngine3\|Dynamic CFEngine]] ==		== The need to improve [[Dynamic_CFEngine3\|Dynamic CFEngine]] ==
	Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />		Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />

Martin: /* Need to improve Dynamic CFEngine */

2025-07-09T20:28:09Z

Need to improve Dynamic CFEngine

← Older revision		Revision as of 20:28, 9 July 2025
Line 5:		Line 5:
	* The software it autonomously installs, configures and runs		* The software it autonomously installs, configures and runs
	Many roles look similar when it comes to many configuration aspects, but there always are those little differences. Those differences prevent the definition of a generic policy and provide redundancy in policies at best. Large parts of the role redundantly define the promises.<br /><br />		Many roles look similar when it comes to many configuration aspects, but there always are those little differences. Those differences prevent the definition of a generic policy and provide redundancy in policies at best. Large parts of the role redundantly define the promises.<br /><br />
	== ~~Need~~ to improve [[Dynamic_CFEngine3\|Dynamic CFEngine]] ==		== The need to improve [[Dynamic_CFEngine3\|Dynamic CFEngine]] ==
	Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />		Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />
	Convergence is one of the fundamental principles of CFEngine the dynamic setup relies on too heavily, because policies are being used to identify dependent and subsequent policies. Policies are being derived from the concept of the 'role' a system has, components are defined in the role and convergently become available to the system. A role has one or more components that may depend on the platform or the flavor of the system. Convergence towards the Desired State is meant for configuring a system, not for the composition of the policy set.<br />		Convergence is one of the fundamental principles of CFEngine the dynamic setup relies on too heavily, because policies are being used to identify dependent and subsequent policies. Policies are being derived from the concept of the 'role' a system has, components are defined in the role and convergently become available to the system. A role has one or more components that may depend on the platform or the flavor of the system. Convergence towards the Desired State is meant for configuring a system, not for the composition of the policy set.<br />

Martin at 20:27, 9 July 2025

2025-07-09T20:27:53Z

← Older revision		Revision as of 20:27, 9 July 2025
Line 4:		Line 4:
	* The hardware it has available		* The hardware it has available
	* The software it autonomously installs, configures and runs		* The software it autonomously installs, configures and runs
	Many roles look similar when it comes to many configuration aspects, but there always are those little differences. Those differences prevent the definition of a generic policy and provide redundancy in policies at best. Large parts of the role redundantly define the promises.<br /><br />~~== Need to improve [[Dynamic_CFEngine3\|Dynamic CFEngine]] ==~~		Many roles look similar when it comes to many configuration aspects, but there always are those little differences. Those differences prevent the definition of a generic policy and provide redundancy in policies at best. Large parts of the role redundantly define the promises.<br /><br />
			== Need to improve [[Dynamic_CFEngine3\|Dynamic CFEngine]] ==
	Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />		Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />
	Convergence is one of the fundamental principles of CFEngine the dynamic setup relies on too heavily, because policies are being used to identify dependent and subsequent policies. Policies are being derived from the concept of the 'role' a system has, components are defined in the role and convergently become available to the system. A role has one or more components that may depend on the platform or the flavor of the system. Convergence towards the Desired State is meant for configuring a system, not for the composition of the policy set.<br />		Convergence is one of the fundamental principles of CFEngine the dynamic setup relies on too heavily, because policies are being used to identify dependent and subsequent policies. Policies are being derived from the concept of the 'role' a system has, components are defined in the role and convergently become available to the system. A role has one or more components that may depend on the platform or the flavor of the system. Convergence towards the Desired State is meant for configuring a system, not for the composition of the policy set.<br />

Martin at 20:27, 9 July 2025

2025-07-09T20:27:16Z

@@ Line 1: / Line 1: @@
 The current version of the Webhuis CFEngine policies are an evolution of [[Dynamic_CFEngine3|Dynamic CFEngine]].
 Dynamic CFEngine to a large extent meets the requirement of having only the relevant policies in place, which reduces both the amount of code and the complexity of the code. The way Dynamic CFEngine is structured, however, has some draw backs.<br />
 Convergence is one of the fundamental principles of CFEngine the dynamic setup relies on too heavily, because policies are being used to identify dependent and subsequent policies. Policies are being derived from the concept of the 'role' a system has, components are defined in the role and convergently become available to the system. A role has one or more components that may depend on the platform or the flavor of the system. Convergence towards the Desired State is meant for configuring a system, not for the composition of the policy set.<br />
@@ Line 6: / Line 10: @@
 * Developers tend to reject this setup, they want to have the policy set available right from the beginning
 * The role concept as it was, was far from perfect, because of the redundancy in the different roles.
 Enter the Role Profile concept.

Martin: /* Pool of profile, bundles and templates */

2025-07-09T09:11:59Z

Pool of profile, bundles and templates

← Older revision		Revision as of 09:11, 9 July 2025
Line 26:		Line 26:
	├── pool		├── pool
	│ ├── bundles		│ ├── bundles
			│ │ ├── resolv_conf.cf
	│ ├── profiles		│ ├── profiles
	│ │ └── std_sup		│ │ └── std_sup
	│ │ ├── bundles		│ │ ├── bundles
			│ │ │ ├── resolv_conf.cf -> ../../../bundles/resolv_conf.cf
	│ │ └── templates		│ │ └── templates
	│ ├── templates		│ │ ├── resolv.conf.tmpl -> ../../../templates/resolv.conf.tmpl
			│ │ ├── templates
			│ │ │ ├── resolv.conf.tmpl
	├── roles		├── roles
	│ ├── cfeh		│ ├── cfeh

← Older revision		Revision as of 19:12, 23 July 2025
Line 34:		Line 34:
	├ \|── debian12		├ \|── debian12
	│ ├ \| \|── bundles		│ ├ \| \|── bundles
			│ ├ \| \|── cfeh
⚫	│ │ \| │ ├── cfe_hub.cf -> ../../bundles/cfe_hub.cf
			\| │ ├ \| \|── bundles
		⚫	│ \| │ \| │ ├── cfe_hub.cf -> ../../../../../bundles/cfe_hub.cf
	│ ├ \| \|── templates		│ ├ \| \|── templates
	│ ├── templates		│ ├── templates