Page MenuHomePhabricator

Migrate cewbot from Toolforge GridEngine to Toolforge Kubernetes
Closed, DeclinedPublic


Kindly migrate your tool( from Toolforge GridEngine to Toolforge Kubernetes.

Toolforge GridEngine is getting deprecated.

Please note that a volunteer may perform this migration if this has not been done after some time.
If you have already migrated this tool, kindly mark this as resolved.

If you would rather shut down this tool, kindly do so and mark this as resolved.

Useful Resources:
Migrating Jobs from GridEngine to Kubernetes
Migrating Web Services from GridEngine to Kubernetes

Event Timeline

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, 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 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 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!

@nskaggs @komla May I increase the number of Kubernetes pods running at the same time? Actually, the old 16 is not enough, so I split it into 4+1 tools...

@nskaggs @komla @Aklapper And I also need to use more memory, maybe 16*8GiB per tool... It would be nice to have the latest node image versions (e.g. node20, node21) and keep up with the times.

@nskaggs @komla @Aklapper And I also need to use more memory, maybe 16*8GiB per tool... It would be nice to have the latest node image versions (e.g. node20, node21) and keep up with the times.

Feel free to open a task with what you need following Mention this task and if the need is permanent or temporary as part of the move. Thanks!

@Kanashimi Hi! Were you able to request the quota you needed? Do you need anything else?

This tool has been disabled from running on the Grid.

If you are the maintainer and you want this re-enabled so that you can work on migrating it off the grid, please reach out to the cloud admins on the mailing list(

However, please note that according to the timeline shared, on the 14th of March 2024, the grid infrastructure will be shut down.

taavi subscribed.

The grid engine has been shut down, so I'm closing any remaining migration tasks as Declined. If you're still planning to migrate this tool, please re-open this task and add one or more active project tags to it. (If you need a project tag for your tool, those can be created via the Toolforge admin console.)