Comment on Twitter has an internal root CA problemparentComments−ilyt3yWe have 7 racks and 3 people working in ops and built Puppet setup "right". It's not hard. And their setup was probably right too.Just that nobody plans for "bus hit our entire ops team"−jojobas3yMore commonly you don't plan for it, you make sure the entire ops team are never on the same bus, same plane, preferably not even in the same city.−hef198983yAll fine and good. Until the new owner just fires everyone over night anyway. At which point, I guess, it is not the previous ops team's problem anymore.−VoidWhisperer3yUnfortunately even those precautions wouldn't save you from the 'holy shit basicially the entire ops team got fired out of nowhere' scenario..−rsynnott3y_Nothing_ can save a company from sufficiently incompetent future management, ultimately.
Comments
We have 7 racks and 3 people working in ops and built Puppet setup "right". It's not hard. And their setup was probably right too.
Just that nobody plans for "bus hit our entire ops team"
More commonly you don't plan for it, you make sure the entire ops team are never on the same bus, same plane, preferably not even in the same city.
All fine and good. Until the new owner just fires everyone over night anyway. At which point, I guess, it is not the previous ops team's problem anymore.
Unfortunately even those precautions wouldn't save you from the 'holy shit basicially the entire ops team got fired out of nowhere' scenario..
_Nothing_ can save a company from sufficiently incompetent future management, ultimately.