Iocalhost

Yes, that's an uppercase i

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.

The 1990's naming conventions are back baby!

• Greek gods
• James Bond villains
• colors
• incremental naming: server1, server1a, Copy_of_server1a, otherserver1, ServerA)

-the- 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

cluster01->clusterfuck

cluster02->whattheclust

nas->WhereTheWildThingsAre

ingress01->gandalfthegrey

Ingress02->gandalfthewhite

desktop->gettinserved

macmini-> minimacminiface

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.

I like Futurama robot names for hostnames.

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.