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!

Mentioned in SAL (#wikimedia-cloud) [2023-05-03T20:08:48Z] <wm-bot> <jeanfred> Trigger toolforge-jobs to repopulate database (T320160)

Mentioned in SAL (#wikimedia-cloud) [2023-05-03T20:09:07Z] <wm-bot> <jeanfred> Register nightly toolforge-jobs (T320160)

This is a reminder that the tool for which this ticket is created is still running on the Grid.
The grid is deprecated and all remaining tools need to migrate to Toolforge Kubernetes.

We've sent several emails to maintainers as we continue to make the move away from the Grid.
Many of the issues that have held users back from moving away from the Grid have been addressed in
the latest updates to Build Service. See: https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Changelog

You might find the following resources helpful in migrating your tool:

1. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service#Migrating_an_existing_tool
2. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service#Tutorials_for_popular_languages

Don't hesitate to reach out to us using this ticket or via any of our support channels

If you have already migrated this tool, kindly mark this ticket as 'resolved'

Thank you!

@JeanFred: Do you need help with this task? I don't see the code of wikiloves for years, but if it is still in python2 I can create a virtualenv in python2 in kubernetes. I have other two tools running python2 in kubernetes that also use Flask and pymysql and I can copy the version of each lib, that is the main difficulty when creating a python2 virtualenv, find the libraries versions that work in python2.

Unfortunately, we can not just copy the virtualenv used in grid engine because grid engine and kubernernetes python2 image use different debian versions and the virtualenv does not work in a different version.

In T320160#9523079, @Danilo wrote:

@JeanFred: Do you need help with this task? I don't see the code of wikiloves for years, but if it is still in python2 I can create a virtualenv in python2 in kubernetes. I have other two tools running python2 in kubernetes that also use Flask and pymysql and I can copy the version of each lib, that is the main difficulty when creating a python2 virtualenv, find the libraries versions that work in python2.

Unfortunately, we can not just copy the virtualenv used in grid engine because grid engine and kubernernetes python2 image use different debian versions and the virtualenv does not work in a different version.

Thanks for the offer! I actually did all that already last April (and forgot I did ^_^") − upgrade to Py3 (1b084c487a90 & 442fa0d0fdd2), and move to Kubernetes for both the webservice and the cron jobs.