Mitigating human error in the SP

Suresh Ramasubramanian ops.lists at gmail.com
Tue Feb 2 19:36:59 CST 2010


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 at 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 at gmail.com)




More information about the NANOG mailing list