3 ms·
Even when you pick a naming scheme, it'll eventually cause grief if you get big enough. Name your machines XXYYN[N] where XX is the building name, YY is the ra
by rachelbythebay 12y ago
Even when you pick a naming scheme, it'll eventually cause grief if you get big enough.
Name your machines XXYYN[N] where XX is the building name, YY is the rack name and NN is the position in the rack? You'll eventually have more than 676 buildings, 676 racks, or 99 machines in a rack. Multiple people will have written regexes to split that into building, rack, position and they will break when you grow one of the fields.
- dredmorbius 12y agoThat's where the subdomain-based CNAME system comes in handy. And I'd argue that building numbers probably don't want to be part of your scheme. purpose###.env.loc##.domain.tld is about as deep as I'd like to get with my hostnames (though there are other options for shortening them, with DNS search directives and such). Encoding: purpose###.rac###.cab###.aisle###.env.loc##.domain.tld ... might keep you from losing boxen. You will hate yourself typing that. Store the metadata elsewhere, perhaps a txt record for the host.