| 9 | | 1. Cleaning out space |
| 10 | | a. Clear logs |
| 11 | | a. Remove existing testing.engagemedia.org files |
| 12 | | a. Setup videos.testing.engagemedia.org under /var/www to store freshly transcoded videos |
| 13 | | 1. Setup new clean Plumi 0.2.x installation |
| 14 | | a. Create /opt/backup/plumi2 |
| 15 | | a. Copy over production Data.fs & var/files |
| 16 | | a. Test & verify copied data is working correctly |
| 17 | | 1. Install a new Plumi 3 site under testing.engagemedia.org |
| 18 | | 1. Migrate data from Plumi 0.2.x installation to testing.engagemedia.org |
| 19 | | 1. Migrate the engagemedia.org theme from Plone 2.5 to Plone 3 so it will work with Plumi 3 |
| 20 | | 1. Apply new theme to testing.engagemedia.org'''(complete by 2010-04-09 12:00 GMT)''' |
| 21 | | 1. Thorough testing of testing.engagemedia.org by EM staff '''(complete by 2010-04-14 08:00 GMT)''' |
| | 9 | 1. Preparation Steps |
| | 10 | a. Server Preparation |
| | 11 | i. ~~Set up domains (staging.engagemedia.org & videos.engagemedia.org)~~ |
| | 12 | i. ~~Assess specs for collingwood & estimate duration of migration~~ (920i7 quad core CPU, 2.67GHz, 12Gb RAM) est import = 4 hours, export = 3 hours |
| | 13 | i. ~~Change mount name from /opt/old-colli to /opt/emsite~~ |
| | 14 | a. Data Preparation |
| | 15 | i. Purge old public draft videos (spam, incomplete uploads, etc) - '''Barry''' - ''by Sat 24th Apr'' |
| | 16 | 1. Kick off Migration |
| | 17 | a. Add front page news article about migration and em.org being read-only - '''And''' |
| | 18 | a. Modify Plumi skin to remove login, register & publish functions and add "Migration underway, no site changes allowed. Click here for more information" (where "here" is a link to em.org home) - '''Unweb''' |
| | 19 | a. Set zope database to read-only |
| | 20 | setup Zeos before transcoding |
| 23 | | Once we have completed testing and are ready to focus solely on going live into production we will: |
| 24 | | |
| 25 | | 1. Prepare for production migration |
| 26 | | a. Clear out /opt/backup/plumi2 and reinstall a fresh Plumi 0.2.x system |
| 27 | | a. Copy over production Data.fs & var/files |
| 28 | | a. Test & verify copied data is working correctly |
| 29 | | a. Take copy of engagemedia.org theme from testing.engagemedia.org |
| 30 | | 1. Take engagemedia.org offline (display an "Upgrade in progress" message) |
| 31 | | 1. Backup entire /opt/colli-instances/www.engagemedia.org |
| 32 | | 1. Erase all testing.engagemedia.org files |
| 33 | | 1. Install new Plumi 3 site under testing.engagemedia.org |
| 34 | | 1. Migrate data from Plumi 0.2.x installation to testing.engagemedia.org '''(complete by 2010-04-19 12:00 GMT)''' |
| 35 | | 1. Apply new engagemedia.org theme into www.engagemedia.org (the one saved back in step 1) |
| 36 | | 1. Test to verify testing.engagemedia.org is operational '''(complete by 2010-04-19 14:00 GMT)''' |
| 37 | | 1. Move testing.engagemedia.org over to www.engagemedia.org and open to the public '''(complete by 2010-04-19 17:00 GMT)''' |