* The #wikimedia-cloud IRC channel is moving from Freenode to Libera.Chat.
* Register an account on Libera.Chat and join us there!
There has been a lot of activity over the last 2-3 days related to
staffing changes on the Freenode IRC network . The Wikimedia IRC
Group Contacts (GCs)  evaluated the situation and decided that
moving the Wikimedia IRC channels from Freenode to the brand new
Libera.Chat IRC network  would be the best course of action .
So, we are moving!
A new #wikimedia-cloud channel has been created on irc.libera.chat for
this Wikimedia sub-community to use. The old channel on Freenode still
exists and will be maintained at least until we can get all the bots
moved, our documentation updated on wikitech, and we see more folks on
the Libera channel than the Freenode one. Messages to our channel in
either IRC network, as well as the Telegram channel , will be seen
on all other channels.
There is a new subpage on meta  for information on how to create a
new account for yourself on Libera.Chat and other related information.
There is also a tracking task  that you can look at to see various
activities that the community hopes to take action on to complete the
One last thing: The #wmhack Freenode channel is bridged to
#wikimedia-hackathon on Libera.Chat. The new channel name will make it
easier for the GCs to help manage spam and other issues that come up
occasionally on IRC. Don't miss the fun of our 2021 virtual hackathon
from Friday, May 21st to Sunday, May 23rd! 
Bryan, on behalf of the WMCS team and the Cloud VPS and Toolforge admins
Bryan Davis Technical Engagement Wikimedia Foundation
Principal Software Engineer Boise, ID USA
[[m:User:BDavis_(WMF)]] irc: bd808
Wikimedia Cloud Services announce mailing list
To unsubscribe send an email to cloud-announce-leave(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
tl;dr: please respond with your use cases and concerns about secret
keys, passwords, etc on cloud-vps
Right now we have two not-very-good ways to distribute a secret key
within a cloud project:
1) copy the secret onto each VM by hand as you create it
2) create a puppetmaster in your project and and have it distribute the
Option #2 is pretty good for big, long-lived projects but involves a lot
of overhead. Option #1 is fine for projects with only one or two VMs
but scales terribly.
The WMCS team has been discussing the question of secrets distribution
for years, and we have a few different possible solutions in mind but no
favorite. Rather than rattle off those options here, we're trying to
rewind a bit and gather possible use-cases and user wishes in this area.
So: if this is a feature you've been missing, please respond with an
answer to this question:
"How would I make use of secrets on cloud-vps instances?"
If possible, please include thoughts about these points:
- Is it good enough to provide project-wide distribution, or do we need
finer-grained control, limiting secrets to particular users or instances?
- Is a web UI for managing secrets a requirement, or are command line
tools adequate? What if there were /only/ a web-ui and no command line?
- Would supporting secret management solve immediate issues on its own,
or is it only useful as a part of larger instrumentation tooling (e.g.
puppet, heat, or terraform integration)
Thank you! I welcome your thoughts on-list, but you're also welcome to
list thoughts or use-cases on the phabricator tracking task
Some of the jobs I submit to the grid take a long time (say, 30-60 minutes)
and I would like to check on their status without having to log back into
I was hoping I could run shell_exec('qstat') in PHP and display its output
on a web page. While shell_exec() works with other commands—e.g. echo
shell_exec('whoami') correctly displays my tool's username on the
webpage—for reasons I cannot explain, the output of shell_exec('qstat') is
always blank. When I run qstat on the CLI at that same time, it does show
me the familiar table output of ongoing jobs.
Any idea why that is the case? Has anyone already created a solution for
fetching a list of active jobs from the grid and displaying it on a
web-based status page for your tool?
I'm getting errors regarding expired certificates for wmflabs.org and
wmcloud.org, e.g. https://wikispeech.wmflabs.org and
https://codesearch.wmcloud.org. Is this related to the maintenance later
today or has something gone wrong? Here's an example from curl:
$ curl https://codesearch.wmcloud.org
curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Wikimedia Sverige (WMSE)
Telefon/*Phone*: (+46) 0707 - 92 03 84
We will be doing an upgrade to the CloudVPS edge network Thursday 2021-05-06 @
15:00 UTC that will likely impact user experience, including Toolforge.
We scheduled an 1h operation window. During that time, intermittent network
interruption, packet loss and other network problems are to be expected.
The edge network maintenance will affect how virtual machines (and Toolforge
tools) contact NFS, wiki-replicas, wikis API endpoints, and, in general, any
network traffic that flows leaving or entering the cloud (also known as
More information on the operation can be found in phabricator  and in
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services