Posted Mar 6, 2010 18:27 UTC (Sat) by jeremiah (subscriber, #1221)
In reply to: Code names by giraffedata
Parent article: Fishy business
Maybe that's what's tickling the back of my head, that they aren't code names, but handles. And
I find handles non-informative. There just seems to be this urge out there for cuteness. I'm not
going to win any argument on the topic, but it's nice to know what peoples reasons are.
As for server name, you can see my other post, which basically says virtualization and pool based
hardware enables s to names servers after services, because we can slice and dice a lot more
easily than we used to.
I love being able upgrade a server, and make sure that the one service running on it works, and
cal it a day. Or to clone a server, upgrade the close, and drop it into place, and delete the
original, without having to point to some other ip address etc, and then run down everything
that's screwed up, because we used a different name. And the best over all is being able to build
a completely new infrastructure one server/service at a time, and dropping them into place w/o
having to change anything else, or even being able to roll back those changes by putting in/
bringing up the old server.