What do you name your servers?

Alex Sage

How often do you need to really know that at a glance?

You don't need to know at a glance, but why not? If you going to take up characters to define it as linux, why not give the distro instead?

scottalanmiller

@anonymous said:

@scottalanmiller said:

How often do you need to really know that at a glance?

You don't need to know at a glance, but why not? If you going to take up characters to define it as linux, why not give the distro instead?

Well if you are going to script things super quickly, it's nice to say...

for i in $(grep lnx servers); do ssh $i uptime; done

scottalanmiller

@anonymous said:

@scottalanmiller said:

How often do you need to really know that at a glance?

You don't need to know at a glance, but why not? If you going to take up characters to define it as linux, why not give the distro instead?

Well if you are going down that path, though, wouldn't version numbers be useful? Whats the benefit of knowing CentOS but not 5 vs 6? Knowing the OS is somewhat useful, but I'm not sure it is useful enough. What change in behaviour are you anticipating from identifying CentOS, Ubuntu, Suse, Fedora, Arch, etc.?

We DO code VyOS differently, even though it is Linux under the hood.

Alex Sage

@scottalanmiller said:

What change in behaviour are you anticipating from identifying CentOS, Ubuntu, Suse, Fedora, Arch, etc.?

Different commands, - yum, vs apt-get, etc.

https://help.ubuntu.com/community/SwitchingToUbuntu/FromLinux/RedHatEnterpriseLinuxAndFedora

scottalanmiller

@anonymous said:

@scottalanmiller said:

What change in behaviour are you anticipating from identifying CentOS, Ubuntu, Suse, Fedora, Arch, etc.?

Different commands, - yum, vs apt-get, etc.

https://help.ubuntu.com/community/SwitchingToUbuntu/FromLinux/RedHatEnterpriseLinuxAndFedora

But you need version numbers for that too. The distro name alone is not enough. Fedora 22 drops YUM, for example. Different versions have different service commands and packages.

When would you use only the distro name?

@IRJ said:

Server1
Server2
Server3
Server4
Server5
Server6
Server7
......
......
......
Server88
Server89
Server90
......
......
Server152
Server153
Server154
.......
.......
and so on

Um I hope not How do you know what they do?

@scottalanmiller said:

We use a code like this....

[datacenter]-[os]-[application or function][number]

So a Toronto based Linux server for MySQL might be...

to-lnx-maria1

Pretty much what we use. Except Ours is

[Business Unit]-[Datacenter]-[OS]-[Function]-[Number if multiples in the same location]

creayt

@anonymous said:

What do you name your servers?

We have a very small pool of servers ( less than 15 ) and use fun names based on their overall prowess or any unique characteristics.

Goliath
Ares
Achilles
Cheetara
Sanctuary

JaredBusch

I once named the devices of an entire network after the characters in the 5th element.

Currently, everything is named
[client][primary role][server number]
bundydc01
bundysd01
etc.

gjacobse

@JaredBusch said:

I once named the devices of an entire network after the characters in the 5th element.

Currently, everything is named
[client][primary role][server number]
bundydc01
bundysd01
etc.

Did you have a security server called Multi-Pass?

JaredBusch

@g.jacobse said:

Did you have a security server called Multi-Pass?

It was the ID card printing computer actually.

nadnerB

Work stuff is kind of boring
Location-<abbreviation of function><number = orderofbuild>
Home stuff is always planets from the Star Wars Universe.

Main Home PC is Courescant (bright center of the universe )
NAS is Hoth (it's white)
eeepc is Corellia
Xubuntu laptop is Byss