[07:00:23] Je.sse: thanks for sharing. As discussed in Slack, the team will have limited time so please let us know if specific questions/points you're unsure about on that review, and we're here if you run into problems when deploying [11:15:18] For the DC switch-over, it was suggested that maybe deploying the new debug.json could be done with SpiderPig, to simplify the process for people who normally aren't running Scap. That does introduce SpiderPig as a dependency, but it's at the tail end of the switch. Does servicesops have opinions? [13:20:37] slyngs: I'll let others reply on that optimization. Also I saw issues with parsoid during switchover dryrun test? [13:21:11] Yup, patch is already one and +1 by the always helpful claime [13:21:26] done, not one [13:21:45] great, thanks [13:22:06] I'll merge and re-test on Monday [13:23:39] And jasmine_ and I have live-test scheduled for next Wednesday, so I think we're doing good.... Unless you heard otherwise :-) [15:20:25] slyngs: using SpiderPig sounds reasonable to me! it definitely brings some additional dependencies on, but (1) they're optional (i.e., one can always switch to `scap backport` in a scenario where SpiderPig isn't appropriate) and (2) aren't part of the "critical" stretch of switchover operations (i.e., reordering debug.json is squarely a cleanup). [15:30:28] swfrench-wmf: Cool, I think I'll note down that SpiderPig will be the plan then