jrwdunham
commented
2 months ago I have boiled down the data (OLD) migration part down to these three commands:
dodative:$ ./dump-old-dbs.sh
local:$ ./sync-do-old-to-local.sh
int:mysql> source /home/joel/load-do-mysql-dumps.sqlThe plan for migration is as follows.
- DONE. Document the migration status and completion plan in the runbook.
- DONE. Draft an email to send to users of Dative.
- DONE. Ensure we have Nginx config ready for dative.ca on INT.
- DONE. Share the migration completion plan with technical stakeholders for feeback.
- DONE. Set a date and time for the migration. Suggestion: June 28, 2024.
- DONE. Get feedback on the email and plan from internal stakeholders.
- TODO. Confirm that the migration transfers the data correctly.
- TODO. Ensure we have the commands ready to shut down DO Dative and OLDs.
- TODO. Send the migration notification email to the Dative users.
- TODO. Wait to see if any users want to opt out.
- TODO. Shut down DO Dative & its OLDs.
- TODO. Run the final data migration from DO to OLD.
- TODO. With the help of INT staff, configure dative.ca subdomains to resolve to INT
server.
- app.dative.ca => INT server 132.229.188.226 (Dative app & OLD API)
- www.dative.ca => INT server 132.229.188.226 (Dative website)
- www.old.dative.ca => INT server 132.229.188.226 (OLD website)
- onlinelinguisticdatabase.org is no longer needed.
- TODO. Confirm that production INT Dative is operating correctly.
- TODO. Email users to notify that Dative has been restored.
- TODO. Shut down the Digital Ocean server.
- TODO. Shut down the onlinelinguisticdatabase.org domain.
Problem: With the core technical challenges now overcome, we need a plan for completing the migration of the OLDs from DO to INT. This should cover communication with users to transfer of domain ownership and configuration, as needed.
A/C: