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 Fri, 05 Aug 2016 22:07:20 GMT

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

Johan Corveleyn commented on INFRA-12289:

I'm gradually getting a clear picture of _what_ I need to do (create users "svnsvn" and "wayita";
transfer or reinstate the corresponding data they need; build svn from source so there is
a recent client; set up the crontabs). But I'm mostly struggling with the _how_.

Understanding how to configure things in the puppet3 syntax will probably not be too difficult
I guess (the copy-paste pattern has never let me down), but I'm mainly wondering about how
to test / validate the puppet config, and how to transfer the stuff to you guys.

* Can I test / verify my changes locally or on the VM before submitting a PR? To avoid infra
doing unnecessary work correcting simple syntax errors (or to avoid useless deploy/fix/deploy
cycles). How to develop this thing iteratively without bothering too many people?
* Can I submit the necessary changes without needing git? Not merely out of lazyness (although
...) but mainly to avoid unnecessary work on my part and having to mount yet another learning
curve for seemingly little gain. Judging from the Github interface I see I should be able
to download or svn-checkout, or fork ... Can I also perform my changes that way and submit
the PR (or whatever) you guys need?

> 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