After nearly a decade of mishap and delay, we have updated the WMCS
terms of use. The updated document for toolforge and cloud-vps admins
can be found here:
https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use
and the terms of use for visitors to WMCS sites can be found here:
https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_End_User_Terms_…
There is one significant change in these terms: Cloud-vps projects which
collect personal data will need to include an explicit privacy policy
for their projects. This is section 7.3. For other WMCS users and admins
these documents do not represent any significant change in policy, but
do clarify and finalize many things that were poorly-worded in the
previous TOU, or policies that we have enforced informally without
officially stating.
Please feel free to reach out to WMCS staff if you find any part of
these documents concerning or disruptive to your work on our platforms.
-Andrew
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hello all,
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 July 16, 2023, 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 main member of the
committee. The committee consists of five main 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 May 31 2023*.
Please feel free to pass this invitation along to any users who you think
may be qualified and interested.
Best,
Martin Urbanec, on behalf of the Code of Conduct Committee
Hi!
We are restarting a switch[1] today at 13:00 UTC.
We are moving all the affected VMs to different hypervisors, and we
expect no downtime, though you might experience the servers being a bit
unresponsive when the migration finally moves the VM (a couple
seconds).
We will reply to this email once it's done.
Thanks!
[1]https://phabricator.wikimedia.org/T316544
---
David Caro
SRE - Cloud Services
Wikimedia Foundation <https://wikimediafoundation.org/>
PGP Signature: 7180 83A2 AC8B 314F B4CE 1171 4071 C7E1 D262 69C3
"Imagine a world in which every single human being can freely share in
the sum of all knowledge. That's our commitment."
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hello. I re-send a previous note.
NOTE. I looked for a way to communicate with Wikipedia —an encyclopedia
that I highly value. I don't know if this will help. For this 1st
communication is to request that they reverse the change in the "desktop
page" of each query. Before, it was possible to see the same article
without further ado than to go to some other language that had something
written on the subject of consultation. Now this has been removed. And
so, it is very cumbersome to translate and then enter a Wikipedia with
another language. I THINK THEY SHOULD KEEP THE PREVIOUS OPTION. Without
prejudice to incorporating the current options. THANK YOU.
AVF
PAWS was down and rebuilt. If you had a logged in session you may have to
refresh your state by logging out and back in to restart your server.
Thank you!
--
*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.…
Hi,
We will be upgrading the Toolforge Kubernetes cluster next Monday
(2023-04-03) starting at around 10:00 UTC.
The expected impact is that tools running on the Kubernetes cluster will
get restarted a couple of times over the course of the few hours it
takes for us to upgrade the entire cluster. The ability to manage tools
will remain operational.
Since the version we're upgrading to (1.22) removes a bunch of
deprecated Kubernetes APIs, tools that use kubectl and raw Kubernetes
resources directly may want to check that they're on the latest
available versions. The vast majority of tools that are only using the
Jobs framework and/or the webservice command are not affected by these
changes.
Taavi
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
On Thursday we will be migrating most toolforge databases to a new
server. Thiswill take place on Thursday at 17:00UTC. During this window
ToolsDBwill be read-only and most tools that rely on writing to the
database will fail.
This migration should take about an hour but unexpected side-effects may
extend the downtime.
-- details --
DB outage Thursday: As part of the ongoing effortto upgrade user-created
Toolforge databases, we willmigrate ToolsDB to a new VM that will have a
more recent version of Debian and MariaDB and will use a more resilient
storage solution.
The new VM is ready, and we plan to point all tools to use it on *Apr, 6
2023 at 17:00 UTC*.
This will involve about *1 hour of read-only time*for the database. Any
existing database connection will be terminated, and if your tool does
not reconnect automatically you might have to restart it manually.
An email will be sent shortly before starting the migration, and when
it's finished.
Please also make sure your tool is connecting to the database using the
canonical hostname *tools.db.svc.wikimedia.cloud*and not any other
hostname or IP address.
For more details, and to report any issue, you can read or leave a
comment at https://phabricator.wikimedia.org/T333471
For more context you can also check out the parent task
https://phabricator.wikimedia.org/T301949
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
There will be two major Toolforge outages this coming week. Each outage
will cause tool downtime and may require manual restarts afterwards.
The first outage is an NFS migration [0] and will take place on Monday,
beginning at around 0:00 UTC and lasting well into the day, possibly as
late as 19:00 UTC. During this long period, Toolforge NFS will be
read-only. This will cause most tools (for example, anything that writes
a log file) to fail.
The second outage will be a database migration [1] and will take place
on Thursday at 17:00UTC. During this window ToolsDBwill be read-only.
This migration should take about an hour but unexpected side-effects may
extend the downtime.
We try very hard to avoid outages of this magnitude, but at this point
we need to choose downtime over the increasing risk of data loss.
More details can be found below.
[0] NFS Outage and system reboots Monday: The existing toolforge NFS
server is running on aging hardware and lacks a straightforward path for
maintenance or upgrading. To improve this we are moving NFS to a
cinder+VM platform which should support easier upgrades, migrations, and
expansions in the future. In order to maintain data integrity during the
migration, the old server will need to be made read-only while the last
set of file changes is synchronized with the new server. Because the NFS
service is actively used, it will take many hours to complete the final
sync.
To ensure stable mounts of the new server, every node in Toolforge will
be rebooted as part of this migration. That means that even tools which
do not use NFS will be affected, although most tools should restart
gracefully.
This task is documented as https://phabricator.wikimedia.org/T333477.
[1] DB outage Thursday: As part of the ongoing effortto upgrade
user-created Toolforge databases, we willmigrate ToolsDB to a new VM
that will have a more recent version of Debian and MariaDB and will use
a more resilient storage solution.
The new VM is ready, and we plan to point all tools to use it on *Apr, 6
2023 at 17:00 UTC*.
This will involve about *1 hour of read-only time*for the database. Any
existing database connection will be terminated, and if your tool does
not reconnect automatically you might have to restart it manually.
An email will be sent shortly before starting the migration, and when
it's finished.
Please also make sure your tool is connecting to the database using the
canonical hostname *tools.db.svc.wikimedia.cloud*and not any other
hostname or IP address.
For more details, and to report any issue, you can read or leave a
comment at https://phabricator.wikimedia.org/T333471
For more context you can also check out the parent task
https://phabricator.wikimedia.org/T301949
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…