Change Details

Ideally to apply all at once: 1. Ugrade to jessie 2. Upgrade to latest mariadb package 3. enabling ssl 4. enabling ferm 5. enabling performance_schema 6. setting ROW-based replication on codfw some of these may not be feasible due to resources (reinstalling 150 machines short-term) or have hard blockers- ROW cannot be enabled on eqiad due to labs (maybe nowhere, if we are going to failover soon), performance schema has not been tested yet properly on the busiest servers and we cannot upgrade some API servers.

Ideally to apply all at once: 1. Ugrade to jessie 2. Upgrade to latest mariadb package 3. enabling ssl 4. enabling ferm 5. enabling performance_schema 6. setting ROW-based replication on codfw some of these may not be feasible due to resources (reinstalling 150 machines short-term) or have hard blockers- ROW cannot be enabled on eqiad due to labs (maybe nowhere, if we are going to failover soon), performance schema has not been tested yet properly on the busiest servers and we cannot upgrade some API servers. ROW based replication is not a hard blocker for the restart, although it has to be done very carefully.

Ideally to apply all at once: 1. Ugrade to jessie 2. Upgrade to latest mariadb package 3. enabling ssl 4. enabling ferm 5. enabling performance_schema 6. setting ROW-based replication on codfw some of these may not be feasible due to resources (reinstalling 150 machines short-term) or have hard blockers- ROW cannot be enabled on eqiad due to labs (maybe nowhere, if we are going to failover soon), performance schema has not been tested yet properly on the busiest servers and we cannot upgrade some API servers. ROW based replication is not a hard blocker for the restart, although it has to be done very carefully.