-the- For hardware.
So Bill-the-laptop Ishmel-the-hometheater Etc
Everything else is cattle to me. Function-namespace-random
But I'm a BIG Kubernetes rke2/k3s/harvester guy
this post was submitted on 16 Mar 2025
28 points (100.0% liked)
Ask Lemmy
30016 readers
1493 users here now
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
founded 2 years ago
MODERATORS
I debated on going Kubernetes, but almost everything I host is stateful, so using built in replication just makes more sense (for my personal home lab, anyway).
I would prefix them with parts of your username, my PC is fusho, my server is fushser and my TV is fushtv. This way it's easy to know what's what for anyone involved.
The 1990's naming conventions are back baby!
- Greek gods
- James Bond villains
- colors
- incremental naming: server1, server1a, Copy_of_server1a, otherserver1, ServerA)
Iocalhost
Yes, that's an uppercase i
Easy there satan
That would be brilliant for a honey trap. The second server on the network switched the second l for an i. The third one has both.
Just give them ordinary names. Then when someone hears you say something like, "I think Greg is due for a reboot" you'll make their day that much weirder.
I'll sometimes pick ordinary names that are loosely related to the function for memory purposes. ingress01 becomes Ingred, cluster01 becomes Gus (i.e., Gus the Cluster), etc.
And of course, if there's a machine that you expect will give you trouble, you name it Richard.
This may be the one. Reminds me of pet naming. Though, my cat was named... Cat.
You are a pragmatic fellow and I respect that.
Okay, more suggestions:
- for the clusters, Gus and Buster
- for ingress, Ingrid and Igor
- for the nas, Cass
- for your Mac mini, Bach
- for your development server, Jessop (short for Jessop the Desktop)
I bought a thin client basically to add as a node for my proxmox homelab, I named it smol
My wife saw eventually and was upset I didn't follow our normal naming convention of Bender-adjacent characters.
cluster01->clusterfuck
cluster02->whattheclust
nas->WhereTheWildThingsAre
ingress01->gandalfthegrey
Ingress02->gandalfthewhite
desktop->gettinserved
macmini-> minimacminiface
Hah, love the cluster names.
Could go with animals from the avatar universe. Turtleduck, platypus bear, armadillo bear, lion turtle, etc
I think there is nothing inherently wrong with using obvious descriptive names like desktop. My personal scheme is to do that and then add a numerical index for categories that have multiple hosts, like switch-0, switch-1. Honestly it makes my life so much easier to not be guessing what things on my network do.
Yea, this is clearly me now. And of course what I do at work but with regions, too. Just looking to do something a bit more fun this time around.
I like Futurama robot names for hostnames.
Yeah, my hostnames are Futurama themed 👍
Go ipv6 and use variations of baad:dead:beef:cafe, no need for hostnames😅
Hmmmmmmmmmmmmmmm. Tempting.
Honestly, if you're not going to go with descriptive names like you have now IMO you should pick something you like and pull the names. You already used streets so you could continue like that, or towns from your region. I'm an old Colorado Avalanche fan so I have Sakic, Forsburg, Roy, Foote and Borque. I would have used Hejduk but I had to look up the spelling just to write this post.
quick edit: clients are all descriptive names: rc__buggy-desktop, rc__buggy-laptop, mrs.rc__buggy-laptop, etc.
Not recommend but all of mine are named after Mesopotamian archeological sites.
Prefix with location abbreviation in case you need to expand in the future.
This is why I did street names originally. I have a server in two locations currently, and can one-command migrate a service between them. So good suggestion since I will still have that option.
I’ve always used an abbreviated site name such as CL1 to represent CoLo, then a shortened description like “db” to represent database server, the a number to use in case there’s more than one.
I also keep it under 18(?) characters to deal with name length limitations.
Tip: You can remove all vowels and it will still be readable.
CL1-DB-01 1st db server in the 1st Colo CL1-JMP-02 2nd jump box in the 1st Colo CL2-Frwll-01 1st firewall in the 2nd Colo.
If you can keep these from being multipurpose then name them what they're for. If they're multipurpose then just name them something totally unrelated. I name apps at work occasionally and if you try to get specific (e.g. network-configurator) you pretty much doom yourself to start using it for something that doesn't match the name.