690008 - move blog.mozilla.com to phx1

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Corey Shields [:cshields]]

+++ This bug was initially created as a clone of Bug #689996 +++

blog.mozilla.com is on the sjc1 generic cluster and needs moved to the phx1 generic cluster.

This is a pretty high profile site so we will want the final cutover to be an announced maintenance.  (final cutover should be a matter of redirecting blog.mozilla.com to hardhat page, re-syncing the data, and moving blog.mozilla.com to the phx1 IP)

In process of doing this, we should make sure everything is up to date software-wise.  there are a lot of plugins there.

Comment 2

[Jake Maul [:jakem]]

The duplicate I just marked isn't really a dupe, but the functionality requested in it will be provided by the dev/stage environments on the phx1 generic cluster. Since no dev/stage environment currently exists, those can go up without a maintenance window.

The only thing that should auto-update on dev would be the themes/plugin directory. On mradm02, this is /data/generic/www/blog.mozilla.com/wp-content:

URL: http://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content

Every 15min should be fine... it's not updated very often. It doesn't need an Apache restart so it could actually be much more frequent, but I don't see that it's necessary.

We do pull the main software from upstream's SVN repo (http://core.svn.wordpress.org/tags/3.2.1) as well, but we don't auto-update that... we "svn switch" to newer tags when we want to do an update.


Stage would obviously not auto-update, but it would be the same repo... there is only 'trunk', no separate tags or anything.

For bonus points we could work with dev to create 'stage' and 'prod' tags, and then those could possibly auto-update as well.

Comment 3

[Jason Crowe [:jd]]

I am curious if I can get commit access to the wp-content directory so I can update the many themes?  Also I would like to know who is responsible for this site so I can talk to them to ensure I don't step on any toes.

Basically I have a number of deprecation warnings to fix.

Thanks

Comment 4

[Jason Crowe [:jd]]

This migration is complete.  I will loop back on some additional mana documentation tomorrow.

Comment 5

[Chris More [:cmore]]

FYI. We lost two weeks of Webtrends data on blogs hosted at blog.mozilla.org. Why? Because Webtrends was only set up to record data *only* when the hostname was blog.mozilla.com and it was rejected when the hostname changed to blog.mozilla.org. We are working with webtrends to retrieve this data and pull it into the reports.