My apologies if this ticket comes as a surprise to you. In order to ensure WMCS can provide a stable, secure and supported platform, it’s important we migrate away from GridEngine. I want to assure you that while it is WMCS’s intention to shutdown GridEngine as outlined in the blog post https://techblog.wikimedia.org/2022/03/14/toolforge-and-grid-engine/, a shutdown date for GridEngine has not yet been set. The goal of the migration is to migrate as many tools as possible onto kubernetes and ensure as smooth a transition as possible for everyone. Once the majority of tools have migrated, discussion on a shutdown date is more appropriate. See T314664: [infra] Decommission the Grid Engine infrastructure.

As noted in https://techblog.wikimedia.org/2022/03/16/toolforge-gridengine-debian-10-buster-migration/ some use cases are already supported by kubernetes and should be migrated. If your tool can migrate, please do plan a migration. Reach out if you need help or find you are blocked by missing features. Most of all, WMCS is here to support you.

However, it’s possible your tool needs a mixed runtime environment or some other features that aren't yet present in https://techblog.wikimedia.org/2022/03/18/toolforge-jobs-framework/. We’d love to hear of this or any other blocking issues so we can work with you once a migration path is ready. Thanks for your hard work as volunteers and help in this migration!

Mostly to remind myself, the source code is at https://github.com/toollabs/daily-image-l but there are uncommitted changes on the tool itself. It's still in Python 2, but porting it should be trivial. All of the use of mwparserfromhell can be improved by using Parsoid HTML, so it's probably worth porting to Rust too.

I've moved the Git repo to Wikimedia GitLab; the main technical change we need to make for this is to switch to using SMTP, I've done so in https://gitlab.wikimedia.org/toolforge-repos/potd/-/merge_requests/1, pending a few questions I left in -cloud (and also more testing of the HTML template...)

I think we're probably ready to go on this. I flipped the list configuration to allow HTML mails to go through untouched (i.e. not converted to plaintext). FYI @Platonides that I'm changing the script to send over SMTP, run using toolforge-jobs and send HTML email. :)

legoktm merged https://gitlab.wikimedia.org/toolforge-repos/potd/-/merge_requests/1

Send an HTML email over SMTP

I've commented out the crontab and:

tools.potd@tools-sgebastion-10:~/potd$ toolforge jobs list
Job name:    Job type:            Status:
-----------  -------------------  --------------------------
send         schedule: 0 2 * * *  Waiting for scheduled time

Will see how it goes tomorrow.

Manually fixed a few issues and sent out today's mail, will see that it works tomorrow before closing it.

Thanks, @Legoktm
Can this be closed now?