News for hackers. Stuff that matters.
Re:RFC 1178 – Choosing a name for your computer (1990) by yjftsjthsd-h on Monday April 02, 2018 @10:30PM (#16741433)
Depends how you mean that; I would rather a machine be named prod-app-web-7 than af74b9c. At least mark the cattle by breed!
Re:RFC 1178 – Choosing a name for your computer (1990) by paulmd on Tuesday April 03, 2018 @12:01AM (#16741821)
Winner winner, chicken dinner. As someone who is still managing pets, I even still prefer a standardized naming scheme. I use:

${project}-${dev/staging/web}-${web/db}

(which so far has covered my bases, I'm sure you can come up with any logical extensions if you are running load-balancers or other types of servers, add a number if you are running multiple frontends or clustered DBs, etc)

Even as someone who manages pets, I can't tell you how much time this has saved me from having to look up server names. I have done the generic "assign everything to a single machine## sequence" and it sucks ass. Was your production web server for this app machine32 or machine 54? What about the staging server? Can't even imagine the hassle of uuids as server names.

(of course so far I have done the pets thing in my internal network... but I can tell you that my father with a 40y career in managing servers for major corporations uses names like vmhost01/fsrv01/tvpc at home... which tells you what he thinks of that.)

Re:RFC 1178 – Choosing a name for your computer (1990) by SteveNuts on Monday April 02, 2018 @10:44PM (#16741486)
That goes against the paradigm. I prefer that my hostnames are ambiguous, that way I'm forced to write tools to automate administrative tasks.

If I know the hostname I or my team will be tempted to make one-off changes, breaking the whole "cattle" idea.

Re:RFC 1178 – Choosing a name for your computer (1990) by deathanatos on Monday April 02, 2018 @11:34PM (#16741698)
It is still helpful to have decent names even if you're treating your machines like "cattle" instead of like "pets".

Inevitably, some bug will occur, and in my experience, it usually happens to occur on a machine (rather than all of them at once; I'm not saying this machine is special — the bug could have happened on any of them, and likely exists on all of them because they're all running the same code, but this particular machine ended up being the lucky one to serve that slightly unusual request).

Getting in and debugging the state of that machine, pulling logs, directing a coworker to look at CPU detail "frobnozz", etc. is all easier if I can easily speak or type out the machine's name. "3.dev.microservice" is much easier to type/speak than say, an IP address, an EC2 instance ID, etc.

(I fully agree on not making one-off changes, and not treating machines as pets. But I think that even after that, decent naming has a place.)

And even with cattle, the other way, I still think it's useful for the name to provide some information. I.e., 3.prod.microservice being the third or fourth instance of the production setup of "microservice" is better than say, some random entry from the periodic table of elements.

Re:RFC 1178 – Choosing a name for your computer (1990) by mulmen on Tuesday April 03, 2018 @01:58AM (#16742244)
If you have to say the name of an instance you already lose.
Re:RFC 1178 – Choosing a name for your computer (1990) by semanticist on Tuesday April 03, 2018 @07:34AM (#16743647)
If you do anything to the point of dogma, you've lost. Being a good sysadmin is all about being pragmatic.
Re:RFC 1178 – Choosing a name for your computer (1990) by Pxtl on Monday April 02, 2018 @11:53PM (#16741777)
Then the paradigm is wrong. Serving websites is the most important thing a webserver does, call it that. If that changes, rename it. If renaming it is impossible, you failed.
Re:RFC 1178 – Choosing a name for your computer (1990) by mulmen on Tuesday April 03, 2018 @02:00AM (#16742246)
What about all the application servers behind the load balancers?
Re:RFC 1178 – Choosing a name for your computer (1990) by djur on Tuesday April 03, 2018 @01:17AM (#16742101)
I think it's useful to give long-lived entities memorable names (literally in the sense of 'possible to remember') to allow people to draw fortuitous connections and keep similar entities distinct from each other during discussions. Even if you're just trying to keep track of which server it is that seems to be faulting.
Re:RFC 1178 – Choosing a name for your computer (1990) by mulmen on Tuesday April 03, 2018 @02:01AM (#16742252)
I think its more important that names refer to long-lived resources. If I put a DB name in a connection string I want to see the same data every time. I don't care what hardware it is on.
Re:RFC 1178 – Choosing a name for your computer (1990) by matt_wulfeck on Tuesday April 03, 2018 @12:47AM (#16741988)
There's no reason you can't have both.
Re:RFC 1178 – Choosing a name for your computer (1990) by da_chicken on Tuesday April 03, 2018 @10:28AM (#16744926)
Well, it helps to remember that RFC 1178 is from the days of single monolithic mainframes. Today we've got virtual machines that do everything, so each server can legitimately carry one name. However, if you do call it "prod-app-web-7," then you need to make sure that it's a web server for the app application in production and if that changes, you need to spin up a new server instead of reusing the VM.

But, hey we don't name infrastructure sites "Site 1" and "Site 2". They're "Milwaukee" and "Austin" and "DR". So if we do that, why name them "EMC-SAN-1" and "EMC-SAN-2"? We're going to retire that name eventually and there won't be a SAN 1 anymore. And what happens after "EMC-SAN-9"? So, instead why not "EMC-SAN-ARTEMIS" and "EMC-SAN-APOLLO" and "EMC-SAN-HADES"?

There's a distinction between physical names and logical names, too. What kind of long term nomenclature planning should we have? Look at hurricane names. The NWS does that so people remember which is which.