Version 13 (modified by grant, 7 years ago) (diff)


Migrating to Plumi 3

These are the steps we're following to migrate the site to Plumi 3. They will be come the recommended steps to follow to upgrade other existing sites.

This page shows at a high level the steps to follow and the target dates for conversion of the site. You can also find detailed technical steps in the  MIGRATING.txt file included with Plumi.

Steps & Dates/Times?

  1. Preparation Steps
    1. Server Preparation
      1. Set up domains ( &
      2. Assess specs for collingwood & estimate duration of migration (920i7 quad core CPU, 2.67GHz, 12Gb RAM) est import = 4 hours, export = 3 hours
      3. Change mount name from /opt/old-colli to /opt/emsite
      4. Modify transcode script to use multiple cores - Unweb
    2. Data Preparation
      1. Purge old public draft videos (spam, incomplete uploads, etc) - Barry - by Fri 23rd Apr
      2. Prepare a list of sites with embedded videos in them (small list, for testing later)
      3. Set up with a fresh new Plumi 3 install - Unweb
      4. Configure Staging site with production title & description (& other items that are not migrated) - Unweb
      5. Check that skin is looking correct & up to latest version - And
      6. Add front page news article about migration and being read-only - And - by 3pm Tue 27th Apr
  2. Migration Process - Unweb - On hold - new migration start date/time to be determined
    1. 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 home) - Unweb
    2. Turn off plumiftp - Unweb
    3. Set mail host to an invalid server so emails are not sent out as videos are migrated - Unweb
    4. Set zope database to read-only - Unweb
    5. Export users & content from (est 3 hours) - Unweb
    6. Import users data into (est 1/2 hour) - Unweb
    7. Import content data into (est 3 & 1/2 hours) - Unweb
  3. Start running transcoding - Unweb
  4. Test & Verify - start date/time to be determined
    1. EM staff work through the site to verify all systems are functional while Unweb staff repair any issues (est 2-6 hours)
      1. Fix up list of pages on the left hand side - And
      2. Relink translated pages - And
      3. Go through feature testing list - All EM Staff
      4. Add tag cloud portlet - And
  5. Move staging to production
    1. Stop transcoder - Unweb
    2. Shut down site (production) - Unweb
    3. Shut down site - Unweb
    4. Change apache configuration so is directed to staging installation (now the new production site) - Unweb
    5. Start up new production site - Unweb
    6. Test that embedded videos from the old site are still working (use list of test entries) - And
    7. Start transcoder again using Dimo's "resume" script - Unweb
    8. Edit PlumiFTP config file to suit new production site and start plumiFTP - Unweb
    9. Test PlumiFTP & verify operating correctly - EM Staff
    10. Monitoring of new site while people start using it - EM Staff
  6. Release Plumi 3 to the world = Unweb
  7. Post install clean up
    1. Reset transcoder script to use only 1 or 2 cores - Unweb
  8. Set up ZEO on collingwood - Unweb
  9. Go have a few beers - Everyone