Draft a timeline for the final shutdown of the ancient labsdb servers and announce it on labs-announce and the blog. There should be a page on wikitech created similar to the one that we did for the Precise deprecation project that the announcements can link to.
|Resolved||jcrespo||T140788 Labs databases rearchitecture (tracking)|
|Resolved||bd808||T166402 Program 7 Outcome 3: data services|
|Resolved||bd808||T142807 Migrate all users to new Wiki Replica cluster and decommission old hardware|
|Resolved||bd808||T175086 Create and announce timeline for shutting down labsdb100|
On wikitech we say that the user created databases could disappear at any time, but we try not to cause that unnecessarily. The blocker to decomm is giving reasonable warning of the decision made in T156869: Design a method for keeping user-created tables in sync across labsDBs for tools that are relying on co-located databases. I was initially in favor of never rebooting labsdb100, but in T168584#3569772 @jcrespo proposed a reasonable compromise of waiting until the basic announce of the new servers had been made and people had started to migrate. I do think that we should have puppet changes staged in gerrit to fail the *.labsdb hostnames over to the new servers before we try any reboot.
Drafted on wikitech -- https://wikitech.wikimedia.org/wiki/Wiki_Replica_c1_and_c3_shutdown
We need to pick dates/times for the reboots that work for roots from the cloud-services-team and for the DBA team so that we can handle routine issues that may come up from the reboots. @jcrespo, I'll have my people call your people. ;)