Hi all -

Following up on Reuven's message on Monday, 5th of May.

As of today, maintenance scripts can no longer run on the mwmaint hosts, in advance of their decommissioning. This follows the earlier "hard" deprecation that began on the 12th of May.

While the majority of maintenance script use cases have moved to Kubernetes, some are not yet supported (e.g., sql.php [0]) or involve additional complexity in that environment (e.g., large output files [1]).

For these cases, as Reuven noted in his message on the 5th of May, users are directed to the active deployment host (i.e., available at deployment.eqiad.wmnet) to run their scripts on an interim basis.

This interim solution will be phased out as support lands for the remaining use cases.

Many thanks,
Scott French
Service Ops SRE

[0] https://wikitech.wikimedia.org/wiki/Maintenance_scripts#Not_yet_supported
[1] https://wikitech.wikimedia.org/wiki/Maintenance_scripts#Output_to_a_file

On Tue, May 6, 2025 at 1:40 PM Brooke Vibber <bvibber@wikimedia.org> wrote:
On Tue, May 6, 2025 at 1:17 PM Reuven Lazarus <rlazarus@wikimedia.org> wrote:
Foreachwiki and friends are available in the Kubernetes container now, with a flag on the way to make it easy to invoke them via mwscript-k8s. (https://phabricator.wikimedia.org/T378479) We've also resolved the resource-consumption issues with the shell loop approach, so that option is viable too.

Woohoo! Thanks! :D
 
(That is, simultaneously launching that number of jobs will no longer overload the Kubernetes infrastructure itself; of course it's still possible to use up the available compute resources, and it's also possible -- as ever -- for aggressive maintenance scripts to overload shared resources like the databases. But it's back on the table; consider it remediated from the temporary guidance "don't do this, it's dangerous" to the indefinite guidance "this is powerful, do it cautiously.")

*nods seriously*
 
Interactive scripts like eval.php can be used with mwscript-k8s in --attach mode (which forwards stdin and stdout to your terminal). (https://wikitech.wikimedia.org/wiki/Maintenance_scripts#Input_on_stdin) Separately, note there's also mw-debug-repl to get a shell in a mw-debug pod, rather than a mw-script one. (https://wikitech.wikimedia.org/wiki/MediaWiki_On_Kubernetes#MediaWiki_REPL)

*success kid meme* yay! Eval lives. :D
 
That said, mwscript-k8s can't support {my,}sql.php specifically, because we don't have a mysql client in the MW image and shouldn't add one. For now, you can run `sql` from the deploy hosts instead of the mwmaint hosts. The long-term replacement probably won't be a maintenance script at all but a dbconfig-aware wrapper around a local mysql client. (https://phabricator.wikimedia.org/T375910)

Awesome, that works fine for my needs.

Thanks!

-- brooke
_______________________________________________
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/