Still on precise, migrate to jessie. This would also involve a postgresql update from 9.1 to 9.4
|operations/puppet : production||Change osm master to be labsdb1007 on configuration|
|operations/puppet : production||tools: Make DNS point to labsdb1004 and not 1005|
|operations/puppet : production||labsdb-toolsdb: Cleaning up tls certificates|
|Resolved||Dzahn||T123525 reduce amount of remaining Ubuntu 12.04 (precise) systems in production|
|Resolved||jcrespo||T123731 Migrate labsdb1005/1006/1007 to jessie|
|Resolved||Marostegui||T157358 labsdb1005 (mysql) maintenance for reimage|
|Duplicate||None||T157359 labsdb1006/1007 (postgresql) maintenance|
There is indeed a replacement for labsdb100 about to arrive. However, there are no short-term plans for these, as they have lower impact.
labsdb1005.eqiad.wmnet has already a jessie slave- so it should be able to have scheduled downtime soon.
Not much is happening for the postgres slaves.
@yuvipanda I think the asks here if you could think on it are:
- Who do we let know toolsdb is going down
- What are the impacts of toolsdb going down (just generally)
-1- assume labs-announce is fine
-2- I'm not sure? Are things using toolsdb going to be ok? Assuming things reconnect on failure (probably a bad assumption) it's a small window of issue but looking for input. There may be little we can do to shore that up other than verbose announcement.
I wonder if it'll be better to do this next quarter. We've already done a few bits of pretty disruptive maintenance, and have one coming up next week.
If not next quarter, how about 2nd week of December?
I wonder if it'll be better to do this next quarter.
I am ok with next quarter- let's set a time. I have workarounded the 5.5 support on puppet, so this is no longer a blocker.
Just one comment- note that in theory this maintenance is not disruptive.
Dzhan- the "reinstall as jessie" part is done, but the setup of the passive replica is not 100% complete. It will take one commit to fix it and some extra time for reimport- but there is not way to revert it anymore. I just got distracted with more important ongoing issues.