Yeah see, it doesn’t necessarily solve any of these problems.
If you have to do all this guesswork or refer to documentation anyway, maybe just use the human readable and immediately interpretable name of the town the DC is in. Increment a number for each new DC in the area. No cognitive hoops to jump through.
How many Springfields in the US? (65ish)
How many San Joses in the world? (1700ish)
Pennsylvania has two Baldwins, two Whitehalls and two Elizabeths.
“I know we’re physically closer to BDL, but I think we’re culturally closer to JFK and, come on, you know the name is cooler,” says the guy determined to reintroduce bikesheding into the naming process.
There's only one good "closer to" for these purposes, and that's "by packet latency." The prefix is basically the location of the carrier hotel that serves your DC.
This seems to just shift the problem to mapping an airport to the carrier hotel, though?
Re:Choosing a Name for Your Computer
by TRiG_Ireland on Wednesday May 24, 2023 @01:14PM
(#36061191)
Got it. No data centre in Andorra.
The purpose is to have a Schelling point that bypasses any tedious weeks-long arguments. Otherwise your Frankfurt datacenter gets named "ceurope" because the London datacenter got "europe" first, or you named the Ohio datacenter "east" and there's a fight about whether to call the new Virginia datacenter "easter".
[0] If you're building a submerged datacenter in the middle of the Atlantic then ... well, do your best.