Change Details

Currently, aliases for things like enwiki.labsdb and s1.labsdb are maintained as /etc/host entries. Why aren't they just DNS records? This causes a multitude of problems, such as: 1. No easily verifiable single source of truth if two instances differ 2. One more step to be able to forget when creating new toollabs nodes 3. Problematic for other projects on labs This should be in DNS and in puppet (see how public / private aliases are set up with dnsmasq right now)

Currently, aliases for things like enwiki.labsdb and s1.labsdb are maintained as /etc/host entries, manually. Why aren't they just DNS records? This causes a multitude of problems, such as: 1. No easily verifiable single source of truth if two instances differ 2. One more step to be able to forget when creating new toollabs nodes 3. Problematic for other projects on labs This should be in DNS and in puppet (see how public / private aliases are set up with dnsmasq right now)

Currently, aliases for things like enwiki.labsdb and s1.labsdb are maintained as /etc/host entries, manually. Why aren't they just DNS records? This causes a multitude of problems, such as: 1. No easily verifiable single source of truth if two instances differ 2. One more step to be able to forget when creating new toollabs nodes 3. Problematic for other projects on labs This should be in DNS and in puppet (see how public / private aliases are set up with dnsmasq right now)