Hi,
If you do not use the raw Toolforge APIs directly, you can ignore this
message.
As we are moving toward stable API versions for the three Toolforge APIs
(jobs, builds, envvars), we are further consolidating the API paths. The
following backward-incompatible changes will take effect next Tuesday July
23 at 12:00 UTC:
- The /api prefix will be dropped from jobs API, e.g.
/v1/tool/<toolname>/jobs/
instead of */api*/v1/tool/<toolname>/jobs/
- All api resources will be in plural instead of singular, e.g.
/v1/tool/{toolname}/build*s* instead of /v1/tool/{toolname}/build
The new API docs can be seen here:
- Builds API:
https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-api/-/blob/slavin…
- Envvars API:
https://gitlab.wikimedia.org/repos/cloud/toolforge/envvars-api/-/blob/slavi…
- Jobs API:
https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-api/-/blob/slavina/…
While these APIs are not officially supported (use at your own risk), we
are happy to assist if you need help or more time for the transition. Thank
you for your understanding as we work to improve our services.
Best,
Slavina on behalf of the Cloud Services team
--
Slavina Stefanova (she/her)
Software Engineer | Developer Experience
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Greetings,
This patch[0] sets the default configuration in Wikimedia CI to enable the
temporary accounts feature.[1] This means: PHPUnit, Selenium, API-Testing,
and QUnit tests run in an environment where temporary account autocreation
is enabled.
## Why?
Next week, the Trust and Safety Product team is deploying the temporary
accounts feature to testwiki.[2] Later this year, we will move forward with
deploying to other production wikis. By enabling temporary accounts in CI,
we increase the likelihood that new code works smoothly with the temporary
accounts feature.
## What do I need to do?
This time, nothing. All MediaWiki core, extension and skins tests pass,
whether temporary accounts are enabled or disabled.[3]
For new PHPUnit tests, please make use of `TempUserTestTrait` to disable
the temporary accounts feature for tests that make assertions specifically
about anonymous IP editing.
We also recommend that you enable temporary accounts in your local
development environment by adding `$wgAutoCreateTempUser['enabled'] = true;`
to your LocalSettings.php.
## Questions?
Please contact us[4] or file a task on Phab and tag it with “#Temporary
accounts”.
[0] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/980947
[1]
https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/…,
https://www.mediawiki.org/wiki/Help:Temporary_accounts
[2] https://phabricator.wikimedia.org/T348895
[3] https://phabricator.wikimedia.org/T355879
[4]
https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Acco…
Cheers,
Kosta & Thalia, Trust and Safety Product
and
Szymon Grabarczuk (he/him)
Lead Movement Communications Specialist
(Product & Tech)
Wikimedia Foundation <https://wikimediafoundation.org/>
Next week (starting 2024-07-22) I'll be updating Trove database
servers[0] to use more up-to-date VM images and guest agents. This will
involve a minute or two of downtime (in the best case) and possibly an
hour or more of downtime for troublesome (and unpredictable) edge cases.
The complete list of database servers can be found on the phabricator
task below[1]. If you would prefer to schedule upgrades for your
database for a particular time, please follow up with specifics on the
task and we will find a time that works for everyone. If I don't hear
otherwise, I'll perform the maintenance on your database at my convenience.
This maintenance will affect the following cloud-vps projects:
adiutor
baglama2
citefix
copypatrol
deployment-prep
discordbots
dumps
glamwikidashboard
hoiscript
huma
library-upgrader
linkwatcher
maps
mwoffliner
mwstake
osmit
pm20database
quarry
reading-web-staging
spacemedia
wikisp
wmcz-stats
xtools
Thank you!
-Andrew
[0] Trove is the software behind Horizons 'database' tab. Databases on
VMs that were setup up manually or via puppet are unaffected by this
maintenance.
[1] https://phabricator.wikimedia.org/T369723
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hi there,
The Toolforge Kubernetes system has been scheduled to be upgraded to version
1.25 [0] next Tuesday 2024-07-17 @ 09:00 UTC.
The operation window will last 2 hours, and during this time, some Toolforge
components will briefly and intermittently become unavailable.
Examples of things that can be affected include:
* running the different `toolforge` commands from bastions
* accessing the web URL of some tools
* the internal operations of some jobs, which may be restarted as containers are
moved to different worker nodes.
Please report [1] any problems you see in Toolforge after the upgrade.
regards.
[0] https://phabricator.wikimedia.org/T369172
[1] https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_communication
Hi,
If you do not use the raw Toolforge APIs directly, you can ignore this
message.
We are writing to inform you about upcoming changes to several API
endpoints. Most importantly, the* /api/v1/jobs/* endpoint, which is
currently the only one still in use, will be changing.
The general pattern for affected endpoints will shift from:
{jobs|builds|envvars}/api/v1/<resource>/
to:
{jobs|builds|envvars}/api/v1/*tool/{toolname}*/<resource>/
Key points:
- This change will take effect next *Thursday July 18 at 12:00 UTC*.
- If you are using the */api/v1/jobs/* endpoint, please update your
tools accordingly.
- While these APIs are not officially supported (use at your own risk),
we are happy to assist if you need help or more time for the transition.
We are also working on developing stable API versions. If you are
interested in the details or want to contribute to the discussion, you can
check out https://phabricator.wikimedia.org/T356974.
Thank you for your understanding as we work to improve our services.
Best,
Slavina on behalf of the Cloud Services team
--
Slavina Stefanova (she/her)
Software Engineer | Developer Experience
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Following several requests from users over the past eight years [0],
we are finally enabling access to ToolsDB's "public" databases (the
ones with a name ending with "_p") [1] from both Quarry [2] and
Superset [3].
The data stored in those databases have always been accessible to
every Toolforge user, but after this change they will become more
broadly accessible, as Quarry can be accessed by anyone with a
Wikimedia account, and saved queries in Quarry can be shared with
public links that require no login at all.
== This change is planned to go live on Monday, July 1st. ==
If you have any concerns or questions related to this change, please
leave a comment in the Phabricator task or one of its subtasks. [0]
Thanks to everyone for your patience and for keeping the task alive
over the years!
[0] https://phabricator.wikimedia.org/T151158
[1] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Database#Privileges_on_t…
[2] https://meta.wikimedia.org/wiki/Research:Quarry
[3] https://superset.wmcloud.org/
--
Francesco Negri (he/him) -- IRC: dhinus
Site Reliability Engineer, Cloud Services team
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hello!
You may have been notified about Buster VM deprecation on projects where
you are not an admin.
This was in error.
Kindly ignore.
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.…
Hello,
I'm trying to tunnel to my VPS Trove instance, so that I can test some code
against the production database.
I'm using the following:
ssh -N -L 4177:tdlqt33y3nt.svc.trove.eqiad1.wikimedia.cloud:3306
login.toolforge.org
I've also tried:
ssh -N -L 4177:tdlqt33y3nt.svc.trove.eqiad1.wikimedia.cloud:3306
mwcurator.mwoffliner.eqiad1.wikimedia.cloud
The initial connection seems to work, but in my application I'm getting
dropped connections. I see the following in the terminal where I set up the
tunnel:
channel 2: open failed: connect failed: Connection refused
channel 2: open failed: connect failed: Connection refused
I imagine this isn't a fully supported workflow but I'm wondering if
there's some way to get it to work?
Thanks,
-Travis
We’re going to keep both Gerrit and GitLab.
Many of the repositories now on Gerrit require features that are lacking in
GitLab:
- Cross-repository dependent merge requests
- Project gating and deterministic, atomic merges
- Stacked patchsets
- Multiple reviewers
Likewise, GitLab has features that our developers have come to depend on:
- Familiar fork, branch, and merge workflow
- Self-service repository creation
- Jupyter Notebook rendering
- GitLab's self-service CI/CD pipeline
- Bring your own runners
- Artifact and packages registries
As a result, we'll be running both systems for at least the next two years.
More information is available on MediaWiki.org[0], summarized below.
___
*Details*
These repositories have requirements that mean they must remain on Gerrit:
- MediaWiki core
- The subset of extensions and skins which track MediaWiki core’s
mainline branch (including all Wikimedia production-deployed extensions,
skins, and MediaWiki vendor)
- SRE’s Puppet repository along with dependencies and dependent
repositories.
Other repositories on GitLab may return to Gerrit to lessen the mental
burden of working with two systems.
Likewise, some repositories on Gerrit may wish to continue to migrate to
GitLab.
We'll use the Phabricator tag "GitLab (Project Migration)"[1] to track
requests from project stewards to migrate between systems. We’ll be
monitoring that workboard closely through the end of this calendar year to
assist developers with their migrations.
___
*What now*
- We have no intention of shutting down either system for the next two
years.
- We've posted a longer explanation on MediaWiki.org[0]. Please use the
talk page there (rather than this mailing list) for discussion.
- We've gathered a list of questions we anticipate some folks may have
on MediaWiki.org[2].
- Specific requests from project stewards to migrate repositories
between either of our systems should use the Phabricator tag "GitLab
(Project Migration)"[1].
- We'll be hosting office hours to answer any questions. More details
about these sessions will come later.
The decision to keep both systems was challenging. Having two code forges
adds to the fragmentation of our systems, the mental overhead for our
developers, and the maintenance burden of stewards. But each system is
well-suited to a subset of our needs, keeping both systems safeguards the
productivity of our developers and the stability of our systems.
For more details, I encourage you to review MediaWiki.org[0] and engage on
the talk page.
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://www.mediawiki.org/wiki/GitLab/Migration_status>
[1]: <https://phabricator.wikimedia.org/project/profile/5552/>
[2]: <https://www.mediawiki.org/wiki/GitLab/Migration_status/FAQ>
Hello Cloud users,
Just wanted to give a heads-up for an upcoming maintenance for our cloudelastic hosts <https://wikitech.wikimedia.org/wiki/Help:CirrusSearch_elasticsearch_replicas>. We will be migrating them to a new load balancer starting Thursday, Jun 20 at 1400 UTC . The service will be down through the maintenance, which is expected to last between 1 and 2 hours.
Fine details are available in this Phabricator task <https://phabricator.wikimedia.org/T367511> . If you have any questions about this, feel free to respond here or in IRC (see my nick below).
Best,
Brian King
SRE, Data Platform/Search Platform
Wikimedia Foundation
IRC: inflatador
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…