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.

  • refreeze@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    6 hours ago

    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.

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

      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.

  • owenfromcanada@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    8 hours 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.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 hours 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
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        6 hours 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.

  • hddsx@lemmy.ca
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    8 hours ago

    cluster01->clusterfuck

    cluster02->whattheclust

    nas->WhereTheWildThingsAre

    ingress01->gandalfthegrey

    Ingress02->gandalfthewhite

    desktop->gettinserved

    macmini-> minimacminiface

    • fmstrat@lemmy.nowsci.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 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
        ·
        3 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.

  • traches@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    ·
    8 hours ago

    Could go with animals from the avatar universe. Turtleduck, platypus bear, armadillo bear, lion turtle, etc

  • BrianTheeBiscuiteer@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 hours ago

    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.

  • rc__buggy@sh.itjust.works
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    8 hours 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.