21–30 of 128 posts
Like a lot of things, people can remember names of things better than numbers. Genes for example, it’s easier to remember their names lz, wnt, than their associated gene Id number. But like stars and many other things there are too many to give each a unique name. Naming can make sense, our old cluster was named after orchestra parts. When you logged In you where placed on the lobby. The machines where clustered (vio…
I can't find the post that linked it, but it had a very nice scheme.
EDIT: found it: https://mnx.io/blog/a-proper-server-naming-scheme/
EDIT2: one-liner to get a random word from the file:
cat wordlist.txt | tail -n +2 | sed -E 's/\s*(\w+)\s+/\1\n/g' | sed -E '/^$/d' | shuf -n 1
i.e. | | | |
This kind of naming is fine for small projects, and personal setups. In professional settings I would suggest using descriptive names and rely more on DNS. It's not that I don't enjoy fun and personal naming schemes, it's just that it's a constant annoyance when dealing with a large number of different systems. We've been hired to deal with different companies, who picks some random naming, cars, athletes, plants, ci…
Anyway, is prod-web01 that server with an outdated web server that you keep because of that one system that couldn't migrate, the one with a Java server that runs those proprietary tools, the one with IIS that runs that FOSS code that the developer decided to write in C#, the one supporting your main applications or the one you insulated in a special network because it hosts a powerful API that you don't want to expose?
This kind of naming is fine for small projects, and personal setups. In professional settings I would suggest using descriptive names and rely more on DNS. It's not that I don't enjoy fun and personal naming schemes, it's just that it's a constant annoyance when dealing with a large number of different systems. We've been hired to deal with different companies, who picks some random naming, cars, athletes, plants, ci…
This was written in 1990, though, and there was no cloud, and VMs were quite rare things, (and we had to walk to school uphill, both ways, in the snow). Machines were physical things, and no one had the budget to buy an entire computer to be the second production web server - a machine ran a lot of different daemons that did a lot of different things, and the roles and responsibilities of a given physical piece of hardware would change as time went on. Which is still true today, but today it's just that a machine runs a lot of docker containers instead of running a lot of daemons, and we don't care where the docker containers are running, whereas back then we very much cared what machine it was running on, because sometimes we had to go to that machine and reboot it or kick it or install more RAM.
At the time, I was working at Alcatel (before it was Alacatel-Lucent, before that became Nokia), on a 450Gbps switch which was used for things like routing satellite TV feeds or handling distribution from big fiber backhauls, or running LANe for small nations. On the third floor, we had several racks of these switches in "the lab" which we used for testing and development work. While you could push a new software load from the comfort of your desk, if you borked things badly enough you'd sometimes have to go downstairs and plug a serial cable into the front of the control card so you could go poke around and force the card into a sane state.
So, when a new hire came in, they might say, "Hey mrweasel, I uploaded a bad load to Spock, and it's stuck in a boot loop. Where can I find that physical machine?" And you'd say, "Head down to the third floor, turn left out of the elevators, walk to the second last row of racks. On your left there should be switches named "Picard", "Riker", "Deana", etc..., and on your right should be "Kirk", "McCoy", and friends. Spock is third on the right between McCoy and Uhuru."
That conversation is way more confusing if all of these machines are named "test01-test20". You couldn't even name them that - there were lots of different products in different areas of the lab, so you'd need the product name in there, and they'd be "rsp7670-test01" through "rsp7670-test20".
And, when you want to push a new build from your desk, it's way less likely you'll mistype "picard" when you want to update "data", but it's quite easy to accidentally clobber "rsp7670-test05" when you mean to overwrite "rsp7670-test06", which was sure to summon an angry developer to your desk asking why you just killed their 48 hour validation testing, 45 hours in.
Shameless plug, CLI for reading IETF RFCs. https://github.com/cy6erlion/ietf You will read this RFC like this: $ ietf -n 1178
I use the wordlist from Oren Tirosh’s mnemonic encoding project: http://web.archive.org/web/20090918202746/http://tothink.com... I can't find the post that linked it, but it had a very nice scheme. EDIT: found it: https://mnx.io/blog/a-proper-server-naming-scheme/ EDIT2: one-liner to get a random word from the file: cat wordlist.txt | tail -n +2 | sed -E 's/\s*(\w+)\s+/\1\n/g' | sed -E '/^$/d' | shuf -n 1 i.e. | | |…
Use anime character names. That way you have an excuse to collect cute artwork for these machines.
It's easy to be nostalgic for the days of big iron servers or clusters that were around for years as a sort of network landmarks. We used to have dev and QA clusters named after movie monsters and you'd get some great hallway conversations about who was using Godzilla that week. Made for great mascot toys and posters on the rack doors.
(My machines all have musical instrument names).
I use the wordlist from Oren Tirosh’s mnemonic encoding project: http://web.archive.org/web/20090918202746/http://tothink.com... I can't find the post that linked it, but it had a very nice scheme. EDIT: found it: https://mnx.io/blog/a-proper-server-naming-scheme/ EDIT2: one-liner to get a random word from the file: cat wordlist.txt | tail -n +2 | sed -E 's/\s*(\w+)\s+/\1\n/g' | sed -E '/^$/d' | shuf -n 1 i.e. | | |…
It is fairly straightforward to incorporate into your infrastructure as code workflow for managing your "cattle".
https://mtg.fandom.com/wiki/Forest
These days, for work, it’s just boring unambiguous stuff. I think with more cloud infrastructure and the rarity of shared unix servers with home directories for people, it’s rare that I have any emotional investment in a machine. They’re basically soulless now.
* Don't overload other terms already in common use.
* Don't choose a name after a project unique to that machine.
* Don't use your own name.
* Don't use long names.
* Avoid alternate spellings.
* Avoid domain names.
* Avoid domain-like names.
* Don't use antagonistic or otherwise embarrassing names.
* Don't use digits at the beginning of the name.
* Don't use non-alphanumeric characters in a name.
* Don't expect case to be preserved.
* Use words/names that are rarely used.
* Use theme names.
* Use real words.
* Don't worry about reusing someone else's hostname.
* There is always room for an exception.