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!

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'
To do this, click on the 'Add Action' dropdown above the comment text box, select 'Change Status', then 'Resolved'.
Click 'Submit'

Thank you!

I'm testing the migration now, some things need fixing but I think I can handle it; let's hope things keep going well and I'll report again (and maybe close the task) tomorrow. Thanks to @taavi and @bd808 for the help in IRC.

Hi @-jem-! Were you able to migrate? I still see one webservice running on the grid, let me know if you are finding any issues or want any guidance. If you share the url to your code (gitlab/github/...) I might be able to help with the boilerplate if any (quite limited resources though).

Hi, @dcaro, thanks for your interest. I'm afraid things got complicated; I asked in the IRC channel for guidance in December and I still have to find time to figure things out in the next days. Basically, one of my tools under jembot uses ssh and pdflatex calls under php to generate dynamic png files, and those calls/binaries aren't available in the kubernetes environment, so probably I will have to do that task elsewhere/elsehow. Recently, I have completed the Spellcheck migration (T320053), which was more urgent. I will report as soon as possible. Thanks again...

No problem :)

If you need specific packages installed that are not there in the pre-built images, you can use the build service image (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service#Installing_Apt_packages), that would allow you to install both ssh and pdflatex for any php project (see https://gitlab.wikimedia.org/toolforge-repos/sample-php-buildpack-app for php specific stuff).

Let me know if you find any issues/bugs/etc.

Yes, I was told about that possibility in IRC, but if I remember well, it would require using Gitlab for the code and a deep change in my work dynamics, which I can't afford currently... I have my own code for source publishing and connections with code in external servers, and I prefer not to change things while they are working, or to change them as little as possible. Anyway, thanks again; I hope I can get through this and report by the end of this week.