New host challenges: configuration files

Arusha manages a large and growing number of system configuration files:
password, group, automounter, syslog, and many more. The ark packages for
many of these files use a two phase approach:

-- First, a master configuration file or template is constructed from data
on the gold server by <configure> and <compile> methods.

-- Second, the host specific files are disseminated in <deploy> methods.

When a new host is bootstrapped into ark's world, the <configure> and
<compile> methods are not rerun automatically. Instead, the <deploy> method
tries to disseminate a host specific file based on a master configuration
file or template that predates the new host. The result is usually an
incorrect configuration on the new host.

As a workaround, I ran "ark-invasive --hosts=newhost package-config" for
each config package. There must be an easier way.

--

Joel Shprentz
National Imagery and Mapping Agency
Mailstop N-17
Washington Navy Yard, Building 213
1200 First Street, SE
Washington, DC 20303-0001

202-685-3534




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php