Hi everyone,

I’ve been a single-server built from whatever desktop I upgraded for years kind of guy, with a hostname of the street it is on (better than server, which is what it used to be).

However, at some point in the future my home lab will be located in a place I will not have immediate access to, and since it’s getting on in age and due for an upgrade anyway, I’m going to build in some redundancy. So, current names:

  • OPNsense micro-router: ingress01
  • OPNsense backup: ingress02
  • Cluster micro-server with essential services: cluster01
  • Cluster micro-server with non-essential services and replicated essential services: cluster02
  • NAS: nas
  • Powered on remotely when needed:
    • Mac mini dev/release box: macmini
    • Primary remote development server (basically my old desktop): desktop

Bring on the Mini-MacMinifaces, and any other ideas you have.

  • fmstrat@lemmy.nowsci.comOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 hours ago

    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.

    • Brkdncr@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      7 hours ago

      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.