CloudServices/Loop/MySQL

Loop migration to MySQL

The loop-server will be transistioning from using Redis for all its storage to using MySQL for the persistant data and Redis for the volatile data.

This is because it is far easier from an OPs point of view to operate a MySQL database for non-volatile data.

Tentative schedule

We need to have this landed on our prod stack before we hit firefox 35 release if possible. Depending if we can drop the data or not, the schedule would change.

In case the data can be dropped but not after a certain point in time, we need to define what this time is and it would mean that we deploy something early on:

• 28 of october: Code ready, we are ready for deployment;
• 29 of october: MySQL deployed on the staging stack, QA can verify;
• Once it's deployed to staging and verified, we can deploy to prod.
• Once this is done, we plan to have some feature-freeze time when we have time to investigate how MySQL is behaving and to any bugfix that's needed.

In case we need data migration, it means that we need to write the scripts to do this data migration, decide on how to deal with that and make it happen before the firefox 35 release.

Data migration

This schedule is tied to the fact we would not need to write data migration scripts. We need to find out if that's acceptable to drop the data we have for beta use, so we can start with a new empty database, and what is the last time we can drop the beta data.