10 Reasons I Hate Server Name Changes

There’s been a, um, heated discussion at my work about our current server naming standards. Personally I hate our naming scheme. However, a lot of people have become accustomed to it, and a lot of applications use the standards in their configurations, often to automate management. So when the idea of changing it came up again this week, the O.C.D. part of me was anxious to “fix” our naming. Then I realized just what that meant.

For those that can’t read my handwriting (with explanations):

#10. Time consuming to “fix” existing servers (must update files, DNS, monitoring, reboot, etc)
#9. Nobody is every happy (or rather, for every person you please you probably tick someone else off)
#8. This would be irrelevant if everyone used CNAMEs (’nuff said)
#7. Breaks bcfg setup (our config management system bases some configs on the hostname)
#6. Adds time to RH6 upgrade process (rather than an OS upgrade being transparent, now the owners need to update all their configs)
#5. Invariably will end up repeating this again later (this is the 3rd or 4th naming “standard”)
#4. Angers end-users (they need to update their configs, and notify everyone that depends on their apps – would be irrelevant if #8 didn’t apply)
#3. DCops must relabel everything (datacenter guys must label every server)
#2. Value? Makes us $0. Saves us $0.
#1. Must open 700 WOs for Windows to update DNS (my team does not have DNS rights, so we must open a request and coordinate each change).

If this doesn’t sound like a “make work” project, I don’t know what does.