[121972] in North American Network Operators' Group
Re: Mitigating human error in the SP
daemon@ATHENA.MIT.EDU (Suresh Ramasubramanian)
Tue Feb 2 20:37:27 2010
In-Reply-To: <877585b01002021730s660bc6bcy4c2aa2e91b44efb5@mail.gmail.com>
Date: Wed, 3 Feb 2010 07:06:59 +0530
From: Suresh Ramasubramanian <ops.lists@gmail.com>
To: Michael Dillon <wavetossed@googlemail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Never said it was, and never said foolproof either. Minimizing the
chance of error is what I'm after - and ssh'ing in + hand typing
configs isn't the way to go.
Use a known good template to provision stuff - and automatically
deploy it, and the chances of human error go down quite a lot. Getting
it down to zero defect from there is another kettle of fish altogether
- a much more expensive with dev / test, staging and production
environments, documented change processes, maintenance windows etc.
On Wed, Feb 3, 2010 at 7:00 AM, Michael Dillon
<wavetossed@googlemail.com> wrote:
>
> It is easy to create a tangled mess of OSS applications that are glued together
> by lots of manual human effort creating numerous opportunities for human error.
> So while I wholeheartedly support automation of network configuration, that is
> not a magic bullet. You also need to pay attention to the whole process, the
> whole chain of information flow.
--
Suresh Ramasubramanian (ops.lists@gmail.com)
