Opened 4 years ago

Last modified 3 years ago

#18629 new task

archive.tp.o needs a shepherd or it will go away

Reported by: arma Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: weasel, boklm, mikeperry, gk, sajolida Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Weasel has pointed out that archive.torproject.org has no owner, and since the VM needs to move, our policies for services say that it should be shut down unless it gets an owner:
https://lists.torproject.org/pipermail/tor-project/2016-March/000202.html
https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure

It would be wonderful to get it an owner. Since it's where the old Tor Browsers go to live, could I ask somebody from the Tor Browser team to pick this up?

In theory there shouldn't be that much to it. There's a cron job that runs somewhere to copy stuff from dist.tp.o over to archive.tp.o. We should figure out if it's doing the right thing, and make sure it's still doing that right thing after the move. Figuring out how much disk space it has, and when it's going to run out at the current rate of growth, might be wise too.

You would not need to maintain the computer or the apache and so on -- just make sure that the files there are the ones we want them to be, etc.

(There are other files on archive that maybe don't need to be there, but I think it's fine to leave them there for now unless you want to get adventuresome.)

Andrew used to do this, and it's been personless since he left.

Thanks!

Child Tickets

Change History (12)

comment:1 Changed 4 years ago by gk

Cc: weasel boklm mikeperry gk added

I think I agree with Mike that this should not be a Tor Browser team task (even if it were only Tor Browser stuff that would be on archive.tpo which is not the case; there are old and new tor tarballs there as well and other stuff that seems to get updated sometimes). That said I agree as well that one of our team (I'd say boklm, too) could keep this running for a while until we have a proper maintenance plan in place. So, yes, but let's start with a better plan in parallel. I definitely don't want to have this on our plate without a concrete idea of how to move this forward in the right direction.

weasel: What is the deadline here? I am trying to get a handle on how much time we have left to develop a better solution.

comment:2 Changed 4 years ago by boklm

I can keep this running until we have a proper maintenance plan. It has been running with no maintainer for some months, so hopefully it's not a lot of work to keep it running.

comment:3 Changed 4 years ago by weasel

Ok, I added you to the torarchive group.

Currently aroides is the master machine. We need to move this to listera shortly.

I am preparing a copy of the archive as of today on listera, we can do another sync later if you want.

Please familiarize yourself with how it does stuff so we can then move cronjobs and anything else that you might require and decommission aroides.

comment:4 Changed 4 years ago by sajolida

Cc: sajolida added

comment:5 Changed 4 years ago by weasel

Where are we with being able to move the archive stuff?

comment:6 in reply to:  3 Changed 4 years ago by boklm

Replying to weasel:

Please familiarize yourself with how it does stuff so we can then move cronjobs and anything else that you might require and decommission aroides.

I looked on aroides but couldn't find the script that is updating the tor-package-archive directory. Do you know where it is? Is there some cronjobs on the torarchive user?

comment:7 Changed 4 years ago by weasel

I think starting from the crontab is a good idea. You should be able to sudo to the torarchive role user to find out.

comment:8 Changed 4 years ago by boklm

Ok, I've been able to sudo to the torachive user and found the rsync commands in the crontab now, thanks.

Can we do another sync of the archive on listera? I will then enable the rsync commands on listera.

comment:9 Changed 4 years ago by weasel

done.

comment:10 Changed 4 years ago by boklm

I have now enabled the rsync commands in torarchive crontab to keep /srv/archive.torproject.org/htdocs updated on listera.

comment:11 Changed 3 years ago by boklm

It looks like the archiving of files on listera is working correctly. If not already done, I think we can point archive.tpo to listera, and decommission aroides.

comment:12 Changed 3 years ago by weasel

Perfect, thanks boklm.

I have removed aroides from the archive rotation, so only listera remains. I have also updated the symlink/apache config on listera to serve the directory from /srv/archive.tpo.

Is there anything left on aroides you care about?

Note: See TracTickets for help on using tickets.