161–170 of 187 posts
* Heisenberg is our Hypervisor server. Running everything.
* Combo is our MySQL database.
* Ehrmantraut is our Git server.
* Skyler is our build server.
Basically that. It's a bit of fun. There are 5 of us in the web team who all watched BB.
There's an RFC on that, too. "Choosing a name for your computer" http://tools.ietf.org/html/rfc1178 Shades of colours, for example https://en.wikipedia.org/wiki/Category:Shades_of_blue , are a good, safe source of names.
Haha, nice idea - would be a nice prank to use: https://en.wikipedia.org/wiki/Category:Shades_of_gray For a network of 50 computers :)
It doesn't matter is my conclusion. where I work we have the remnants of about 5 different naming schemes living side by side (very big environment) and we're not missing out our gaining a thing.
We always resort to some external db (Sometimes just a spreadsheet) to lookup particular hosts based on whatever today's criteria is.
TL;DR it's a distraction. Don't waste time on it.
I used to go with "theme" name like wine oriented (chardonnay, merlot...) But after a while it gets confusing to remember which machine does what and switch to more "functional" names like "worker01, worker02, db01..."
First rule of running a farm: don't name your animals. You'll get too emotionally attached when it comes time to put them down. Yes it's funny and cool et cetera. But, and I say this with love and twenty years' experience, for fucksake: take the time to plan a sensible ontology and stick with it. Hostnames should describe the purpose, capabilities, and disposition of your assets. Nothing more and nothing less.
Periodic table: hydrogen, helium, lithium, beryllium, boron, carbon... and shorthands... h.yourcompany.net, etc... :)
This is my favorite one. For extra awesome, you can use the atomic mass of each element as the last octet of the device's IP address.