nanog mailing list archives
Re: Mitigating human error in the SP
From: Suresh Ramasubramanian <ops.lists () gmail com>
Date: Tue, 2 Feb 2010 07:58:53 +0530
On Tue, Feb 2, 2010 at 7:51 AM, Chadwick Sorrell <mirotrem () gmail com> wrote:
This outage, of a high profile customer, triggered upper management to react by calling a meeting just days after. Put bluntly, we've been told "Human errors are unacceptable, and they will be completely eliminated. One is too many."
Automated config deployment / provisioning. And sanity checking before deployment. -- Suresh Ramasubramanian (ops.lists () gmail com)
Current thread:
- Mitigating human error in the SP Chadwick Sorrell (Feb 01)
- Re: Mitigating human error in the SP Suresh Ramasubramanian (Feb 01)
- Re: Mitigating human error in the SP Dobbins, Roland (Feb 01)
- RE: Mitigating human error in the SP Stefan Fouant (Feb 01)
- Re: Mitigating human error in the SP Ross Vandegrift (Feb 03)
- Re: Mitigating human error in the SP Christopher Morrow (Feb 03)
- Re: Mitigating human error in the SP Michael Dillon (Feb 03)
- Re: Mitigating human error in the SP David Hiers (Feb 03)
- Re: Mitigating human error in the SP Michael Dillon (Feb 02)
- Re: Mitigating human error in the SP Suresh Ramasubramanian (Feb 02)
- Re: Mitigating human error in the SP Steven Bellovin (Feb 02)
- Re: Mitigating human error in the SP Brian Raaen (Feb 03)
- Re: Mitigating human error in the SP Suresh Ramasubramanian (Feb 01)