- Cloud - lists.wikimedia.org

Issue with jitsi - Anyone knows why?
by Amir Sarabadani 27 Feb '21

27 Feb '21

Hello, I usually wouldn't bother people with my issues but I'm sorta desperate here. This is about https://meet.wmcloud.org. WM Cloud jitsi instance. It's on a bigram VM and on docker <https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker>. Users report that when using this "a session with three people today and it was rather poor. Bad grainy video from my side even though I have 100 Mbps both ways. After about 15 minutes the session froze and the other two dropped out." or "we were 4 persons and it was very unstable (no screen sharing). people's connection got lost, so they could often still hear but could not participate in the call anymore." and you can reproduce the issue too if you stay long enough in a meeting with another connection (your phone for example). I can't find any reason why this is happening. I wrote some of my investigations here <https://phabricator.wikimedia.org/T268393> but we checked the cloud's infra. CPU, memory, etc. all look fine as well as the network throughput. It doesn't happen with a new VM but quickly (after one meeting) builds up to have the same issues again. I added a regular restart of the docker containers (it even destroys them and recreates them again, also the docker service itself gets restarted) but nothing changes (maybe I should add a restart of the network manager too?). I assume the iptables being busy because of docker can contribute to the issue but not this much. I'm running out of ideas. If anyone has worked with such setup and feels comfortable debugging this, let me know and I give permission to check the VM. Thank you -- Amir (he/him)

1 0

Code of conduct committee call for new members
by Amir Sarabadani 26 Feb '21

26 Feb '21

Hello all, It's coming close to time for annual appointments of community members to serve on the Code of Conduct (CoC) committee. The Code of Conduct Committee is a team of five trusted individuals plus five auxiliary members with diverse affiliations responsible for general enforcement of the Code of conduct for Wikimedia technical spaces. Committee members are in charge of processing complaints, discussing with the parties affected, agreeing on resolutions, and following up on their enforcement. For more on their duties and roles, see https://www.mediawiki.org/wiki/Code_of_Conduct/Committee This is a call for community members interested in volunteering for appointment to this committee. Volunteers serving in this role should be experienced Wikimedians or have had experience serving in a similar position before. The current committee is doing the selection and will research and discuss candidates. Six weeks before the beginning of the next Committee term, meaning 9 April 2021, they will publish their candidate slate (a list of candidates) on-wiki. The community can provide feedback on these candidates, via private email to the group choosing the next Committee. The feedback period will be two weeks. The current Committee will then either finalize the slate, or update the candidate slate in response to concerns raised. If the candidate slate changes, there will be another two week feedback period covering the newly proposed members. After the selections are finalized, there will be a training period, after which the new Committee is appointed. The current Committee continues to serve until the feedback, selection, and training process is complete. If you are interested in serving on this committee or like to nominate a candidate, please write an email to techconductcandidates AT wikimedia.org with details of your experience on the projects, your thoughts on the code of conduct and the committee and what you hope to bring to the role and whether you have a preference in being auxiliary or constant member of the committee. The committee consists of five members plus five auxiliary members and they will serve for a year; all applications are appreciated and will be carefully considered. The deadline for applications is the end of day on 26 March 2021. Please feel free to pass this invitation along to any users who you think may be qualified and interested. Best, Amir on behalf of the CoC committee

1 0

Network change for VMs contacting NFS dumps
by Arturo Borrero Gonzalez 23 Feb '21

23 Feb '21

Hello, today 2021-02-23 in about ~30 minutes (16:00 UTC) we will change how virtual machine instances running in Cloud VPS contact NFS dump servers [0]. There is no action required on your side. We anticipate little to no impact as a result of the network changes. But in case you notice something is not properly working with dumps NFS in Cloud VPS (or Toolforge) please contact us [1] as soon as possible. The relevant phabricator ticket [2] is T272397. regards. [0] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Dumps [1] https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_Introduction#Commun… [2] https://phabricator.wikimedia.org/T272397 -- Arturo Borrero Gonzalez SRE / Wikimedia Cloud Services Wikimedia Foundation

1 0

Removing myself from Horizon projects
by Željko Filipin 23 Feb '21

23 Feb '21

Hi, I'm offboarding from my previous team[0]. As part of that process, I've noticed I'm a member in a few Horizon projects: - bastion - mediawiki-vagrant - search - tools I don't think I've ever used Horizon. For project security reasons, I would like to remove myself from all projects, since I'm not using them. I've failed to figure out how to do that. I've looked at Horizon[1] and Wikitech[2]. Can somebody point me in the right direction? Thanks, Željko -- 0: https://phabricator.wikimedia.org/T267313 1: https://horizon.wikimedia.org 2: https://wikitech.wikimedia.org/wiki/Help:Horizon_FAQ

3 4

tmpfs for tool account?
by Roy Smith 20 Feb '21

20 Feb '21

My personal account has an entry in /run/user: drwx------ 4 roysmith wikidev 80 Jan 14 14:04 /run/user/17980 but not my tool account. Is it possible to set one up for tool accounts?

1 1

X_REQUEST_ID?
by Roy Smith 17 Feb '21

17 Feb '21

I'm running a django app under toolforge. I see there's already a X_REQUEST_ID: e9ec1899b09244939d22c2387db3b75a header in the incoming request. That's totally cool, but I don't see it documented in the toolforge docs. is that something the toolforge infrastructure guarantees will be there?

2 2

Starting the Wikimedia Rust developers user group
by Kunal Mehta 12 Feb '21

12 Feb '21

Hi everyone, We are starting a user group for people interested in spreading the adoption of the Rust programming language[1] in the Wikimedia movement. If you're not familiar with it, Rust is a systems programming language that aims to provide the trifecta of safety, concurrency and speed. It's very fun to use (rated #1 favorite language in Stack Overflow's survey 5 years and counting) and has fantastic tooling. https://meta.wikimedia.org/wiki/Wikimedia_Rust_developers_user_group If you're already using Rust or looking to get started - please sign up! The current proposed goals of the user group are: * Develop a rich toolkit of Rust libraries and applications for working with Wikimedia and MediaWiki projects and APIs * Make Rust a first-class language in Wikimedia infrastructure like Toolforge * Encourage the usage of Rust where appropriate to build safer and better tools * Assist others who end up encountering Rust and need help (e.g. when upstreams adopt Rust) * Mentor new developers who are interested in contributing technically to the Wikimedia movement, including through programs like GSoC and Outreachy Have other ideas of what we could do? Please suggest them on the talk page! [1] https://www.wikidata.org/wiki/Q575650 [2] https://meta.wikimedia.org/wiki/Talk:Wikimedia_Rust_developers_user_group -- Legoktm

2 1

Invitation to apply to Outreachy and Google Summer of Code program with Wikimedia!
by Gopa Vasanth 11 Feb '21

11 Feb '21

(feel free to forward the message as is to your friends, family members & colleagues) Hello folks, We would like to invite you to apply to the Outreachy and Google Summer of Code program with the Wikimedia Foundation (a non-profit organization behind Wikipedia)! About the Outreachy program Wikimedia will be mentoring ~3 projects in the Outreachy program in the May to August 2021 round. The initial applications are due February 22nd at 4 pm UTC. Apply today: https://www.outreachy.org/apply/ [1] Outreachy offers three-month internships to work remotely in Free and Open Source Software (FOSS) projects with experienced mentors. The internships may include programming, user experience, documentation, illustration, and graphic design, or data science. Outreachy internships run twice a year – from May to August and December to March. Interns are paid a stipend of $5,500 USD for the three months of work. They also have a $500 USD stipend to travel to conferences and events. Interns often find employment after their internship with Outreachy sponsors or in jobs that use the skills they learned during their internship. Outreachy is open to both students and non-students. Outreachy expressly invites the following people to apply: - Women (both cis and trans), trans men, and genderqueer people. - Anyone who faces under-representation, systematic bias, or discrimination in the technology industry in their country of residence is invited to apply. - Residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin@, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. About the Google Summer of Code program Wikimedia is planning to mentor 8-10 projects in 2021’s Google Summer of Code (GSoC) program. Beginning March 9th, pending Wikimedia’s acceptance as a mentoring organization, applicants can begin discussing ideas with the mentors! The student application will be due on April 13, 2021: https://summerofcode.withgoogle.com/ [2] Google Summer of Code, now in its 17th year, is Google's summer program for candidates participating in any academic programs who want to get involved in open-source software. Over 6,626 students from 121 countries have already participated in the last year’s round i.e 2020 < https://opensource.googleblog.com/2020/06/google-summer-of-code-2020-statis…> [3]. Google Summer of Code is a unique program that pairs students with mentors who introduce them to the open-source community and provide guidance while they work on real-world open-source projects during their summer break from university. This year there are some new breaking changes in the GSoC program, including: - Smaller project size ~175 hr project (previously 350 hr) - Shortened coding period ~10 weeks long (previously 3 months) - Eligibility criteria redefined; the program is now open to candidates participating in a variety of academic programs (previously accredited university programs only) Projects cover a wide range of fields including Cloud, Operating Systems, Graphics, Medicine, Programming Languages, Robotics, Science, Security and many more. It's a highly competitive program (and this year is expected to be even bigger than last year), so don't wait until the last minute to prepare! About the Wikimedia Foundation The Wikimedia Foundation is the nonprofit organization that hosts and operates Wikipedia and the other Wikimedia free knowledge projects. Our vision is a world in which every single human can freely share in the sum of all knowledge. We believe that everyone has the potential to contribute something to our shared knowledge and that everyone should be able to access that knowledge, free of interference. We host the Wikimedia projects, build software experiences for reading, contributing, and sharing Wikimedia content, support the volunteer communities and partners who make Wikimedia possible, and advocate for policies that enable Wikimedia and free knowledge to thrive. Resources * Browse through the participants’ guides, to learn more about the application process steps: <https://www.mediawiki.org/wiki/Outreachy/Participants> [4] <https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants> [5] * All the projects will be showcased here: <https://www.outreachy.org/communities/cfp/wikimedia/> [6] <https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021> [7] We hope you will help us spread the word about Wikimedia’s participation in these programs (by sharing this email) Looking forward to your participation! Cheers, Gopa, Srishti, Pavithra, Ankit & Mahveotm (Wikimedia organization administrators for GSoC & Outreachy) [1] https://www.outreachy.org/apply/ [2] https://summerofcode.withgoogle.com/ [3] https://opensource.googleblog.com/2020/06/google-summer-of-code-2020-statis… [4] https://www.mediawiki.org/wiki/Outreachy/Participants [5] https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants [6] https://www.outreachy.org/communities/cfp/wikimedia/ [7] https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021 -- Regards Gopa Vasanth <https://www.mediawiki.org/wiki/User:Gopavasanth> Amrita Vishwa Vidyapeetham <http://www.amrita.edu/> | Blog <https://gopavasanth.wordpress.com/> amFOSS <https://amfoss.in/@gopavasanth> | GitHub <https://github.com/gopavasanth> | Gerrit <https://gerrit.wikimedia.org/r/#/q/gopavasanth> “Yesterday is not ours to recover, but tomorrow is ours to win or lose.”

1 0

[Cloud-announce] cloud-vps maintenance scheduled for Tuesday, 15:00 UTC
by Andrew Bogott 10 Feb '21

10 Feb '21

On Tuesday we will be upgrading the cloud-vps OpenStack install to version 'Train'. During the upgrade window (probably about an hour), Horizon will be disabled. Existing tools and VMs should be largely unaffected; there will likely be a brief network interruption when the network software is restarted. The upgrade is scheduled for 15:00 UTC, which is 7AM in California. -Andrew + the WMCS team _______________________________________________ Wikimedia Cloud Services announce mailing list Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud-announce

1 2

[Cloud-announce] new Cloud VPS feature: attachable block storage
by Andrew Bogott 06 Feb '21

06 Feb '21

Wikimedia Cloud Services now supports attachable block storage via the OpenStack Cinder project. Attachable block storage is a flexible storage option that allows you to create volumes local to your project but not coupled to a particular VM; they can be moved between different instances and persist after their associated volume is deleted. Project admins can access this feature via the 'Volumes' tab in Horizon. I encourage all of you to start using Cinder storage for your new databases and large data sets. Over the next few months we'll be working to move various use cases onto Cinder volumes and off of NFS or LVM; soon I hope to deprecate large-storage flavor types entirely and support all new non-root file storage with Cinder. The default storage quota is quite small, but we plan to be generous with quota increases. To request additional storage, open a phabricator ticket here: https://phabricator.wikimedia.org/project/view/2880/ For more details about this feature, I've written a blog post, here: https://techblog.wikimedia.org/2021/02/05/cinder-on-cloud-vps/ And, technical documentation can be found here: https://wikitech.wikimedia.org/wiki/Help:Adding_Disk_Space_to_Cloud_VPS_ins… Like any new feature, our implementation almost certainly includes bugs and missteps. Please provide feedback or feature requests via phabricator or on the cloud mailing list. -Andrew + the WMCS Team _______________________________________________ Wikimedia Cloud Services announce mailing list Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud-announce

4 4

2024

2023

2022

2021

2020

2019

2018

2017

Cloud