Posted Mar 8, 2010 16:04 UTC (Mon) by Baylink (subscriber, #755)
In reply to: Code names by jeremiah
Parent article: Fishy business
I would say "well, if we can't trust you to spell 'slicing' and 'dicing' properly, then..." but Jon wants us to be polite and respectful.
So I won't. :-)
Seriously, though: the issue has to do with replacing machines. There are often cases where you *cannot* have two machines existing in the world with the same name; most of these have to do with commercial licensing and other related stupidities.
If you're in such a regime, then you have no other real choice: the machine's "true name" has to be something new, different, and arbitrary -- the last because we've already established that it *can't* be the same name as the box it's replacing, which would then have to already have the functional name.
If you're replacing one outbound FTP server with another already configured server, you drop in the replacement, test it, and then "swing" the DNS CNAME to point to it (as telco guys used to swing jumpers on switch frames at 2am on Sundays on Big Switch Cuts), and you're done.
No muss, no fuss.
But AEleen, Evi, or Tom can probably explain this to you much better than I can. :-)