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.

  • Fushuan [he/him]@lemm.ee
    1·
    31 minutes ago

    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.

  • fruitycoder@sh.itjust.works
    1·
    2 hours ago

    <UniqueName>-the-<type of computer> 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

  • partial_accumen@lemmy.world
    2·
    7 hours ago

    The 1990’s naming conventions are back baby!

    • Greek gods
    • James Bond villains
    • colors
    • incremental naming: server1, server1a, Copy_of_server1a, otherserver1, ServerA)
  • owenfromcanada@lemmy.worldEnglish
    3·
    2 days ago

    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.

      • owenfromcanada@lemmy.worldEnglish
        1·
        2 days ago

        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)
      • Jakeroxs@sh.itjust.works
        1·
        2 days ago

        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.

  • rc__buggy@sh.itjust.works
    1·
    2 days ago

    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.

  • hddsx@lemmy.ca
    1·
    2 days ago

    cluster01->clusterfuck

    cluster02->whattheclust

    nas->WhereTheWildThingsAre

    ingress01->gandalfthegrey

    Ingress02->gandalfthewhite

    desktop->gettinserved

    macmini-> minimacminiface