infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (INFRA-16653) migrate projects-vm
Date Tue, 09 Oct 2018 08:41:00 GMT


Sebb commented on INFRA-16653:

1) Not sure what you mean by this. If it affects exernal users then it may be too early

2) This will stop user updates to releases data, but will stop all access to projects and
reporter, so there needs to be advance warning. Would be better to redirect users to a holding
page, especially since there are public links to projects.a.o (reporter requires login so
only committers can access it). Given that the hosts run puppet, is there any danger that
this will restart httpd?

2a and 2b are the wrong way round.

3) No revert needed. projects-vm2 needs to end up running on a workspace checked out from
SVN trunks rather than the temporary branches. I think it would be best to check out the trunks
in parallel under /var/www (remember they need to be owned by www-data). The names can then
be swapped when everything is ready. 
e.g. checkout pao/trunk as /var/www/pao-trunk. Do checks and copy JIRA extracts etc.
Can then rename /var/www/ => pao-old and rename pao-trunk back to  /var/www/
When all is running OK the old trees can be removed.

> migrate projects-vm
> -------------------
>                 Key: INFRA-16653
>                 URL:
>             Project: Infrastructure
>          Issue Type: Project
>          Components: comdev
>            Reporter: Chris Lambertus
>            Assignee: Chris Lambertus
>            Priority: Major
>              Labels: pull-request-available
> projects-vm needs to be migrated to projects-vm2

This message was sent by Atlassian JIRA

View raw message