[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4162: Infrastructure as Code to manage DNS configurations

[Tahoe-LAFS]

#4162: Infrastructure as Code to manage DNS configurations
------------------------------------+-----------------------
     Reporter:  btlogy              |      Owner:
         Type:  enhancement         |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  IaC
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by btlogy):

 To clarify a bit:
 - This issue is about defining the DNS configuration as code, not about
 migrating off Trac (though it would help doing this)
 - The initial proposal described all the way above was to delegate the
 management of the DNS records using features provided by Gandi which is
 currently both the DNS registrar and the DNS hosting party. The new
 proposal described by Blaise in the comment above is an alternative way of
 (hopefully) achieving the same delegation, but by splitting the registrar
 from the hosting.
 - The pros are the same as the ones listed in the initial description (see
 value), in addition to those new ones:
   - separating the role of the registrar from the hosting one would likely
 reduce possible disruption due to losing (access to) one of those party
 (e.g. the DNS zone could be easily migrated elsewhere).
   - the steps to achieve the delegation seem slightly simpler than the one
 describe in comment:7:
 https://docs.gandi.net/en/domain_names/common_operations/changing_nameservers.html
 - As for the cons and more alternatives, I would invite anyone wiling to
 participate to describe those here in some new comments.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4162#comment:15>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage