Joshua Hoblitt what is the status of this ticket?

SQuaSH is using mysql and mysqlclient in development and I think it is a good time to remove the dependency on MySQL-python for deployment, thus Frossie Economou I am moving this ticket from the backlog to the SQuaSH update epic.

This issue also relates to DM-8414 which implements the JSON field type in the database, it requires django-mysql and mysqlclient. That was merged recently to master.

In development settings we have now
https://github.com/lsst-sqre/qa-dashboard/blob/master/squash/squash/settings/dev.py

we also need django-mysql in production because of the JSON field.

More info here:
http://sqr-009.lsst.io/en/latest/#setting-up-the-database

A migration will be necessary to acommodate the the scalar measurements stored in measurements.value to the new JSON field.

So it is worth to test that bit in production in advance, before another (major) update which is the goal of this epic.

We still need to figure out how to run a version of uwsgi linked against py35 as a service. We may need to abandon the epel packaged version along with the emperor and write our own systemd service unit.

The issue with uwsgi was resolved by moving towards building our own version of source so that the python plugin could be linked against the rh-python35 SCL.

A manual test was do against `69711e5ac0927089d462910d6438742bead64f89` and a few issues with resource ordering were sorted out. This is ready to ship.