Jump to content

Talk:News/Toolforge Stretch deprecation

Rendered with Parsoid
From Wikitech
Latest comment: 2 years ago by Plenz in topic What about perl?

When is this going to happen for Toolforge?

Hi, when is this planned deprecation going to happen? Is there any indicative schedule at least (like Q4 2021)? --Dvorapa (talk) 16:16, 3 May 2021 (UTC) @Arturo Borrero Gonzalez: --Dvorapa (talk) 18:38, 3 May 2021 (UTC)Reply

Hi there! we don't have a timeline yet, but soon! We will announce the timeline basically as soon as we have time to plan it. Thanks for your interest :-) --Arturo Borrero Gonzalez (talk) 16:10, 4 May 2021 (UTC)Reply

Hi, thank you for your answer, hopefully it will be soon, 2021 is almost over :D Dvorapa (talk) 22:08, 9 December 2021 (UTC)Reply
@Arturo Borrero Gonzalez (forgot to mention you, sorry) Dvorapa (talk) 22:08, 9 December 2021 (UTC)Reply

What about perl?

I want to transfer my tool "osm4wiki" to Kubernetes. The instructions tell me:

  1. <type> is one of: php7.2, php5.6, python, python2, nodejs, golang, jdk8, ruby2, tcl

I wrote my tool in perl. What shall I do? --Plenz (talk) 12:10, 10 April 2022 (UTC)Reply

@Plenz, stick with grid engine, but migrate to the Buster grid. Your feedback on T214343: Create a Perl Docker image for use on the Toolforge Kubernetes cluster would be appreciated as well. -- BryanDavis (talk) 21:58, 10 April 2022 (UTC)Reply
Thank you very much, so I will try to migrate to Buster grid. That's all I can do. Actually, I only know Linux and Perl. I have no idea, what is a grid, a docker, a cluster etc.
<type> is one of: lighttpd, uwsgi-python, tomcat, generic, lighttpd-plain, nodejs, uwsgi-plain
How can I see under which option my program is running now? --Plenz (talk) 06:25, 11 April 2022 (UTC)Reply
webservice status is probably the easiest way to find out which backend and type a running webservice is using. For the osm4wiki tool this outputs "Your webservice of type lighttpd is running on backend gridengine".
You might be interested in creating a webservice template file in $HOME/service.template so that you can skip adding the --backend=gridengine and --release=buster flags to all of your webservice start commands in the future. -- BryanDavis (talk) 20:53, 11 April 2022 (UTC)Reply
Thank you very much for your hints. I found a service.template created on 02. April which contains gridengine, lighttpd, and buster.
So I simply stopped my webservice and started it again, and I hope I will not receive any more reminders about Stretch. --Plenz (talk) 10:05, 12 April 2022 (UTC)Reply