change developer.mozilla.org to kuma repos, mdn branch

VERIFIED FIXED

Status

Infrastructure & Operations
WebOps: Other
--
enhancement
VERIFIED FIXED
7 years ago
4 years ago

People

(Reporter: groovecoder, Assigned: jakem)

Tracking

Details

(URL)

(Reporter)

Updated

7 years ago
Blocks: 655393
(Reporter)

Comment 1

7 years ago
Okay we're ready to do this whenever you are jake. Let's be sure of the rollback plan before we start since this is LIVE LIVE LIVE!
Severity: enhancement → major
Punting to Jake :)
Assignee: server-ops → nmaul
(Assignee)

Comment 3

7 years ago
This has been completed. Below is what was done (copied from etherpad, just in case).

I understand that there is going to be another push soon, to fix up some bugs that have been (re)discovered. During that push, we will also get rid of the ".new" moniker and move or remove the original (non-merged) tree from the systems.

Here is roughly what will be needed to accomplish that (for reference):

mv developer.mozilla.org developer.mozilla.org.old (on mradm02)
mv developer.mozilla.org.new developer.mozilla.org (on mradm02)
Update Apache configs to make point to this location (puppet)
Restart Apache, test again
rm developer.mozilla.org.old ??? (on mradm02)
update cron jobs (on mradm02) - /etc/cron.d/developer.mozilla.org-django





Add the new django dir
# written from sm-devmostage; adjust directories as necessary for mradm prod
# make a new directory for kuma repos clone
cd /data/www/django
mkdir developer.mozilla.org.new
git clone git://github.com/mozilla/kuma.git developer.mozilla.org.new/kuma
cd developer.mozilla.org.new/kuma
# change to the mdn branch and update recursively to get vendor/
git checkout mdn
All above here done
git submodule update --init --recursive
done
# get the locale/ repos
svn co http://svn.mozilla.org/projects/mdn/trunk/locale
done
Copy settings_local.py from "old" mdn dir:
cp developer.mozilla.org/mdn/settings_local.py developer.mozilla.org.new/kuma/settings_local.py
done
Create django resources
cd //developer.mozilla.org.new
mkdir product_details_json
done
cd kuma
python26 manage.py update_product_details
python26 manage.py compress_assets
both done
Add symlink to uploads
e.g., kuma/media/uploads -> /mnt/netapp/developer-stage.mozilla.org-dekiwiki/uploads
No symlink for prod... looks like Apache has a direct Alias to the netapp mount
THIS LOOKS LIKE THE ONLY ROLLBACK NECESSARY?
Change developer.mozilla.org.conf:
-Alias /media /data/www/django/developer.mozilla.org/mdn/media
+Alias /media /data/www/django/developer.mozilla.org.new/kuma/media
-Alias /admin-media /data/www/django/developer.mozilla.org/mdn/vendor/packages/Django/django/contrib/admin/media
+Alias /admin-media /data/www/django/developer.mozilla.org.new/kuma/vendor/packages/Django/django/contrib/admin/media
-WSGIScriptAlias /mwsgi /data/www/django/developer.mozilla.org/mdn/wsgi/mdn.wsgi
+WSGIScriptAlias /mwsgi /data/www/django/developer.mozilla.org.new/kuma/wsgi/kuma.wsgi
changes made in puppet svn, waiting for puppetmaster checkout
checked out on puppetmaster, syncing to servers
THIS MAKES IT LIVE - MAKE SURE QA AND ROLLBACK ARE READY
Restart Apache
/etc/init.d/httpd restart
Change .htaccess symlink
e.g., /data/www/dekiwiki9/.htaccess -> ../django/developer.mozilla.org.new/kuma/configs/htaccess
Test https://developer.mozilla.org/
Severity: major → enhancement
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
verified fixed https://developer.mozilla.org/
Status: RESOLVED → VERIFIED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.