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 https://techblog.wikimedia.org/2022/03/14/toolforge-and-grid-engine/, 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 https://techblog.wikimedia.org/2022/03/16/toolforge-gridengine-debian-10-buster-migration/ 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 https://techblog.wikimedia.org/2022/03/18/toolforge-jobs-framework/. 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!

Adding @Nemo_bis and @8ohit.dua per https://toolsadmin.wikimedia.org/tools/id/bub

@Samwilson: You may want to remove yourself at https://toolsadmin.wikimedia.org/tools/id/bub if you are not actually a maintainer

This webservice seems to be using lighttpd to run a Flask app as an fcgi process. It may be relatively simple to migrate this to using the Python3.9 container and modern standard for running Python WSGI apps. See https://wikitech.wikimedia.org/wiki/Help:Toolforge/My_first_Flask_OAuth_tool for a concrete example of the convention over configuration approach to running a Flask app.

https://github.com/rohit-dua/BUB

You may want to remove yourself at https://toolsadmin.wikimedia.org/tools/id/bub if you are not actually a maintainer

Good point; done.

@Samwilson Is bub even running/actively maintained, aren't we focussing on bub2 ?

@Soda it shows it's running. If it is no longer in use, kindly disable it and mark this as closed.

In T319610#9400673, @komla wrote:

@Soda it shows it's running. If it is no longer in use, kindly disable it and mark this as closed.

I don't have access to the tool, but https://bub.toolforge.org shows a 503 error indicating that it is not currently not really functional. If I can get access, I should be able to look at it sometime next week :)

In T319610#9401717, @Soda wrote:

In T319610#9400673, @komla wrote:

@Soda it shows it's running. If it is no longer in use, kindly disable it and mark this as closed.

I don't have access to the tool, but https://bub.toolforge.org shows a 503 error indicating that it is not currently not really functional. If I can get access, I should be able to look at it sometime next week :)

It shows it is running here

In T319610#9401869, @komla wrote:

In T319610#9401717, @Soda wrote:

In T319610#9400673, @komla wrote:

@Soda it shows it's running. If it is no longer in use, kindly disable it and mark this as closed.

I don't have access to the tool, but https://bub.toolforge.org shows a 503 error indicating that it is not currently not really functional. If I can get access, I should be able to look at it sometime next week :)

It shows it is running here

Maybe @Nemo_bis can provide access (I think Rohit has left the project) ?

From the community's POV this tool is not used since it is not maintained and has mostly been superseded by https://bub2.toolforge.org

Mentioned in SAL (#wikimedia-cloud) [2023-12-13T11:43:57Z] <taavi> disabled tool T319610