[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):

 > I was imaging that any transition plan would look a lot more like: 1.
 set up new thing; 2. point DNS at new thing.

 Not if we want to smoothly integrate the services that will be replaced
 with the ones that will still be hosted on the Linode server (e.g.: valid
 certificates and working outgoing mail traffic).

 Though, I suppose a couple of hours of blackout between step 1 and 2 and
 all legacy services left unreachable could work too.

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