Page MenuHomePhabricator

Migrate pywikibot from Toolforge GridEngine to Toolforge Kubernetes
Open, Needs TriagePublic


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: Toolforge: Decomission 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!

@Dvorapa: Is this assignment intentionally?

Multichill added a subscriber: Dvorapa.

@Dvorapa: Is this assignment intentionally?

As mentioned in T314664: I object to some of these subtasks being assigned to me as this is against : "Only manually assign a task to someone if they have given their prior agreement. It is up to developers (or their product managers) what they plan to work on." I asked in the Cloud Telegram channel @komla to unassign all these tasks.

That was just before the weekend so I guess @komla hasn't done something yet.

Thanks @Multichill. Anyway, I check periodically every 3-6 months if the transition is possible, but there are still some issues with K8s and it waits for them to be resolved.

If I remember correctly, last time I tried there was git not working properly in K8s, which is a blocker for both Pywikibot and DvorapaBot

Last time in May 7th. Result:

toolforge-bullseye-standalone based pod
line 6: git: command not found

toolforge-bullseye-sssd based pod
line 6: git: error: cannot run ssh: No such file or directory
line 6: git: fatal: unable to fork

Also there is gzip missing (Pywikibot needs that as well)