629180 - Update support.allizom.org Apache config and update cron

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[James Socol [:jsocol, :james]]

So, it's taken a while, but we are ready to not use any code from SVN anymore!

We've also broken out the locale subdirectory, it is no longer a submodule, so can update directly from SVN which will be faster.

On dm-app-sumo01, we currently have kitsune cloned into the SVN checkout, i.e.:

/data/www/master.support.mozilla.com/.svn
/data/www/master.support.mozilla.com/kitsune/.git

While kitsune should still be in a directory named "kitsune", the SVN parts are now unused. Also, it's a little confusing that the official domain is 'support.allizom.org' and the code is still in 'master.support.mozilla.com'.

The DocumentRoot presumably points to /data/www/master.support.mozilla.com/webroot/. Assuming we rename the site directory to 'support.allizom.org', that can be changed to:

/data/www/support.allizom.org/kitsune/webroot/

The only thing in there is a .htaccess file. (We're working to remove that as a requirement as well, so that we can change the WSGIScriptAlias from /k to /.)

If we replace 'master.support.mozilla.com' with 'support.allizom.org' we'll also need to update two Alias directives.

For the update cron, if it hasn't been done yet, we should rm -rf the locale directory and check it out of SVN directly:

svn checkout https://svn.mozilla.org/projects/sumo/locales locale

Then replace the `pushd locale && git pull origin master && ./compile-mo.sh . && popd` with

pushd locale && svn up && ./compile-mo.sh . && popd

And to the section of the cron that writes to revision_info.txt, we should add something like 

pushd locale && svn info && popd > /dev/null

Then, finally, the update cron doesn't need to svn up from https://svn.mozilla.org/projects/sumo/trunk anymore. We're done with all that now.

Kind of a big change, but we should test it before we get everything installed *with* SVN in PHX.

Comment 1

[James Socol [:jsocol, :james]]

> Kind of a big change, but we should test it before we get everything installed
> *with* SVN in PHX.

That's less clear than I hoped: We should test out the setup without SVN so we can do it without SVN in PHX.

Comment 2

[James Socol [:jsocol, :james]]

Oh, and almost as an afterthought to all that, if we add a -q flag to this cron:

./manage.py update_product_details -q

it won't email us unless something actually goes wrong, which would be awesome for my inbox.

Comment 3

[James Socol [:jsocol, :james]]

Moving the priority on this up as we've starting making changes we'd need to mirror in SVN.

Comment 4

[Jeremy Orem [:oremj]]

Can you bullet all the stuff that needs to be done, so I don't miss anything? You don't need to include specific instructions, since they are above, just general steps.

Comment 5

[James Socol [:jsocol, :james]]

Sure thing!

* Stop checking out svn.mozilla.org/projects/sumo/trunk
* (maybe) move /data/www/master.support.... to /data/www/support.allizom.org
** If so, update any Alias directives
* Change the DocumentRoot to kitsune/webroot/
* Check 'locale' out of SVN instead of Git
** add `svn info` output from the locale directory to media/revision_info.txt
* add -q to update_product_details cron

Comment 6

[Jeremy Orem [:oremj]]

(In reply to comment #5)
> Sure thing!
> 
> * Stop checking out svn.mozilla.org/projects/sumo/trunk
done
> * (maybe) move /data/www/master.support.... to /data/www/support.allizom.org
done
> ** If so, update any Alias directives
done
> * Change the DocumentRoot to kitsune/webroot/
done
> * Check 'locale' out of SVN instead of Git
done
> ** add `svn info` output from the locale directory to media/revision_info.txt
done
> * add -q to update_product_details cron
There is no update_product_details cron enabled right now. Here is the current crontab:
MAILTO=[e-mail]
LANG=en_US.UTF-8
#15 01 * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py build_avatars
05 01 * * 1,4 root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron update_weekly_votes
* * * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron collect_tweets &> /dev/null
* * * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron get_queue_status &> /dev/null
*/30 * * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron calculate_related_documents
#17 * * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron rebuild_kb
00 1,7,13,19 * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron get_customercare_stats
15 01 * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron update_weekly_votes
00 16 * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron reload_wiki_traffic_stats
35 * * * * root /usr/bin/python26 /data/www/support.allizom.org/kitsune/manage.py cron purge_tweets 
03,33 * * * root /root/bin/update_inko.sh
MAILTO=[e-mail]
*/15 * * * * root /data/bin/update-kitsune > /dev/null
#*/15 * * * * root /usr/local/bin/svn-up.sh /data/www/support.allizom.org HEAD force > /dev/null && (cd /data/www/support.allizom.org/webroot && sh htaccess.sh ) > /dev/null
#*/16 * * * * root find /data/www/support.allizom.org/webroot/temp/cache  -maxdepth 1 -type f -not -name "index.php" -exec rm -f {} \;
#*/16 * * * * root find /data/www/support.allizom.org/webroot/templates_c/  -maxdepth 1 -type f -name '*.tpl.php' -exec rm -f {} \;

Comment 7

[Paul Craciunoiu [:paulc]]

(In reply to comment #6)
Woo thanks!

> > * add -q to update_product_details cron
> There is no update_product_details cron enabled right now. Here is the current
> crontab:
Huh. We should add one.

Looks like there is one for support-stage-new, (aka support-release.allizom.org). You can probably just copy the way it's done. Can you add -q to both please?

Comment 8

[Jeremy Orem [:oremj]]

Added.