On Jun 21, 2010, at 5:44 AM, Damion Alexander wrote:
>
>
> Following the suggestions in this thread I hit all the major points such as
> contacts, things to watch out for etc. The wisdom of writing for the
> "competent sysadmin", helped me the most. I know (or at least assume I know)
> the s
On Fri, Jun 18, 2010 at 6:13 AM, Joe McDonagh
wrote:
> Damion, are you using puppet? If so, I recommend you do your docs inside
> the manifests and use puppetdoc to generate an up-to-date set of docs
> every night. Writing docs by hand at a volume of ~100 servers is not
> something most people wil
> Damion, are you using puppet?
Nope. Was on my long list of things I hoped to implement.
> If you're not using puppet- I still recommend trying to automate doc
> generation somehow. Possibly through a Nagios DB out to a set of wiki
> pages? It all depends on your setup.
>
I had put together
On 06/15/2010 09:39 PM, Damion Alexander wrote:
> Greetings,
>
> I've been tasked with writing documentation on all of the systems/hardware I
> supported so that the remaining admins can support them after I leave. The
> problem I face is determining what information is important enough to
> do
On Tue, Jun 15, 2010 at 09:39:35PM -0400, Damion Alexander spake thusly:
> The problem I face is determining what information is important
> enough to document outside of RTFM.
I always start with a list or outline of things I need to
document. Then I prioritize it. What things would they be abso
> From: discuss-boun...@lopsa.org [mailto:discuss-boun...@lopsa.org] On
>
> Document procedures, passwords, settings and details which a competent
I'd like to go into more detail on that:
procedures/backup-and-restore/laptops
procedures/backup-and-restore/servers
procedures/backup-and-restore/et
> From: discuss-boun...@lopsa.org [mailto:discuss-boun...@lopsa.org] On
> Behalf Of Damion Alexander
>
> If you were in this situation, on either side, what would you expect in
> that in-house documentation?
I am obsessively compulsive about documenting. Here's what I do, and what I
recommend:
On Thu, Jun 17, 2010 at 5:21 PM, Mark Dennehy wrote:
> On Wed, Jun 16, 2010 at 2:39 AM, Damion Alexander
> wrote:
> > If you were in this situation, on either side, what would you expect in
> that in-house documentation?
>
> Well...
>
> _Why_ the system is set up the way it is (how is easy, why i
i'd add:
a quick daily and weekly checklist of stuff you do (the simple act of making
these lists may point out what the most critical items to document are, for
in-house, as opposed to the extant vendor docs)
general roadmap to the systems - how they interconnect, anything out of the
ordinary har
On Wed, Jun 16, 2010 at 2:39 AM, Damion Alexander
wrote:
> If you were in this situation, on either side, what would you expect in that
> in-house documentation?
Well...
_Why_ the system is set up the way it is (how is easy, why isn't)
What the most common failure modes are
What the most seriou
10 matches
Mail list logo
