www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Corveleyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-12289) Migrate svn-qavm2 to LW-EU
Date Mon, 08 Aug 2016 23:12:20 GMT

    [ https://issues.apache.org/jira/browse/INFRA-12289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412629#comment-15412629

Johan Corveleyn commented on INFRA-12289:


Yes, I think for starters we need the (role) users 'svnsvn' and 'wayita'. I'd then need to
transfer everything from their homedirs on svn-qavm2 to svn-qavm3 (I can do that myself scp'ing
between the machines I guess).

Then we should have the crontab from user 'svnsvn' configured the same as on svn-qavm2. But
before doing that I should review if the rest is set up correctly.

Concerning the svn version: I think we can get by with release 1.9.4 for now. Is it possible
to make that version available? I can look into building svn from source myself later. I'm
just basing my reasoning a part of https://svn.apache.org/repos/private/pmc/subversion/machines/svn-qavm2/notes.txt:

It is desireable for our backport merge automation to be using the latest
released version of Subversion so as to benefit from the best stable
implmentation of merging we have.  Older versions may do the merge
incorrectly or create incorrect or simply messy merge info.

To that end we do not use the distribution provided version of svn.
Instead we install Subversion from source.

So if you guys can provide version 1.9.4, which _is_  our latest release, that would be great

> Migrate svn-qavm2 to LW-EU
> --------------------------
>                 Key: INFRA-12289
>                 URL: https://issues.apache.org/jira/browse/INFRA-12289
>             Project: Infrastructure
>          Issue Type: Sub-task
>          Components: ColoTasks, VMWare
>            Reporter: Gavin
>            Assignee: Gavin
>            Priority: Trivial
> svn-qavm2 needs to be migrated off of Eirene as the host being decommissioned.
> A new VM will be created, access granted and assist Subversion project in migrating over.
> Or, if Subversion no longer need their VM, just turn off the old instance. 

This message was sent by Atlassian JIRA

View raw message