db1095 is still in multi-source format, hosting s1, s3, s5 and s8. We may purchase soon an extra host to handle the growing capacity of the different sections. This is the main standalone goal for #DBAs for 2017-2018 Q4 (there could be other more important tasks and goals, but this should have no hard external dependencies, other than hardware provisioning.
- Design a strategy (do we setup a db1095-equivalent to prevent downtime? Distribution of sections?)
- Define the purchases needed for the new host(s) and request them (T189590) [Note the decision seems firm, but the purchases have not yet gone through)
- Setup new hardware needed. If it doesn't arrive on time, maybe use one of the new 8 core host as a temporary measure
- Fix sanitarium_multiinstance puppetization https://gerrit.wikimedia.org/r/#/c/425087/
- Copy data needed for the service
- eqiad
- db1124
- db1125
- codfw
- db2094
- db2095
- eqiad
- Change codfw sanitariums (db2094 and db2095) to replicate from codfw hosts instead from eqiad ones.
- db2094
- s1
- s3
- s5
- s8
- db2095
- s2
- s4
- s6
- s7
- db2094
- Switchover replicas (labsdb hosts) to use the new hosts
- labsdb1009
- labsdb1010
- labsdb1011
Follow up / clean up tasks:
Clean up sanitarium_multisource related code T196376
Productionize old/temporary eqiad sanitariums T196527
Implement a script to facilitate sanitarium failovers between DCs T196367