Slashdot Mirror
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.
functional naming.
Machines need arbitrary names, functional names are aliases.
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.
Use this convention for naming servers. company - airport code - role. For example, MSFT-PDX-MAIL01 (or DC01, TS01, APP01, etc)
Life is not for the lazy.
Just like my user name, I decided to go with the word "snow" in various languages. So far, I have my router chioni, server nix, desktop losse, and various other names for components. My wii is yuki, my xbox 360 is xue, my ipod touch is lumi. Beyond that I've also used "eira" and "schnee".
At my university NMSU, the CS department used alcoholic drinks (vodka, gin, etc), which were changed to vehicles (cobra, stingray) over complaints from an incoming professor. The sunrays were "bear" in various languages (oso, medved, ursa), and later they had words from the hacker's dictionary (foo, bar, baz, frob)
The naming schemes all were easily memorable, and prompted word associations, making them easy to mentally group. Ok, except the translations for bears, (and mine for snow) except for fellow crazy polyglots, and linguiphiles.
WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
I had a series of Macs before I became a diehard Linux guy. I didn't know I could name the first one, but then came Mac and Cheese, Mac Truck and Fanfare for the Common Mac (around the time of Copeland).
Why? Because I could.
What if I do the same thing, and I do get different results?
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
All my computers are named after famous computerists. For example, Welchman. Turing. Babbage. (The exception is my old laptop, named after Richard Hammond.)
My phones are also given surnames: Stubblefield, Adams, etc.
All my iPods are called Steve.
Those using pirated Tinysoft signatures(TM) are a real threat to society and should all be thrown in jail.
...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"
Ok, this drives me nuts. It's a little off topic, since it's names of conference rooms instead of server names, but the concept is the same.
Here in Colorado, we have 54 mountain peaks that are > 14,000 feet. They're referred to as "fourteeners," and they all (of course) have names.
Every company in Denver thinks they're damn clever by naming their conference rooms after the fourteeners. I don't know how many Long's Peak and Mount Evans conference rooms I've sat in, but it makes me want to hurl my chair at the window.
Ok, time for my anger management class. =p
"I either want less corruption, or more chance
to participate in it." -- Ashleigh Brilliant
...and period3 means that you're 12 years old and just started puberty?
-- Cheers!
"slashdotted". In memory of what happened to the old one.
Obligatory blog plug: http://www.caseybanner.ca/
Our usenet upstream provider used to call their main server Pants. Their admin said, "If pants is down, we're fucked."
"You never know when some crazed rodent with cold feet might be running loose in your pants."
-Calvin
(ftp://ftp.isi.edu/in-notes/rfc2100.txt)
The Naming of Hosts is a difficult matter,
It isn't just one of your holiday games;
You may think at first I'm as mad as a hatter
When I tell you, a host must have THREE DIFFERENT NAMES.
First of all, there's the name that the users use daily,
Such as venus, athena, and cisco, and ames,
Such as titan or sirius, hobbes or europa--
All of them sensible everyday names.
There are fancier names if you think they sound sweeter,
Some for the web pages, some for the flames:
Such as mercury, phoenix, orion, and charon--
But all of them sensible everyday names.
But I tell you, a host needs a name that's particular,
A name that's peculiar, and more dignified,
Else how can it keep its home page perpendicular,
And spread out its data, send pages world wide?
Of names of this kind, I can give you a quorum,
Like lothlorien, pothole, or kobyashi-maru,
Such as pearly-gates.vatican, or else diplomatic-
Names that never belong to more than one host.
But above and beyond there's still one name left over,
And that is the name that you never will guess;
The name that no human research can discover--
But THE NAMESERVER KNOWS, and will us'ually confess.
When you notice a client in rapt meditation,
The reason, I tell you, is always the same:
The code is engaged in a deep consultation
On the address, the address, the address of its name:
It's ineffable,
effable,
Effanineffable,
Deep and inscrutable,
singular
Name.
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.
By your logic, I can name all the variables in my code "x", "y", and "z" and then complain that they've hired *idiots* who can't remember that "x means the number of items in the shopping cart, duh". I could claim it's just a rite of passage into the world of complex software development...
Depends. Functional naming conventions often try to name servers according to some crazy attempt to fully qualify the server name. It'd be like naming your variables like I have seen in some VB programs (stupid Hungarian notation!)
I have worked in places where servers are given functional names, and places where servers are named in a more whimsical fashion. Functional names suck.
Even "meaningful" names lose meaning over time, due to changes in naming conventions, repurposing of hardware, or other unforeseen things. Might as well give them whimsical names which relate to one another, yet aren't dependent on the implementation details. Servers are named for human reference, else they'd be IP addresses.
Then, a new director or new group handles server allocation. The naming convention changes and you have to remember yet another arcane naming system.
Again, functional names are cumbersome and hard to remember. And you often have to type server names over and over again. It's easier to remember names like sleepy, grumpy, and dopey than to remember and constantly retype TXDALDC09DEV01, TXDALDC03DEVDB01, and CASFDC06QADB11.
If you just hate whimsical names, then at least serialize the server names. Server01, Server02, and Server03 is a better way to go than coming up with some complex system of fully qualified names.
blah blah blah
We had this exact problem. Originally they were all named Webserver1,Webserver2,Monitoring1,Monitoring2 etc etc etc. We decided it would be cool to name them all after simpsons characters. 3 Days later I get an alert to my phone at 2am to tell me Nelson is not responding to ping. WTF is Nelson? Is he important? No idea what he did, and if he needed rebooting immediately or could wait till reasonable hours.
Hence I'm a big proponent for a useful naming scheme.
In Soviet Russia the insensitive clod is YOU!
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.
...was named "Debbie"
Saves a fortune in tattoo removal.
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.
Nelson is not responding to ping
*Points* Haaa-haaa.
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.
God save us from armchair psychologists!
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. I'm not saying you should never do it (in fact, I do it a lot) but when you do it, be practical. Others may not share your projections. They may find your names confusing, misleading, or even offensive.
Where I work, there are two products that are very similar, but not quite. Somebody in engineering decided that their internal code names should be after a comic book hero and his evil twin. Those of us who don't follow comic books don't find these names very mnemonic, and often get them confused.
You're wondering why I don't tell you these two comic book characters. Can't, because they're for internal use only. If it became widely known that these products had these code names, somebody with a similar product with a similar name could sue us for trademark infringement. (The official product names combine trademarks we've already established with meaningless strings of letters and numbers.) That's another problem with these cute names: get careless and you get sued. Apple actually spends a lot of money paying off people with claims against the names they use for all their OS updates. Possibly worth it, since it contributes to their main marketing asset: their coolness factor. But not worth it for most companies.
And then there are names that just carry the cute reference bit too far. I mean, come on, whose idea was it to name a Linux distro "Yggdrasil"?
First server was nobody, followed by righty, lefty, and fleshlight.
Next up is fido.
What? I just need an echomail gateway.
paintball
This is why my mail server is 192.168.1.25 and the web server is 192.168.1.80, etc. Dev web server is 192.168.1.81. At least you can guess by the IP what it's about, based on that scheme.
Oh and their names?
Moiraine
Berelain
etc...
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.
Here's an analogy... it's like they altered your eyes to make you see in black and white; and someone says you could have a "more intense" vision. Not ever knowing color, you can only imagine that as increased brightness. And you think, no, I don't need more brightness.
But it's not just more of what you know. It's something you don't know at all.
Circumcision is child abuse.
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.
19 cross-sectional studies, 5 case-control studies, 3 cohort studies, and 1 partner study showed that the relative risk for HIV infection was 44% lower in circumcised men. Where's your evidence?
No that should be Zathrus, Zathrus, Zathrus, Zathrus, Zathrus, Zathrus, Zathrus, Zathrus, Zathrus and Zathrus.
Oops, sorry, Zathrus isn't there any more.
Not only that, but names can help you remember which server is for what purpose. My four computers at one employer were 'Sadism', 'Masochism', 'Bondage' and 'Discipline'. I got away with that for nearly half a year before my team leader noticed. Anyway, Bondage was for all my admin stuff, emails, etc. Discipline was my test rig. Masochism my build scripts, et al. Sadism actual development. I was stretching the definitions a fair bit for some of those, but it did make sense to me. And was no suprise at all to those who knew me.
Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
Chop the whole thing off and I'm sure you could get even more of a reduction.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
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.
My printer wastes my time, money, and annoys the hell out of me without ever really doing any work - so I named it after my ex-girlfriend.
Random Thoughts From A Diseased Mind (Not For Dummies)