Page MenuHomePhabricator

Migrate video-cut-tool 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!

cc @Gopavasanth I don't think we have anything run on these projects (ditto for T320124: Migrate video-cut-tool-back-end from Toolforge GridEngine to Toolforge Kubernetes). We are currently hosted on a WMCS project.

Hi @komla, @Soda Oops I somehow missed this ticket, yes we are not running our tool in Tool Forge, please proceed to delete any VideoCutTool instances running on Toolforge. Our services are currently running in WMCS.

Aklapper reopened this task as Open.EditedDec 9 2023, 7:21 PM

In that case, please delete this tool and then resolve this ticket. Self-service tool deletion is available in Striker at . See
the announcement for more information. Thanks a lot! :)

Same might apply for T320124?

Hey @Aklapper, I already deleted these tools at toolforge many days back: let me know if I still need to take some actions.