[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Configuration File Organization
From: |
Jamie Wilkinson |
Subject: |
Re: Configuration File Organization |
Date: |
Fri, 30 Jul 2004 11:58:37 +1000 |
User-agent: |
Mutt/1.5.6+20040523i |
This one time, at band camp, Russell Adams wrote:
>On the topic of splitting up large configs into smaller pieces, can
>anyone share any method of organization that has worked well for them?
I split them up by service.
The master file, cfagent.conf, only does imports.
The first import is a groups definition for network-wide groups that get
used throughout the configuration.
Each service configuration then imported, roughly in order of importance and
dependence.
The services look like:
# SERVICE.cf
groups:
SERVICE_server = ( list of machines that run this service )
SERVICE_subset = ( some condition )
control:
SERVICE_configuration_option = ( something )
SERVICE_subset::
SERVICE_subset_configuration = ( somethign specific to this subset )
then editfiles, links, copy, etc as needed, using the above groups and
control variables to configure the service
finally processes and shellcommands responsible for testing that the service
is running and configured to run at boot, restarting if necessary.
--
jaq@spacepants.org http://spacepants.org/jaq.gpg