On 2/2/10 12:08 AM, "Tim Cutts" <t...@sanger.ac.uk> wrote: > Finally, if there really are some machines which need to be configured > by hand (something I resist strongly) we have a minimal_cfe class > where the vast majority of our cfengine policy is skipped, and only > the bare essentials are checked.
We do the same. Anyone (with root of course) can touch /etc/classes/minimal_host (/etc/classes is a convention we adopted locally for interfacing with cfe, after seeing it done elsewhere), which in turn defines the "minimal_host" class, and skips all but the essentials. As to docs, we found wikis work great when maintaining communal documentation. An initial education in the form of a broad overview presentation, with a pointer to the wiki (and urges to fix what's broken while reading) seems to work. The biggest problem was stale docs as you mentioned... As docs grew and new ones were created, we quickly needed more powerful search. We currently use a Google appliance for that, and it does pretty well. That said, having a good way to "retire" docs from the start (maybe move them to a history web) would be good for anyone going the way of wiki. Some times communal systems like wiki make this worse -- you need good communication, or people will forever block on bad docs waiting for someone else to update them. :) _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
