I miss when we were allowed to name our servers however we wanted. We had groups like comic superheroes being database servers, fantasy book characters were email/messaging servers, sci Fi characters were file servers, and dead musicians were application servers. We’d get problems like Hendrix can’t connect to Hulk and everyone immediately knew the issue we were trying to solve.
Now everything is named with a two letter code for type, two more letters for location, two letters for the group it serves, and a two digit number. It looks random, but I can tell what server it is by glancing. However, I just miss the days when I could say “I don’t know what’s happening, but Dresden is fucked.”
now that i think about it, this would be handy for remote support techs walking a user on-site on what to do…
“you see the 3rd switch from the top that has the cisco logo? i’ll need you to power cycle it”
2 hours later
“oh i found it”
vs.
“you see the girl with the blue hair? unplug the box her hair’s connected to”
My company stopped using “named” servers and instances a while ago, to be “more professional”.
But of course, you fuck up “restart Maria DB n1h5” way more often than “restart Thor”. 😅
I miss when we were allowed to name our servers however we wanted. We had groups like comic superheroes being database servers, fantasy book characters were email/messaging servers, sci Fi characters were file servers, and dead musicians were application servers. We’d get problems like Hendrix can’t connect to Hulk and everyone immediately knew the issue we were trying to solve.
Now everything is named with a two letter code for type, two more letters for location, two letters for the group it serves, and a two digit number. It looks random, but I can tell what server it is by glancing. However, I just miss the days when I could say “I don’t know what’s happening, but Dresden is fucked.”
You forgot:
‘oh I found it’ unplugs a machine in a completely different room