Page MenuHomePhabricator

Migrate steve-adder 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

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

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!

There's no container image that contains wget... guess I can use curl instead.

Can we say this is resolved?

@komla Who is "we" and who are you addressing?

Legoktm claimed this task.

Probably me - I had merged the changes in Git but not yet deployed them. But now it's resolved!

tools.steve-adder@tools-sgebastion-10:~$ crontab -l
no crontab for tools.steve-adder
tools.steve-adder@tools-sgebastion-10:~$ toolforge jobs list
Job name:    Job type:         Status:
-----------  ----------------  --------------------------
download     schedule: @daily  Waiting for scheduled time seems to have gone down, I'd guess as a result of this task. :)

@komla Who is "we" and who are you addressing?

Yes, I was referring to Legoktm seems to have gone down, I'd guess as a result of this task. :)

Oops sorry, I messed up the deployment, its back now. And I will add health checks to automatically complain...