I’ve ended up with a number of machines on my network, and a need to name them all in a somewhat logical way. For several years I had them named after the planets, which worked well until the PCs for myself, my girlfriend, servers and Raspberry Pi’s quickly summed up to more than the eight planets. I’ve broadened it somewhat to include any Greek/Roman mythological figure, but the system is definitely not as clean as it used to be.
Do you have a coordinated naming theme for your machines?
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
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:
Still trying to optimize this naming scheme, like removing all the dash, but currently too lazy to do it lol.
My kubernetes cluster is k3s1, k3s2, k3w1, k3w2, etc. My load balancer is called… lb.home.lan. I guess that we are not as creative.