Opened 4 years ago

Last modified 7 weeks ago

#17202 assigned defect

Shut down SVN and decomission the host (gayi)

Reported by: nickm Owned by:
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #31686 Points:
Reviewer: Sponsor:

Description

It is now 2015. Let us not have an SVN server running in 2016.

Child Tickets

TicketStatusOwnerSummaryComponent
#15948closedanarcatCan we do away with public SVN?Internal Services/Service - git
#15949closedanarcatshutdown SVN internalInternal Services/Service - git
#32025newtor-gitadmStop using corpsvn and disable it as a serviceInternal Services/Service - git
#32273newarchive private information from SVNInternal Services/Services Admin Team

Change History (8)

comment:1 Changed 4 years ago by nickm

Owner: set to nickm
Status: newassigned

comment:2 Changed 2 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:3 Changed 6 months ago by nickm

Owner: nickm deleted

I am not actually working on these tickets, so they shouldn't be assigned to me.

comment:4 Changed 4 months ago by anarcat

what's the next step with SVN? we discussed this briefly in Stockholm, and it's unclear to me what the consensus was. it seems it's still in use by some people, or at least *some* parts of it are still in use, according to timestamps:

root@gayi:/srv/svn.torproject.org# ls -alu repositories/*/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû 16 13:02 repositories/corp/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû  9 05:09 repositories/internal/db/current
-rw-rw-r-- 1 www-data www-data 14 aoû 16 16:29 repositories/tor/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû 15 17:51 repositories/vidalia/db/current

that is, all of the repositories have been access in the last two weeks, and the tor one was accessed in the last two days. that said, the latest *commit* on some of those is much older:

root@gayi:/srv/svn.torproject.org# ls -al repositories/*/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû 16 13:02 repositories/corp/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû  4 03:58 repositories/internal/db/current
-rw-rw-r-- 1 www-data www-data 14 mai  8  2015 repositories/tor/db/current
-rw-rw-r-- 1 www-data www-data  5 mar 20  2011 repositories/vidalia/db/current

ie. the corp and internal ones have been written two in the last two weeks, but the tor and vidalia ones have been idle for years (4 and 8 years, respectively).

what we could do is archive (move aside) the last two (tor and vidalia) and see what breaks. then we need to figure out what to do with the corp and internal repos. in #17201, it seems the plan is to move to git, so I guess that would be the next step?

who uses that stuff anyways?

comment:5 Changed 4 months ago by anarcat

Summary: Shut down SVNShut down SVN and decomission the host (gayi)

update: it seems the proper tickets are #15948 (public) and #15949 (private), let's followup there and keep this ticket for the decommissioning of the host (gayi).

comment:6 Changed 3 months ago by anarcat

Parent ID: #31686

gayi is on textile, which we want to decomission, so mark that relation

comment:7 Changed 2 months ago by arma

Ok, I added #32025, for the third prong of this task: retiring corpsvn.

comment:8 Changed 7 weeks ago by anarcat

so svn internal was "shutdown" today (as in: made inaccessible). the public SVN still needs to be archived (#15948) and a decision needs to be made about corp SVN before its shutdown (#32025).

because SVN internal wasn't archived in any significant way, gayi should NOT be destroyed before that data is somewhat sorted through, same with corp SVN. i have opened #32273 to followup on that task.

Note: See TracTickets for help on using tickets.