Code names

Parmleyhunt · May 29, 2020

How did you decide on the code names for the servers? I have a small rack that I'm slowly building, and when I just had a few devices naming was easy, but as I run out of storage or processing I have to add more. This makes it more difficult to separate devices based off what the device literally is. Although a code name system sounds like it would work better, trying to come up with many unique code names is harder than it sounds.

Senzelian · May 29, 2020

I have a Unraid Server running with an Intel CPU.
I just called the thing "Unraid-Intel".

If I had another one I'd call it "Unraid-Intel 2".

Fishscene · May 29, 2020

Mine for servers is:

s-$Service-$alphabet letter (alphabet letter is optional)

s=server

$Service=Service/Role it hosts.

$alphabet letter=a/b/c,etc.. Using this, I can have 26. At home, I doubt I'm going to have 26 of the same server. Using alphabet tells my brain that there's no particular hierarchy.

Some servers host multiple services, in which case I stick with the primary service it hosts. For example, lancache hosts a DNS server as well as the caching part. It's main role is caching and the DNS services enable it to do that. "s-lancache-a" would be it's name.

------------

Network devices can also host multiple services. I just stick with the main role/service:

n-gateway-a

n-switch24-a

n-wifi-a (when labeling access points, it's nice to just have "a" instead of "AP-3701" or some other long name everyone can see.

Using this, it doesn't matter to me if a server or router is physical or virtual - the role/function is the same. On a larger scale, building the physical/virtual in to the name is important. For me? Not so much. Maybe If I did build it in, I might do "np-gateway-a" or "sv-samba-a". Looks kind of ugly for my taste though.

------------

In a business/work environment, my naming scheme is *completely* different. The name of the server is completely divorced from it's role/function. This adds an addition layer of befuddling for actors who shouldn't be on my network.

Parmleyhunt · May 30, 2020

Currently i have 3 servers and dont have a permanent purpose for any yet besides the freenas so a systematic approach doesnt work because they could share purpose or be repurposed i would really rather go with a symbolic name so that if i call the r710 s-web and then tack on other purposes or completely ditch the web then it no longer applies

Server_42 · July 15, 2020

On 5/29/2020 at 5:07 PM, Parmleyhunt said:

How did you decide on the code names for the servers?

I am assuming that by code name you mean a name for the server.

On 5/29/2020 at 5:07 PM, Parmleyhunt said:

I have a small rack that I'm slowly building, and when I just had a few devices naming was easy, but as I run out of storage or processing I have to add more. This makes it more difficult to separate devices based off what the device literally is. Although a code name system sounds like it would work better, trying to come up with many unique code names is harder than it sounds.

I am also slowly building my rack. Naming definitely isn't has easy has it sounds. However, you could pick a theme like Star Wars and name your servers after things in it like ships or characters. I would recommend finding a theme because it can help you think of ideas for names. Ultimately, the choice of what to name your servers are yours. I hope this helped.