News for hackers. Stuff that matters.
Re:A Google Cloud support engineer solves a tough DNS case by dralley on Tuesday May 19, 2020 @12:48PM (#23237024)
That's awfully convenient, and I can't deny having done this, but it's also a great way to never understand what went wrong.
Re:A Google Cloud support engineer solves a tough DNS case by cmeacham98 on Tuesday May 19, 2020 @12:51PM (#23237054)
Re-provisioning a failed server to solve the problem and taking a deep dive to find the root cause are not mutually exclusive. Essentially all VM software will allow you to snapshot/backup/clone the VM for later analysis, while also fixing your production environment _now_.
Re:A Google Cloud support engineer solves a tough DNS case by londons_explore on Tuesday May 19, 2020 @02:44PM (#23238510)
When you have a service which is acting weirdly, ideally I'd like to snapshot the VM, then do whatever I need to do to repair the service urgently.

That might involve making a new VM from scratch, but it also might twiddling some settings, or other emergency changes.

Afterwards, I want to be able to restore the VM state, probably in a firewalled off environment, so I can debug exactly what was wrong.

Sometimes I'd like to do it to a set of VM's - for example, if there is some DNS wierdness, I might want to snapshot an application server and a DNS server.

So far, no cloud provider seems to offer functionality to make that easy, which is a bit disappointing.