Changes between Version 3 and Version 4 of MigrationFromEtch
- Timestamp:
- 04/27/10 19:03:40 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MigrationFromEtch
v3 v4 34 34 === Migration plan - preparatory stage === 35 35 1. Formulate plan on how to communicate with users during the migration process; begin gathering required contact info if necessary 36 1. Calculate the approximate size and rate of change of each type of data on the server 36 37 1. Give preliminary notice to users and ask for feedback 37 38 1. Configure domain name etch.haskell.org (will later become read-only copy and left active for a while as a backup) … … 41 42 1. Install and perform basic configuration of all services 42 43 1. Test all installed services 43 1. Write scripts to copy user accounts and home directories, and to verify44 1. Write scripts to copy user accounts and rsync home directories, and to verify 44 45 1. Write scripts to copy project groups in /etc/group, and to verify 45 1. Write scripts to copydarcs repos from /srv/projects, and to verify46 1. Write scripts to copyproject data from /srv/code, and to verify47 1. Write scripts to copytrac projects, and to verify48 1. Write scripts to copy mailman lists , and to verify49 1. Write scripts to copyPlanet Haskell, and to verify50 1. Write a script to make all user data and projects read-only , and to verify.46 1. Write scripts to rsync darcs repos from /srv/projects, and to verify 47 1. Write scripts to rsync project data from /srv/code, and to verify 48 1. Write scripts to rsync trac projects, and to verify 49 1. Write scripts to copy mailman lists and rsync archives, and to verify 50 1. Write scripts to rsync Planet Haskell, and to verify 51 1. Write a script to make all user data and projects read-only (except mailman archives), and to verify. 51 52 1. Write a script to *undo* making things read-only, in case of emergency. 52 53 1. Test all scripts thoroughly 53 1. Fix a date for migrationand give advance notice and instructions to users.54 1. Fix dates for beginning initial copy and final migration, and give advance notice and instructions to users. 54 55 1. Transfer RT database and verify (as a dry run, go through the entire migration process just for RT) 55 56 1. Move the rt domain 56 57 1. After TTL, verify that RT is working on the new server 57 58 59 === Migration plan - Initial copy === 60 1. Run script to copy user accounts. Verify. 61 1. Run script to copy /etc/group entries for projects. Verify. 62 1. Run scripts to rsync home directories, darcs repos, project data, trac projects, mailman archives, and Planet data 63 1. Monitor progress; update schedule and notify users as needed 64 1. When completed, verify. 65 58 66 === Migration plan - D-Day === 59 67 1. Notify users. 60 1. Make all user data and projects read-only. Verify. 61 1. Run scripts to copy user accounts and home directories. Verify. 62 1. Run scripts to copy darcs repos, project data, and Trac project. Verify. 68 1. Stop the Planet Haskell hourly cron job. 69 1. Run script to make all user data and projects read-only. Verify. 70 1. If any user accounts or projects were added since initial copy began, add them. 71 1. Run scripts to rsync home directories, darcs repos, project data, and Trac projects. Verify. 72 1. Stop mailman service on etch. 73 1. Run the scripts to rsync mailman archives. Verify. 63 74 1. Move the domain CNAME for community, trac, projects, and code. 64 75 1. After TTL, verify remotely that the domains moved and that services are working. 65 1. Notify users of current status. 66 1. Run the scripts to copy mailman lists. Verify. 76 1. Notify users of current status. 67 77 1. Tell Ian and Malcolm to check their mail. 68 78 1. Move the domain MX records. 69 1. Run the scripts to copyPlanet Haskell. Verify.79 1. Run the scripts to rsync Planet Haskell. Verify. 70 80 1. Move the planet domain. 81 1. Start the Planet Haskell hourly cron job. 71 82 1. After TTL, verify remotely that '''all''' domains are moved and that '''all''' services are working. 72 83 1. Notify users and community. … … 77 88 1. After a day or two, raise TTL back to normal levels on all domains 78 89 1. After a month or two, delete the Etch server 79
