3 ms·
This reminds me of a client that hired a new IT director and his first order of business was renaming all the machines from their boring names. We had things l
by linsomniac 9y ago
This reminds me of a client that hired a new IT director and his first order of business was renaming all the machines from their boring names.
We had things like database servers named "db1" and "db2", load balancers were "haproxy1" and "haproxy2", web servers "web1" through "web8", that sort of thing.
The new IT director decided to name servers based on city names, where the country indicated the type (Sweden is database servers, Finland is load balancer, Japan is web servers). And these weren't obvious names, ISTR that one of the 20 names I had heard before.
So at 3am when an alert came in saying "Hagfors has high load", you had to know that was in Sweden to know it was one of the database servers. But was it the primary or the secondary?
It seemed a curious decision to make.
- technofiend 9y agoBack when Shell's design pattern required a master NFS server per work group whoever got the money to buy their server got to pick the naming convention. Since most of the servers where I worked were for geologists we ended up with servers named scungilli and murex and lots of really long names that required aliases. And unless you knew your biology classifications very well there was no reason to know which server went with which client.
- whistlerbrk 9y agoThat seems like a curious hire to make.
- linsomniac 9y agoMy recollection was that he wasn't with that company very long...