[Jenkins-infra] Confluence migration planning

[Kohsuke Kawaguchi]

Good question.

Most of such daemons that I can think of interact through HTTP, so they
will get disrupted as the service goes into the maintenance mode, but once
the DNS change propagates they should come back, provided that they refer
to Confluence as wiki.jenkins-ci.org.

I realized that cucumber pulls apache access logs from Confluence via
rsync. I fixed the script so that it refers to wiki.jenkins-ci.org.


2015-04-06 4:29 GMT-07:00 Daniel Beck <ml at beckweb.net>:

> No Reply-To header in this list...
>
> On 06.04.2015, at 13:28, Daniel Beck <ml at beckweb.net> wrote:
>
> > Do we know what automated processes access the wiki regularly (e.g.
> update center generator)? How will these handle the migration? Anything to
> adjust there?
> >
> > On 06.04.2015, at 08:01, Kohsuke Kawaguchi <kk at kohsuke.org> wrote:
> >
> >>
> >> I've successfully run the confluence container on lettuce (albeit with
> temporary throw-away database), so now it's time to plan for the actual
> migration.
> >>
> >> My current goal is to get this migration done in the next weekend.
> Here's the step-by-step description of what I think I'm going to do. Your
> review is appreciated.
> >>      • Disable puppet run on eggplant by manually commenting out puppet
> run with "crontab -e"
> >>      • Switch http://wiki.jenkins-ci.org/ to maintenance by having
> /etc/apache2/sites-enabled/wiki.jenkins-ci.org to
> /etc/apache2/sites-available/wiki.jenkins-ci.org.maintenance. This blocks
> traffic from getting to Confluence
> >>      • Verify from my local browser that http://wiki.jenkins-ci.org/
> is showing maintenance screen
> >>      • Shutdown Confluence via kill ("/etc/init.d/confluence shutdown"
> never work)
> >>      • Take full backup of confluence DB dump & home
> >>      • Disable puppet agent on lettuce by "puppet agent --disable"
> >>      • Stop all docker container services on lettuce (wikidb,
> confluence, and confluence-cache)
> >>      • Wipe out /srv/wiki/home on lettuce, rsync /srv/wiki/home from
> eggplant to lettuce.
> >>      • adjust file permissions on the lettuce's new wiki home (chown -R
> 1000:1001 /srv/wiki/home)
> >>      • merge PR #90 to production. This change shuts down temporary
> mariadb for testing, and switch Confluence to talk to the production DB
> >>      • Re-enable puppet agent on lettuce by "puppet agent --enable"
> >>      • Manually run "puppet agent -t" on lettuce to get Confluence going
> >>      • Manually sanity check Confluence on lettuce by using browser and
> looking around, making edits
> >>      • "service docker-confluence restart" on lettuce and make sure it
> comes back up all right
> >>      • merge PR #91 to make lettuce production. "puppet agent -t"
> manually on edamame and spinach to speed up the propagation of DNS change
> >>      • merge PR #71 to make sure eggplant won't run Confluence.
> >>      • Enable puppet run on eggplant by editing "crontab -e". run
> /root/infra-puppet/run.sh immediately and manully inspect the result. In
> particular, make sure confluence won't run on eggplant.
> >>      • Update datadog dashboard so that it picks up metrics from
> lettuce. tweak monitoring.
> >> Any other things we can do to reduce the risk of migration?
> >>
> >>
> >> --
> >> Kohsuke Kawaguchi
> >> _______________________________________________
> >> Jenkins-infra mailing list
> >> Jenkins-infra at lists.jenkins-ci.org
> >> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
> >
>
>


-- 
Kohsuke Kawaguchi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20150406/d9078879/attachment.html>