Why Do We Name Servers the Way We Do?
jfruhlinger writes "If you use a Unix machine, it probably has a funny name. And if you work in an environment where there are multiple Unix machines, they probably have funny names that are variations on a theme. No, you're not the only one! This article explores the phenomenon, showing that even the CIA uses a whimsical server naming scheme." What are some of your best (worst?) naming schemes?
h t t p colon slash slash slash dot dot org
Old Reader's Digest Joke:
Seven terminals named Doc, Happy, Sleepy, Grumpy, . . ., and a printer named "Handsome Prints". :-)
I like that in this edition of Duplicate Stories on /. Monthly, the link in the story actually links back to a previous story that's asking the same thing! Thanks for saving us the few seconds of searching for the older stories on this one /.!
A goofy naming scheme is a bad idea when you're running over 100 servers in a dynamic environment. When your servers are named after wines, cheeses, and trees, who can say what Oak does, or Chablis, or Feta, or Jujuba, or Sassafras, ad nauseum.
-r0
Naming our machines in odd and amusing ways it our way of secretly rebelling against over management.
I name each of my servers the name of another computer's mac address on the network. This way, as part of my retirement package I'll have the joyous knowledge that the person who takes over my position is going insane.
I used to run a fairly lucrative business at a time when a certain industry was much more profitable... JennaJameson would always go down while RonJeremy would always be up.
Coincidence? I think not.
Over time, systems get refactored for uses that they were not originally intended, so that box named web1 is now an ftp server and nobody bothered to rename it. The same happens when you try to name them by physical location. r1a2r10n5 got moved from Room 1, Aisle 2, Rack 10, Number 5 to another room entirely.
The easiest time I had dealig with servers was when they were named after japanese monsters. We had Godzilla, Mothra, etc. We all know that Godzilla was the PostresSQL server. If a box's purpose changed, we didn't have to worry about renaming it and people would eventually learn its new purpose.
Whimsical names work.
-- Will program for bandwidth
...but I later decided on naming them after AIs.
Roker?
Jolsen?
Sharpton?
Yankovic?
Gore?
Oh, wait...
There's a pretty sizeable collection of funny/clever server names on Stack Overflow here:
http://stackoverflow.com/questions/262657/the-coolest-server-names
Sturgeon was an optimist.
So when something goes wrong, people sound like morons: "Why is motherboard down!?" "I can't connect to RAM!"
Obligatory blog plug: http://www.caseybanner.ca/
Great idea! Let's name the others "Mickey", "Minnie", and "Pluto"
It gives your customers something to chuckle over during traceroutes too. Why settle for letting them discover they traversed v11s0p1.dal01.blahblahblah.net, when you could let them know that they went through thebeast.bbb.net or ratbastard.wehateourjobs.com?
See, I don't get it. WHY would you name your servers this? If you smack your head or have a hard night drinking, would you know FOR SURE that ServerX is the file server or the database server? Would you code like that? At least make the names useful.
Personally, I like MrDomainController, MrNameServer, MrFileServer, etc. Have a backup? Meet MsDomainController. Need yet another backup? JrDomainController? Need another one? No you don't. See, easy, unambiguous, useful.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
...and logically, Cats 5 and 6 would be very similar in appearance, but Cat 6 would end up able to chase mice ten times faster.
We had a Simpsons fan where I used to work, When our engineering groups got our first workstations, he named his 'homer' and suggested that we follow suit. We named ours 'ulysses'.
Have gnu, will travel.
For smaller setups with less than ten machines, I like to use colours.
Red - Production Server
Orange - Staging Server
Yellow - Test Server
Green - Dev Server
Blue/Purple/etc etc for other things like the database server etc.
This way, when I'm setting up PuTTY or another shell, I can set the foreground text colour for each machine to match the server name, which stops most of those embarrassing mistakes when you run a command on production that you meant to run on test, and so on.
And a server that serves more than 1 role? or if you're trying to fit names into a small namespace? Or you ever have to pass the name over the phone to a colleague?
Starbucks, Harbuckle of Breath.
...was named "Debbie"
Thus, if you tether your Motorola cell phone to your laptop, you end up with Ockham's RAZR.
We reused an old piece of junk machine as a print server in our development lab, which was connected to the enterprise network. We gave it an appropriately descriptive name, Dungpile. Little did we know that in its prior life Dungpile had been configured as a DHCP server. (We didn't look at it too closely... our bad.) One day we hear a frazzled guy from the IT department going door to door crying, "I'm looking for Dungpile! Does anyone know where Dungpile is?" It turns out the enterprise DHCP server had a hiccup, and in the subsequent negotiation for which backup would take over, Dungpile won out. Our little print server started handing out 10.10.*.* IP addresses (it was evidently set up for a private network) to the enterprise workstations. That worked very poorly. The IT folks could tell the bogus addresses were coming from a machine called Dungpile, but didn't know where it was located. (I don't know why they didn't just boot Dungpile and force their primary server to resume duties. The weren't a great team.) Anyway, it made my day hearing someone wandering the hall yelling about finding dungpile.
I was a network admin for a small law office, and I named all their computers after medical conditions. I named the senior partner's computer 'IMPOTENCE' hoping that someday he'd come to me and tell me that he was having problems with impotence and that he couldn't get it to come up.
Actually, the "piles of medical evidince" have lead the American Association of Pediatrics and the American Medical Association not to recommend routine circumcision of newborns. Given the number and density of nerve endings in the foreskin, comparison to clitoridectomy is not so far-fetched. Just because the one is socially accepted where you live doesn't make it any less barbaric than the other.
Although it may be healthy to project personalities onto things (I'm a little skeptical, though I could maybe be persuaded by somebody who doesn't go around making sweeping psychiatric diagnoses of people he's never met) that hardly justifies encoding those projections into names.
There's a simple, practical reason for using names: IP addresses can be hard to remember.
There's a simple, practical reason for using "themed" name spaces: coming up with dozens/hundreds of names can be hard.
After all, I am strangely colored.