Mistakes we made when naming our computers
lbrandy.com
lbrandy.com
Best scheme I’ve used (if you can ignore the silliness) is Pokémon characters. There’s hundreds of them (and guaranteed to be more by the time you run out), the names are all fairly easy to spell and you’ve got pre-made iconography for connection shortcuts :)
Well defined, very large set, built-in ordering.
If a machine gets repurposed, it typically gets wiped and reidentified.
My college used Pokemon names, incidentally. Which seems to work out pretty well since they keep adding new ones and none of them have accents or special glyphs.
A lot of the names tend to sound good as computer names. It's hard to talk about machines named Bart or Spock or Frodo without getting a little embarrassed (IMO). But a computer named 'reliant' or 'intrepid' is pretty sweet.
My favorite answer: http://serverfault.com/questions/45734/the-coolest-server-na...
That's an interesting issue. When to start over with a new scheme?
When naming/labelling physically the servers two main things to be taken for consideration.
SECURITY and CONVENIENCE
SECURITY : When other persons have physical view/access to our servers they should not be able to locate the role of servers by our namings like WEB , DB , PROD , TESTING etc. By this weakness they know which machine to attack.
CONVENIENCE : Our sysadmin should be able to identify server with ease.
We name by Rack , Location and Position. Example R1CA12 i.e Machine is in Rack1 California and 12th Server. This will ease our Remote Network Operations Center engineer to know the position and coordinate with local sysadmin .
When I'm ready to reboot a machine or drop a table, I like to see 'DEV' on the hostname and not 'DB1'...
For my personal machines I decided to implement the same male/female scheme but for a theme I am using 'people somehow associated with Pink Floyd' e.g. vera, torry, storm, mallet, emily. I used to joke that if Apple ever came out with an x86 Mac I would have to call it 'layne', but they did, and I realized that PF (to my knowledge) only ever did one song about a transvestite, so that would not be a sustainable convention. :)
I opted for the most boring naming system because it made logical sense. [department abrev]-[PI abrev]-[usage abrev][Number]. This leads to names like ee-she-s03 for the third server for the Sheron group in the electrical engineering department. I can always create aliases for stuff that's commonly referenced.
Router - Courier
Home server - Minion
Slicehost server - Perpetua
Laptop - Arial
Nokia N800 - Futura
etc...
A pal's network used jazz musicians (mingus, monk).
Once upon a time some MIT machines were named after cold cereals (frosted-flakes, sugar-smacks).
A work friend, Chuck, passed away after a long illness. He was scheduled to receive a new computer and I ended up getting it instead. So naturally...
This is chuck.domain.com (Linux i686 2.6.30-gentoo-r6)
chuck login:
Authors were a good one for an on-line bookseller I worked for (not Amazon). One of my current gigs has wines: merlot, cabernet, pinot, shiraz, etc...
People tend to find it an amusing talking point.
http://transformers.wikicomplete.info/list-of-all-transforme...
When I was at MIT, the convention they used for the print servers was characters from the novel _Ringworld_: teela, louiswu, nessus, speaker, etc.
For production: db1, web1, balancer1, etc.
It was mildly uncomfortable (and very amusing) to hear people ask where to find "Rubber". :)