On 12 February 2010 16:18, Daniel Pittman <[email protected]> wrote:
> Alternately, I would suggest using something like puppet which is designed to
> do system management like this in an automated fashion; it is a completely
> different approach, but one that will probably solve your underlying problem
> without needing to change your security model so much.

I'd strongly second that if you are willing to get a more general
approach to managing systems.

There are 4 of us managing about a hundred hosts (and counting) using
puppet and actually installing stuff instead of copying images around
means that you can share a whole lot of the common configuration stuff
(e.g. sudoers files, for instance, or tweaking small part of the
installation based on the specific environment (e.g. test vs.
production)) and avoid copying huge amounts of files unnecessarily.
Not to mention doing changes on a live system without having to
completely re-image it (if you don't want to, we sometimes move aside
an existing virtual node (rename an LV) and rebuild it from scratch so
we have something to roll back to).

--Amos
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to