do birds fly? do ducks duck?
this post was submitted on 18 Jul 2023
4 points (100.0% liked)
Selfhosted
40132 readers
741 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Every machine is named after what it does (although I do 1337-ify the names, because I'm still a late 90s IRC teen at heart). If you've ever been onboarded into a sysadmin role where all the machines are named with whatever whimsical naming scheme each department chose, you'll fast develop a visceral hatred for non-descriptive naming schemes. The fifth time you get a ticket saying something like 'Hedwig is down' and you have to go crawling through three layers of linked files on SharePoint to find what and where 'Hedwig' is, you'll be ready to beat the person who named it to death, and that attitude tends to persist to your home naming scheme :p
So more of a "cattle" than "pet" approach in general?
The fifth time you get a ticket saying something like ‘Hedwig is down’
If only there was an excellent database to store where Hedwig.bthl4.sea.wa.goliath.corp was and maybe include an alias so you know it's NNTP5.goliath.corp also.
I shall invent one. It shall replicated and synchronize quickly. It shall interface and accept changes and share data. It will be simple to query so everyone can use it. I shall call it DNS . If people get snippy, I shall next invent an HS record.
Learn to use the tools, man. It'll help you adhere to a 40-year-old RFC on naming things.
Yes, if you've built the network from scratch that works. Retrofitting it into an existing network however is a massive piece of work when you don't have that single source of truth to start with however. On networks I've built sensibly, I'll happily give people whatever CNAME they want to refer to their machine, but the machines actual name is descriptive, not the other way round.
Rfc1178 be damned.
I'll get right on rearchitecting the dns infrastructure of a large sprawling corporation, with mountains of technical debt from decades of acquisitions where they just mashed shit together. I'm sure that project will get approved.
Don't be condescending, man.
Well I'm glad you know it's there!
I can't comment on your particular technical debt, as I'm not very psychic. I like how you say not to be condescending and require me to be psychic. That's cool, but I bet you're stressed.
Have a good week.
Because I’m a huge dork, all my machines are named after the FFXIV jobs:
Desktop-Red Mage Laptop-Machinist RaspberryPi-Sage etc.
Personally I use corporate-like naming scheme for my devices, the format is:
[AABB-CCCC-DDEE]
AA: Location of the device - HQ (home), CL (cloud).
BB: Role of the device - HV (hypervisor), SV (server), NW (network) and workstation (WS).
CCCC: Device brand (for NW), application running (for SV), and workstation purpose (for WS).
DD: For server and workstation - OS running on the device (WN=Windows, LX=Linux, MA=macOS). For network device - their role on network (RT=router, AP=access point, SW=switch).
EE: # of the device, year of purchase for WS.
For example, here's my router, KASM server and my gaming PC hostnames:
HQNW-UBNT-RT01
HQSV-KASM-LX01
HQWS-GAME-WN16
Still trying to optimize this naming scheme, like removing all the dash, but currently too lazy to do it lol.
I name my machines after my cats.
Discworld characters. My storage servers name is Luggage, my phone is 'Ig', the vacuum is named after a monk.
I'm incredibly boring. I name them with the company/model name. And what role they have appended.
Cute naming schemes are for people who don't have lots of servers. At my work we have over 700 servers. We're not naming them after something arbitrary, we're being descriptive.
Ungulates. Because who doesn't like a hoofed animal?
My client machines are even-toed ungulates (order Artiodactyla) and my servers/IoT machines are odd-toed (order Perissodactyla). I'm typing this on Gazelle. My router is called Quagga, both after the extinct zebra subspecies and the routing protocol software (I don't use it any more but hey, it's a router).
Biological taxonomy is a great source of a huge number of systematic (and colloquial) names.
Depending on the size of the machine I'll call it big/large/huge/small/Lil then a human name like John. BigJohn is my main server and hopefully one day he can get an upgrade and become large John.
This, but it’s all suggestive names, such as:
Big Johnson, Small Richard, lil Peter, Huge Willy, etc.