Vijay Gill had some real interesting insights into this in a presentation he gave back at NANOG 44:
http://www.nanog.org/meetings/nanog44/presentations/Monday/Gill_programatic_N44.pdf His Blog article on "Infrastructure is Software" further expounds upon the benefits of such an approach - http://vijaygill.wordpress.com/2009/07/22/infrastructure-is-software/ That stuff is light years ahead of anything anybody is doing today (well, apart from maybe Vijay himself ;) ... but IMO it's where we need to start heading. Stefan Fouant, CISSP, JNCIE-M/T www.shortestpathfirst.net GPG Key ID: 0xB5E3803D > -----Original Message----- > From: Suresh Ramasubramanian [mailto:ops.li...@gmail.com] > Sent: Monday, February 01, 2010 9:29 PM > To: Chadwick Sorrell > Cc: nanog@nanog.org > Subject: Re: Mitigating human error in the SP > > On Tue, Feb 2, 2010 at 7:51 AM, Chadwick Sorrell <mirot...@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.li...@gmail.com)
