On Wed, Mar 09, 2011 at 07:44:58AM -0500, no-re...@cfengine.com wrote: >Forum: Cfengine Help >Subject: Re: Bundling the configuration into modules >Author: neilhwatson >Link to topic: https://cfengine.com/forum/read.php?3,20949,21008#msg-21008 > >Typically files are organizes thus: > >Cfengine policy files: >/var/cfengine/inputs >I do not have any subdirectories. I do split the files up and use bundles. >For example the file postfix.cf would handle configuring postfix. So a >typical list of files might be >promises.cf >globals.cf >site.cf >hardending.cf >postfix.cf >ntp.cf >apache.cf >monitor.cf > >All of these files are copied to each client. There is seldom a compelling >reason to limit this. > >Master files reside on the policy host. In my installs they are at >/var/cf-masterfiles/. These could be application configuration files, >binaries or SSL certs. The policy host acts as a file server and allows >clients to download files as requested by the client when the client runs its >policy.
I do something similar, but in a slightly different location: /etc/cfengine/ |-- data | |-- Packages | |-- etc | |-- root | |-- opt | |-- sbin | |-- usr | `-- var |-- inputs `-- modules Policy files all live in /etc/cfengine/inputs/, and like Mr. Watson, I tend to have one file per "thing". For example, I have specific .cf files for postfix, ntp and apache (among others). Typically, each file has one bundle, although there are some files with multiple, but still related, bundles. There are no sub directories, and all files are copied to all hosts. Distribution files live in /etc/cfengine/data/, and usually very closely mirror the destination on the target system. Thus, the source file for "/etc/hosts" will probably come from "/etc/cfengine/data/etc/hosts-${sys.uqhost}" on the policy server. The /etc/cfengine/Packages/ directory is used to keep files with unusual/complicated distribution requirements that may vary widely, depending on the target host. Use of this Packages/ directory is kept to a minimum. For convenience, cfengine module scripts are typically stored in, and distributed from /etc/cfengine/modules. The policy server is also the file distribution server, although it could easily be a different system. -- Jesse Becker NHGRI Linux support (Digicon Contractor) _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine