nanog mailing list archives
Re: AWS EC2 us-west-2 reboot
From: Jared Mauch <jared () puck nether net>
Date: Wed, 1 Oct 2014 17:18:49 -0400
On Oct 1, 2014, at 4:59 PM, Todd Underwood <toddunder () gmail com> wrote: this is kind of incident handling 101 and shouldn't be surprising to anyone.
There’s always people who feel “left out of the loop” when these things occur. I’ve found there’s no one location for centralized data after many years of doing this from the ASN.1/ILMI days to present. It requires being professional and engaging when most people just want to consume the derived data. Having found a few of these issues myself over the years, the best bugs are the ones where the advisory comes out after the fixed software is broadly available and deployed. Nothing will be perfect as people always like their legacy system that requires no work, but in reality, there is no such thing. - Jared
Current thread:
- Re: AWS EC2 us-west-2 reboot Grant Ridder (Oct 01)
- Re: AWS EC2 us-west-2 reboot Matt Palmer (Oct 01)
- Re: AWS EC2 us-west-2 reboot Bryan Fullerton (Oct 01)
- Re: AWS EC2 us-west-2 reboot Todd Underwood (Oct 01)
- Re: AWS EC2 us-west-2 reboot Jeff Fisher (Oct 01)
- Re: AWS EC2 us-west-2 reboot Jared Mauch (Oct 01)
- Re: AWS EC2 us-west-2 reboot Bryan Fullerton (Oct 01)
- Re: AWS EC2 us-west-2 reboot Matt Palmer (Oct 01)