[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:  btlogy
         Type:  enhancement         |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  IaC
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by btlogy):

 Replying here to a comment made my meejah [https://github.com/tahoe-
 lafs/MoveOffTrac/issues/9#issuecomment-3324799019 elsewhere]:


 > Since LA is now threatening to take these servers offline in 3 months
 I'm definitely waiting for that guidance before re-targeting DNS. Please
 direct your questions to him.


 I suppose meejah is referring to "Least Authority July Update" where it is
 said:


 > ... without any instruction from the stakeholders as to the future plans
 for them, we will have to shut them down


 W/o any recent feedback from the stakeholders, it seems fair to wonder if
 those servers are still needed at all.

 At least, the self-hosted replacement of Trac is useless since the right
 DNS records are still not pointing to it. Probably a chicken-egg issue
 here. If the DNS records were targeting the server, there would be a good
 reason to keep the server running.

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