Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

Opened 9 years ago

Closed 8 years ago

#432 closed task (fixed)

Migrate SVN repositories

Reported by: landauf Owned by: admin
Priority: major Milestone: IT: Server Migration
Component: IT Version:
Keywords: Cc:
Referenced By: References:

Description (last modified by landauf)

The SVN repositories should be migrated to the new server. After the migration they should be available under the same url.

Change History (4)

comment:1 Changed 9 years ago by landauf

  • Description modified (diff)

comment:2 Changed 8 years ago by lferran

Subversion migration

Preliminary comments

The URL should remain the same, otherwise checkouts would not work. In case the URL would change, each user should type this in their local computers, where their checkouts are:

svn relocate OLD_URL NEW_URL

If we want the URLs to remain the same, first the Apache2 virtual hosts configuration in the new server must imitate the one in the old server!

Migration

  1. Create a dump portable file of the repository in the old server:
    svnadmin dump /var/svn/testferran/ > ~/testferran.svn_dump
    
  1. Move it (scp) to the new server.
  1. Create a new repository with the same name in the new server:
    svnadmin create testferran
    
  1. Load the dump file on the new repository in the new server with the

following command:

sudo svnadmin load --force-uuid --bypass-prop-validation\
testferran < ~/testferran.svn_dump
  1. Remember to set the owner and permissions accordingly:
    sudo chown -R www-data:www-data testferran   
    sudo chmod -R 770 testferran
    
  1. Deactivate V2 Protocol Advertisement. Go to the config file of /etc/apache2/sites-enabled/tracrepo.conf and add:
    SVNAdvertiseV2Protocol Off
    

Some issues to solve

  • What do we do about the users:password from the previous pps etc (svnusers file)?
  • What do we do with all other repositories?: I think pretty much all of them must be migrated
  • /var/svn/svnaccess file dictates who can access what in the several repositories that exist in the old server. At the moment, the users and groups are hardcoded in the file… but we want to get thisinformation from LDAP!!

Once we get the users&groups information from LDAP, we can copy&paste&adapt the same permissions that were using before.

Version 0, edited 8 years ago by lferran (next)

comment:3 Changed 8 years ago by lferran

According to #457, repositories to migrate for sure:

downloads game webdev orxonox.OLD (should be read-only)

Other repos not related to orxononx, still pending to decide what to do with them:

biomed datavis netflow orxonox_closed subprojects vseth_projects

Last edited 8 years ago by landauf (previous) (diff)

comment:4 Changed 8 years ago by landauf

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.