[SAC] [OSGeo] #2363: Move tracsvn to osgeo7

#2363: Move tracsvn to osgeo7
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2019-II
Component: Systems Admin | Keywords:
---------------------------+---------------------------------------
I thought I had this already ticketed but couldn't find it.

As discussed the plan is to get everything off of osgeo3 so we can
reformat it and put in the new disks we purchased, so it will be exactly
the same as osgeo4 in configuration and serve as an lxd host as well.

That said biggest thing left on it is the tracsvn VM which hosts
svn.osgeo.org, git.osgeo.org, trac.osgeo.org.

After that -- short time later I will upgrade the OS (which I have already
experimented with on the dev replica I created on osgeo4).

So here are the steps as I had documented here:
https://lists.osgeo.org/pipermail/sac/2019-September/011514.html

(I changed a little -- to keep the name tracsvn as I think uprading the OS
might be sufficient)

1) Switch over the DNS so that all trac/svn/git points at
OSGeo7 and nginx proxy's over to trac.osgeo.osuosl.org (this will ensure
there is no lag of dns change) **DONE**

2) Send out an announcement to discuss, projects lists that
trac/svn/gitea will be going down for maintenance the following week
**DONE**

3) If all is good - Week after I would do the following

a. Send out an announcement again saying I am shutting down the
services now and they'll be down for about 2-3 hrs (optimistically I could
be done in an hour)

b. Put a under maintenance note in nginx - so all will show - server
is
down for maintenance

c. Shutdown postgres service on tracsvn.osgeo.osuosl.org

d. Shutdown apache on tracsvn.osgeo.osuosl.org

e. Do a final lxd2pc container image of tracsvn.osgeo.osuosl.org ->
pushed to osgeo7 and call it tracsvn

f. Start up tracsvn and configure the IP etc, as I have already
documented in osgeo7 repo -
https://git.osgeo.org/gitea/sac/osgeo7/wiki/tracsvn-old--container-in-
progre
ss (update the repo with current state once I have it back up as my first
test of gitea working)

g. Update the nginx configs for trac.osgeo.org, svn.osgeo.org,
git.osgeo.org to point at tracsvn-old container

h. Send out announcement that services are back up and people should
try at their earliest opportunity and report back with issues.

i. Add tracsvn to list of containers that should be backed up to
osgeo4

j. Update the wiki to reflect trac/gitea/svn have moved and
instructions for people who need to ssh to it

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2363&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2363: Move tracsvn to osgeo7
---------------------------+----------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2019-II
Component: Systems Admin | Resolution: fixed
Keywords: |
---------------------------+----------------------------------------
Changes (by robe):

* status: new => closed
* resolution: => fixed

Comment:

I've completed the move of tracsvn to osgeo7.
I ran into an annoying stumbling block that took me hours to resolved.
It seems our trac can handle ipv6 and when I moved nginx was passing its
ipv6 address along which was preventing sessions in trac to be maintained.
Try as I could I couldn't disable it in nginx. So I disabled ipv6 in the
nginx container itself by doing:

By editing the file /etc/sysctl.conf in nginx container

{{{
net.ipv6.conf.all.disable_ipv6 = 1
}}}

and then reloading with

{{{
sysctl -p
}}}

That seemed to fix the issue. I was hoping to have apache automatically
pick up the forwarded address, but it seems we need mod_remote_ip for that
which requires Apache 2.4 or higher and we are running apache 2.2.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2363#comment:1&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.