Cloud-announce July 2024

cloud-announce@lists.wikimedia.org

5 participants
8 discussions

Access to ToolsDB public dbs from Quarry and Superset
by Francesco Negri 02 Sep '24

02 Sep '24

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

1 2

Brief toolforge build service outage Monday, 2024-07-29 @ 14:00 UTC
by Andrew Bogott 29 Jul '24

29 Jul '24

On Monday I'll be upgrading the database that backs toolforge's Harbor service. Any attempts to download new container images during this window will fail. Existing, running tools will not be affected, and periodically scheduled jobs should also be fine, but any brand new jobs may fail, depending on what is or isn't cache at the moment. The outage should be brief; if you see a cryptic failure around the scheduled time just take a 10 minute break and try again. -Andrew

1 1

toolforge build service outage in progress
by Slavina Stefanova 24 Jul '24

24 Jul '24

There is currently an issue with Toolforge's image registry (Harbor) due to its database being out of space. This affects the Toolforge build service, meaning no new builds can be started, and no images can currently be pulled from the registry. Currently running tools should be unaffected. We are actively working on the issue and will update you here. Sorry for the downtime! -- Slavina Stefanova (she/her) Software Engineer | Developer Experience Wikimedia Foundation

1 1

Trove database upgrades + downtime next week
by Andrew Bogott 23 Jul '24

23 Jul '24

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

1 1

Please associate your developer account with an SUL account
by Andrew Bogott 22 Jul '24

22 Jul '24

Many of you have either received or are about to get an email from Komla about connecting your developer account with an SUL account. The action necessary is very simple, just log in to https://idm.wikimedia.org and gill in the Wikimedia Global Account (SUL) field. Please update this field as soon as you're able; otherwise Komla's email will only be the first of many. If you are curious about the very many technical details about this project, you can read about it here: https://wikitech.wikimedia.org/wiki/News/Migrating_Wikitech_Account_to_SUL Thanks! -Andrew (who is only repeating Komla because I'm less likely to land in your spam filter).

1 0

[Important] Toolforge API endpoint deprecations
by Slavina Stefanova 19 Jul '24

19 Jul '24

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

2 1

Toolforge operation scheduled for 2024-07-16 @ 09:00 UTC
by Arturo Borrero Gonzalez 12 Jul '24

12 Jul '24

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

1 0

Important: Toolforge API endpoint changes coming soon
by Slavina Stefanova 10 Jul '24

10 Jul '24

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

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

Cloud-announce July 2024