Re: [SLUG] Configuration Management and Linux Distributions in Large Scale Farms (was "hardware dependencies?")

From: Paul M Foster (paulf@quillandmouse.com)
Date: Wed Feb 01 2006 - 15:08:30 EST


Ian C. Blenke wrote:

<snip>

>
> I stress the concept of "little switches" and "big switches" here. A
> "little switch" is a configuration option that an OpenSource package
> sees inside it's configuration file. A "big switch" is a configuration
> switch that we set for our metapackage to model the machine's
> configuration state. The metapackages on every box turn the "big
> switches" into "little switches" for the packages that they envelop. By
> developing in this way, we can add "big switches" as necessary to enable
> features for our customers, yet hide the complexity of the "little
> switches" inside each metapackage. Each metapackage begins with a
> "template" configuration, and proceeds to set the many little switches
> as appropriate for each big switch setting. This is enforced every time
> from the central configuration repository, and will override any local
> configuration changes (debugging and troubleshooting should happen at
> the edge, _not_ configuration).
>

So do you compile all your packages from source? And when you upgrade
machines you do so from your own repositories?

-- 
Paul M. Foster
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS).  Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:04:53 EDT