• corsicanguppy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    7 months ago

    The gist of rfc1178 is

    • don’t name them incomprehensible shit
    • don’t name them indistinguishable shit
    • don’t name them unpronounceable shit
    • don’t name them after their ephemeral purpose (less an issue now since it’s one service per cattle member)

    I worked at a shop where it was all ussfllb02 (a Linux load balancer in San Fran) and ukloesto12 (an emc array in London) and that’s how they went all over the globe for like 15 DCs.

    But then it got hard to keep the numbers straight, and we’d patch boxb10 instead of 01 or something, and the very real issue where humans can’t keep abstract glyphs in their head for too long became a problem.

    I’ll do RedTruck and GreenBoat every time.

    • Kurotora@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      7 months ago

      I’ve felt the same pain, coming from enterprise environment with strict naming convention. So, of course, at home I avoid that like eating sh*t.

      At home my servers are called after my deceased pets, little tribute of their precious time on earth, based on their “capabilities”. Some raspberry pis with small services named after our squirrel and cats and the big ones named after our dogs. That way they continue somehow with us, even after leaving us for more than 15 years.