- Cloud - lists.wikimedia.org

High replag on s1/enwiki wiki replicas
by Kunal Mehta 10 Jun '22

10 Jun '22

Hi, Because of schema changes happening in production, the s1/enwiki wiki replica is currently behind by ~40 hours, so tools and bots relying on it will have outdated data. The expectation is that it should recover by Monday. You can look up the current replag using <https://replag.toolforge.org/> and discussion about the issue itself is at <https://phabricator.wikimedia.org/T310325>. -- Legoktm

1 0

Old DB schemata on //tools-info.toolforge.org/schemas.php
by Andre Klapper 05 Jun '22

05 Jun '22

Hola, https://tools-info.toolforge.org/schemas.php?schema=enwiki says last updated 67 months ago. Is there something more recent to link to? (Or did we really not change the DB scheme since then which I doubt?) https://wikitech.wikimedia.org/wiki/Help:MySQL_queries#Database_layout links to that page if anybody wonders how I ended up here. PS: Oh, and bonus points if someone knows where the code for https://tools-info.toolforge.org/schemas.php itself is located. (Or how I could have found out myself because there are no hints on https://admin.toolforge.org/tools ). Because dead links in sidebar. Thank you!, andre -- Andre Klapper (he/him) | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/

2 1

Removal of MobileFrontend MobileView API
by Jon Robson 03 Jun '22

03 Jun '22

Yesterday, the MobileView Action API was removed from all Wikimedia production servers [1]. The API was originally built to service our apps but over time that has been replaced with the Page Content Service [2]. The original service was not being maintained, and usage was very low. If you were using the MobileView API we urge you to check this API out as it is a more powerful, better cached alternative. We marked the API as hard deprecated in December 2019 [3], after which it was marked in ApiSandbox and in the response as deprecated, and support has been dwindling since then, for example, the noimages parameter was dropped in September 2020 [4]. In March 2022 we removed the remaining production blocker for removing the code: language variant support [5]. The Page content service was prreviously using the mobile view API for language variant views but has now been rewired to use the better supported core action=parse API. If you need to support language variant views and previously couldn't because of the lack of support in the page content service this should no longer be an obstacle.. Since April 2022 users of the API would have been seeing an inline banning warning them of the upcoming breakage [6]. We got no feedback from these banners so were comfortable with pushing forward. Impact on user scripts was judged as low [7] with only 14 scripts impacted so this has not been announced on tech news. If you are impacted by this change, I apologise that previous communications have failed you and I'd love to hear from you about how we could have done this deprecation better. If I can support you in any way in making sure your apps/gadgets/scripts are working again please feel free to reply to this email either privately or publicly or to raise a topic on the MobileFrontend talk page [8]. Finally, thanks to the engineers who helped make this deprecation possible. Jon [1] https://phabricator.wikimedia.org/T186627 [2] https://www.mediawiki.org/wiki/Page_Content_Service [3] https://phabricator.wikimedia.org/T210808 [4] https://phabricator.wikimedia.org/T262580, [5] https://phabricator.wikimedia.org/T236733 [6] https://phabricator.wikimedia.org/T286836 [7] https://global-search.toolforge.org/?q=%5B%27%22%5C%3D%5Dmobileview&regex=1… [8] https://www.mediawiki.org/wiki/Extension_talk:MobileFrontend?tableofcontent…

1 0

[Cloud-announce] [NOTICE] Migrating Toolforge Tools On Stretch Grid To Buster Grid
by Seyram Komla Sapaty 01 Jun '22

01 Jun '22

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 _______________________________________________ Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…

1 0

[Reminder] Your Hackathon feedback is wanted (until May 29th)
by Andre Klapper 01 Jun '22

01 Jun '22

Hi, this is a friendly reminder that we would love to hear from you about your experience at last weekend's Hackathon. Please fill in the survey until Sunday, May 29th and help us improve. See the links below. Thanks a lot in advance! andre -------- Quoted Message -------- From: Haley Lepp Date: Sun, 22 May 2022 11:13:39 -0700 On behalf of the 2022 Wikimedia Hackathon Committee, we would like to thank you for coming to the Wikimedia Hackathon! Please consider giving us feedback on the Hackathon and your suggestions for improvement. There are two ways to give feedback: 1. Fill out the Wikimedia Hackathon Survey <https://wikimedia.qualtrics.com/jfe/form/SV_cGbCKj4xyP0H3wi>. For more information on privacy and data-handling, see the survey privacy statement <https://foundation.wikimedia.org/wiki/Wikimedia_Hackathon_Post-Event_Survey… >. The survey will remain open until May 29, 2022. 2. If you would like to share feedback but do not wish to take the Qualtrics survey, you can leave feedback on the Etherpad <https://etherpad.wikimedia.org/p/Wikimedia_Hackathon_2022_Feedback >. Finally, check out the badges <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/How_to#Joining_a_se… > the committee made. You can put them on your userpages to show your participation. Thank you again for joining us! It was so much fun to meet everyone and hack together. See you at the Wikimania Hackathon in August! Haley, on behalf of the 2022 Wikimedia Hackathon Team -- Andre Klapper (he/him) | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/ _______________________________________________ Wikitech-ambassadors mailing list -- wikitech-ambassadors(a)lists.wikimedia.org To unsubscribe send an email to wikitech-ambassadors-leave(a)lists.wikimedia.org

2 1

Custom puppet class?
by Roy Smith 31 May '22

31 May '22

I want to set up a custom rsyslog config on my spi-tools VPS instance. I know what I want to end up with, but I'm trying to get it puppetized. It's not really clear what I need to do. Do I really need to set up my own standalone puppetmaster <https://wikitech.wikimedia.org/wiki/Help:Standalone_puppetmaster>? That seems like overkill.

2 1

Connecting from Toolforge to VPS?
by Roy Smith 26 May '22

26 May '22

I want to send data from a process running on toolforge to a VPS host. I tried the obvious: On the VPS host (puppet-test.spi-tools.eqiad1.wikimedia.cloud): > $ nc -4 -l -p 23001 On tools-sgebastion-11: > echo foo | nc -v -4 puppet-test.spi-tools.eqiad1.wikimedia.cloud 23001 > nc: connect to puppet-test.spi-tools.eqiad1.wikimedia.cloud port 23001 (tcp) failed: Connection timed out I'm assuming I need to configure a security group in horizon to allow ingress on that port, is that correct?

2 3

[Cloud-announce] Upgrading kubernetes on PAWS 2022-06-01
by Vivian Rook 25 May '22

25 May '22

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/> _______________________________________________ Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…

1 0

Hackathon thank you and feedback!
by Haley Lepp 22 May '22

22 May '22

Hi Everyone, On behalf of the 2022 Wikimedia Hackathon Committee, we would like to thank you for coming to the Wikimedia Hackathon! Please consider giving us feedback on the Hackathon and your suggestions for improvement. There are two ways to give feedback: 1. Fill out the Wikimedia Hackathon Survey < https://wikimedia.qualtrics.com/jfe/form/SV_cGbCKj4xyP0H3wi >. For more information on privacy and data-handling, see the survey privacy statement <https://foundation.wikimedia.org/wiki/Wikimedia_Hackathon_Post-Event_Survey…>. The survey will remain open until May 29, 2022. 2. If you would like to share feedback but do not wish to take the Qualtrics survey, you can leave feedback on the Etherpad <https://etherpad.wikimedia.org/p/Wikimedia_Hackathon_2022_Feedback>. Finally, check out the badges <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/How_to#Joining_a_se…> the committee made. You can put them on your userpages to show your participation. Thank you again for joining us! It was so much fun to meet everyone and hack together. See you at the Wikimania Hackathon in August! Haley, on behalf of the 2022 Wikimedia Hackathon Team

1 0

Wikimedia Hackathon May 20-22: Info you need for tomorrow’s event
by Melinda Seckington 20 May '22

20 May '22

Hi everyone, We hope you’re ready for this three-day event, because the event starts in 10 hours! The main hackathon will take place over the weekend (Friday through Sunday), with two sets of core hours for sessions, social events, and hacking. These core hours are: - 3:00 <https://iw.toolforge.org/zonestamp/1653102000> - 6:00 <https://iw.toolforge.org/zonestamp/1653112800>UTC (Note: this is tonight for some time zones!) - 15:00 <https://iw.toolforge.org/zonestamp/1653145200>- 19:0 <https://iw.toolforge.org/zonestamp/1653159600>0 UTC We’re expecting the virtual space to be the busiest at these times. Outside of those core hours, you’re welcome to stay online to hack on projects, collaborate with others, or hang out in the virtual space. The goal with this schedule is to allow time for breaks and to accommodate as many time zones as possible. You are not expected to attend both sets of core hours - choose whichever hours work for you! For more info, see the Schedule <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Schedule>. When will the event start? The opening ceremony will happen twice - once at 3:00 UTC, and once at 15:00 UTC on May 20. Find the links on the schedule <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Schedule>! How can I join the virtual space? We’ll be using an online game-style space for the Hackathon. The links will be published shortly before the event on the hackathon page on MediaWiki.org <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022>. There will be rooms for hacking and for sessions. Feel free to explore the virtual space and join any room - they’re open for everyone! What happens if I need help? Once the platform goes live, you will be able to find a Help Desk where you can ask questions, report any incidents, or just consult useful information about the event. There are also discussion channels <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Discussions> that you can participate in. How can I work on a project? If you have an idea, you will be able to add your own projects <https://phabricator.wikimedia.org/project/board/5802/> on Phabricator. If you don’t know yet what to work on, see what projects <https://phabricator.wikimedia.org/project/view/5802/> others will be working on. You might find a project to join or get inspiration for your own idea! If you have any other questions, please check our FAQ <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/FAQ> section or leave a comment on the talk page. See you soon! Melinda, for the Hackathon Committee -- Melinda Seckington Developer Advocacy Manager Wikimedia Foundation <https://wikimediafoundation.org/>

1 1

2024

2023

2022

2021

2020

2019

2018

2017

Cloud