Hello!
This is a friendly reminder for you to spare 5-10 minutes to leave
feedback[0] on the Toolhub taxonomy[1].
The period for providing feedback ends on August 21, 2022.
Toolhub[2] is a catalog of 1500+ tools used by a wide range of Wikimedia
contributors: editors, developers, patrollers, researchers, admins and more.
We want to make finding and categorizing these tools as easy as possible.
The taxonomy is at the heart of how tool search works, and your feedback
would help improve it.
Whether you are a current user of Toolhub or hearing about it for the first
time doesn't matter – your input is valuable and much appreciated either
way!
=== How To Provide Feedback ===
Use the discussion page[3] of the feedback page to provide your responses
to the questions.
You will find more details on the feedback page.
=== Implementation ===
At the end of the feedback round, the team will evaluate and work on the
necessary improvements.
This is expected to be completed by the end of September 2022.
[0]: https://meta.wikimedia.org/wiki/Toolhub/Data_model/Feedback
[1]: https://meta.wikimedia.org/wiki/Toolhub/Data_model#Taxonomy_v2
[2]: https://toolhub.wikimedia.org/
[3]: https://meta.wikimedia.org/wiki/Talk:Toolhub/Data_model/Feedback
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
Hi all,
We've added Node.js version 16 as an available image[0] to Toolforge
Kubernetes. Note that you might need to delete and re-create the
node_modules directory with the newer runtime for it to work properly.
[0]:
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Kubernetes#Container_ima…
-- Taavi Väänänen, on behalf of the entire Toolforge admin team
Hello!
The Toolhub project team wants your feedback[0] on the Toolhub taxonomy[1].
Toolhub[2] is a catalog of 1500+ tools used by a wide range of Wikimedia
contributors: editors, developers, patrollers, researchers, admins and more.
We want to make finding and categorizing these tools as easy as possible.
The taxonomy is at the heart of how tool search works, and your feedback
would help improve it.
Whether you are a current user of Toolhub or hearing about it for the first
time doesn't matter – your input is valuable and much appreciated either
way!
Please take 5-10 minutes to leave feedback.
=== How To Provide Feedback ===
Use the discussion page[3] of the feedback page to provide your responses
to the questions.
You will find more details on the feedback page.
The period for providing feedback ends on August 21, 2022.
=== Implementation ===
At the end of the feedback round, the team will evaluate and work on the
necessary improvements.
This is expected to be completed and announced by the end of September 2022.
[0]: https://meta.wikimedia.org/wiki/Toolhub/Data_model/Feedback
[1]: https://meta.wikimedia.org/wiki/Toolhub/Data_model#Taxonomy_v2
[2]: https://toolhub.wikimedia.org/
[3]: https://meta.wikimedia.org/wiki/Talk:Toolhub/Data_model/Feedback
Thanks
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
Rstudio has an interest in system users existing that make it difficult to
upgrade in PAWS, which doesn't have the same ideas about system users.
Currently the single user container is blocked from being upgraded by
Rstudio. There are some more Rstudio specific details in
https://phabricator.wikimedia.org/T302164
One simple solution would be to remove Rstudio. At the moment there is not
a clear path forward for keeping it as a part of PAWS.
Are there any opinions on this approach?
Thank you
--
*Vivian Rook (They/Them)*
Site Reliability Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello,
WMCS will be migrating the remaining Toolforge tools running on Stretch[0]
grid to Buster grid tomorrow(2nd June, 2022).
This has become necessary as the deadline for long term support(including
security updates) for Stretch comes to an end this month(June 2022).
=== What Do I Have To Do ===
Unless your tool starts failing on Buster grid, you don't have to do
anything.
If your tool can only work on Stretch grid, you can temporarily move it
back to Stretch grid with the following commands(while you work to port it
to Buster grid or kubernetes)
1. Webservice
Stop and Start the tool with *-release=stretch* flag
Example: *webservice stop*; *webservice start -release=stretch*
2. Jobs
Add *-release=stretch* to jsub command
Example: *jsub -release=stretch ...*
If you need further assistance, kindly reach out to us via our
communication channels[1]
[0]https://wikitech.wikimedia.org/wiki/News/Toolforge_Stretch_deprecation
[1]
https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Commun…
Thanks
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
On 2022-06-01 we will be upgrading kubernetes (from 1.20 to 1.21) on the
PAWS cluster. This should take no action on your part.
--
*Vivian Rook (They/Them)*
Site Reliability Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
We need to perform very brief maintenance on the servers that support
the DUMPS and TOOLS NFS mounts. That means that (among other things)
toolforge will be almost entirely broken for about 5 minutes. I expect a
graceful recovery, but in the worst case I may need to reboot toolforge
hosts (including the bastions), in which case some jobs will be interrupted.
This downtime will happen on Thursday, the 12th of May, at 15:00 UTC.
-Andrew + the WMCS team
Hi all,
We'll be upgrading the Toolforge Kubernetes cluster next Wednesday
(2022-05-11) starting at 16:00 UTC.
As with previous updates, the expected impact is that web services and
Toolforge Jobs Framework jobs may get restarted a couple of the times
over the course of the few hours it takes for us to upgrade the entire
cluster. Assuming your services are able to survive a restart, no action
should be needed on your part.
-- Taavi Väänänen (User:Majavah)
There are still dozens of VMs in cloud-vps running Debian Stretch. All
of these hosts will need to be deleted and replaced with VMs running
either Buster or Bullseye in the next few months. Beginning in May we
will begin to shut down Stretch instances.
Please check this page for your projects, and take whatever steps are
necessary to move off of Stretch:
https://os-deprecation.toolforge.org/
Don't hesitate to reach out for help on IRC or mailing list if you need
help with this migration. You may find Cinder volumes
(https://wikitech.wikimedia.org/wiki/Help:Adding_Disk_Space_to_Cloud_VPS_ins…)
especially useful for transferring data between VMs. Note that we do NOT
recommend in-place OS upgrades of VMs; it is almost always better to
start with a fresh host and transfer workloads over.
Details about the what and why for this process can be found here:
https://wikitech.wikimedia.org/wiki/News/Stretch_deprecation
Here is the remaining deprecation timeline:
May 1, 2022: All active Stretch VMs will be shut down (but not deleted)
by WMCS admins.
June 30, 2022: LTS support for Debian Stretch ends, all Stretch VMs will
be deleted by WMCS admins