this post was submitted on 17 Jun 2024
102 points (98.1% liked)
Asklemmy
43939 readers
458 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Similar to your #2, but less serious, I once wrote a script to power down virtual machines for a data center move. It was a nice piece of work too, grouping them in batches, sending shutdown commands to the guest OS, falling back to forcing a power off through the hypervisor after a configurable timeout...
I don't recall the specifics of the problem or the virtual infrastructure I was working with, but in short I didn't have sanity checks on what was being shut down. Ended up force shutting off the hypervisor/virtual infrastructure management system.
Added an extra few hours the move with that.
I can absolutely see that happening in vsphere.