Page MenuHomePhabricator

Migrate wikitasks from Toolforge GridEngine to Toolforge Kubernetes
Closed, ResolvedPublic


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!

My tools are broken for a long time because no one from WMF want to solve problems with their hosting: T295220, T292289.
If you can check and confirm that my programs will work with new system, I may try to migrate.
However, I expect that new system will not bring better level of support (because if depends on humans), so I have doubts about migration even if programs will work.

T292289 is resolved; if there is still some issue please create a new task. Thanks a lot!

is resolved; if there is still some issue please create a new task. Thanks a lot!

That's the quality of support I was talking about.

@Vort: Well, I tried to point out that it's more likely that issues get resolved together, the more atomic and well-described the problem is. However, if you think that the problem initially described in T292289 is not resolved, then please reopen that task so it appears on the list of unresolved tasks. Thanks.

@Vort can we hear from you as to whether T292289 resolves your issue

@Vort can we hear from you as to whether T292289 resolves your issue

No. I made T295220 instead and there was no solution as well.

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:

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


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!

This is a reminder

No need for reminder until T295220 is fixed. Am I talking to bots here?

I started conversion process, but it will take several days to set up everything correctly and check if tools work stable enough.
My tools are launched once a day, so now I will wait.

Run, which executed this night, was successful.
So if nothing wrong happens in following days, this task will be closed.