Re: [tor-bugs] #29399 [Internal Services/Tor Sysadmin Team]: Retire host and services for tordnsel and check

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#29399: Retire host and services for tordnsel and check
-------------------------------------------------+---------------------
 Reporter:  ln5                                  |          Owner:  tpa
     Type:  task                                 |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Tor Sysadmin Team  |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:                                       |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+---------------------

Comment (by anarcat):

 Okay, so what's the plan then?

 Supporting chuiwi is going to get harder and harder. We can probably
 afford to do so a little longer, but things are going to progressively
 break as we go along. Mow it's backups: there *might* be a way to backport
 things to chiwui to make them work, but it will be a waste of time if we
 get this fixed otherwise later anyways. But other things might break in
 the future as well...

 For now, I've "acknowledged" the backups warnings in Nagios for this host,
 which means we will not fix backups for this host in the short term. I
 assume this is okay-ish: the older backups (from april 23rd) are still
 there and from what I understand the contents on that host are not
 changing (it's the problem we're trying to solve!).

 Could the problem be split in two? Maybe "check" can be upgraded and not
 the other? Or are the two services as critical and inter-dependent?

 For the record, someone mentioned "Docker" as a solution here, and I
 somehow disagree: it would certainly shift the burden of maintaining the
 jessie box away from us (TPA) but we would *still* have to maintain *some*
 environment with the older Haskell, which is the problem we're trying to
 solve in the first place.

 It would allow us to upgrade the box and resume backups, so it's a
 possible alternative in the mid term, but it just shifts the upgrade
 problem under a container veil. I'm worried it would make us just forget
 about it and create another liability.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29399#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs