Earlier this year, WMCS initiated the process to migrate tools off the
We also published a series of blog posts explaining further the reasoning
behind this action
We encouraged maintainers to move to Kubernetes if they could but also made
available Debian Buster GridEngine for those tools who were blocked or
otherwise unable to migrate to Kubernetes at that time.
We are aware that not all workloads can easily move from the grid to
For some of the current grid workflows, there may be no 1:1 functionality
match on Kubernetes.
Work is underway to address most of these issues
We’re putting together a use case continuity table showing GridEngine
workloads and their equivalent Kubernetes workloads
[image: case continuity.PNG]
To help track the specific migration work, we created a Phabricator
ticket(project tag: grid-engine-to-k8s-migration) for each tool that is
currently running on GridEngine. With a ticket for each tool on GridEngine,
we hope to collect specific blocking issues and have the team work on
We encourage maintainers to reach out if you need help or find you are
blocked by missing features.
We noticed, after receiving notifications for these tickets, some of you
wondered whether the grid is being shut down immediately.
This is not the case. We will work with tool maintainers to ensure all
tools safely move off the grid(or are safely shutdown), only then will we
start looking at decommissioning the grid.
Apologies to those who felt spammed by the ticket creation process and got
worried about the future of their projects. We should have communicated
better around this process.
=== Way Forward ===
The working draft for GridEngine plans and timeline can be found here
If you need further clarifications, reach out to us on the ticket for your
specific tool on Phabricator or reach out via any of our communication
Seyram Komla Sapaty
Wikimedia Cloud Services