Jump to content

Portal:Toolforge/Ongoing Efforts/Toolforge Workgroup/Reports

Phabricator project: #tbs
From Wikitech


Toolforge Workgroup

About
Project Overview
Reports
Feedback


Reports

Reports include both decision records and progress reports on the implementation of Toolforge and related projects. These reports are intended to keep team members and interested community members updated on progress of the project.

For a log of new user-facing features and fixes, you can check the Portal:Toolforge/Changelog instead.

Decision records

Ongoing
Decided

Progress reports

Read the latest sync meeting notes.


2025

  • 2025-04-01: k8s 1.29 upgrade done in toolsbeta, tools planned for next week (phab:T362868). Opentofu work started (phab:T389081), volumes and neutron ports first. Francesco tasked with reviewing Raymond's patches for toolforge as David is on sick leave.
  • 2025-03-18: Deploys with builds running now on toolsbeta. Komla might take over the sustainability score OKR. Logging questions again, might be the next focus after push-to-deploy. Chuck's intership started, looking into what resources to manage with opentofu first (phab:T389081).
  • 2025-02-25: 1.29 upgrade work ongoing, focusing on improving current docs. Wondering if there's any blockers to start the logging service project, will have to ask again async.
  • 2025-01-21: The k8s upgrade is pending on the kubelet flags cleanup. Created a miro board (was moved to this board) to lay down a high level overview of toolforge tasks/potential projects.
  • 2025-01-07: Coming back from a long PTO, not much to report. No new ToolsDB upgrades expected soon, as the current version has 18 months of support, but we might want to not wait until the support is out to do it. Will retake the k8s upgrades, trying to wait for Arturo to come back from sick leave before actually doing the next (1.29). Starting to build up the new hypothesis for the next quarter on the Toolforge UI, sustainability score, and components API/push to deploy side.

2024

  • 2024-11-14: We will skip december meetings due to PTOs and such. There's a mariadb upgrade in progress for toolsdb, will try to create a workgroup similar to the upgrades one for the next. We will send this week or earlier the next a form to gather input in impact and feasibility of the concerns raised for the sustainability score. The components-api is on track (deployed in toolsbeta).
  • 2024-10-08: Tekton upgrade done, components-api work going ok, working on an end-to-end webhook trigger + deploy (without build), having some lima-kilo setup issues for unstable internet, slowing down 1.28 k8s upgrade work.
  • 2024-09-24: Upgrade to k8s 1.27 done \o/, focusing on two workflows, getting webservice migrated to the jobs API, and getting the components-api bootstrapped.
  • 2024-07-16: Upgrade to k8s 1.25 finished \o/, focus on the last changes to the API paths before declaring it stable for users (sometime next week).
  • 2024-06-04: Maintain-kubeusers refactor has been deployed unblocking the creation of kyverno policies, continue with the API auth investigation and the api consolidation, jobs have --port support now, so we can continue with the effort to move webservices to jobs-api, and we have our first functional tests.
  • 2024-05-22: Continue with the API auth investigation, the api consolidation, move of webservices to jobs-api, and migration from PSP to kyverno policies.
  • 2024-04-20: Start on the toolforge API auth scheme definition to unblocks the compontents api and continue working on the upgrade to kubernetes 1.24.
  • 2024-04-16: Focus on enabling users to use the API, and start working on the first components-api tasks.
  • 2024-04-03: Keep focusing on the grid-migration issues (few left), and enabling users to use the APIs (api consolidation), upgrades to k8s went well, keep working on jobs-api refactor to add webservice and unblock the consolidated API, and refinement for components api. Keep an eye on what prod does to move from PSPs so we can reuse (task T279110).
  • 2024-03-19: The grid has been turned off (yay!), focus on cleanup + user requests, all the phab subprojects have been merged, focus on jobs-api refactor to add webservice, and refinement for components api. Start thinking on a session for the upcoming hackathon.
  • 2024-02-20: Merge all the phabricator subprojects into the general toolforge for ease of management/visibility, keep focusing on helping/unblocking users moving out of the grid, start refining user stories for orchestration API and unified API, migration to bullseye+containerd almost done, starting to plan upgrade to k8s v1.24 (should be simple).
  • 2024-02-06: Decided to start defining the details for the 2024 user stories, and continue focusing on supporting people migrating from the grid.
  • 2024-01-23: Continue focus on grid migration, last review of the 2024 toolforge user stories and high view (working doc), investigate how to expose a unified OpenAPI definition (task T354745), and start working on the details for the next quarter tasks (working doc).
  • 2024-01-09: Focusing on support for tools migrating off-grid, starting to define the next steps for toolforge with a focus on push to deploy (see this).

2023

  • 2023-10-10: Beta is almost there, keep on working on stats and operationalization, and start thinking on the action plan for the toolforge (re)architecture decision request.
  • 2023-09-26: Focus on getting statistics from the APIs, and fixing the local development environment
  • 2023-09-13: Focus on the beta rollout, improve user experience and add metrics to the services
  • 2023-08-29: Focus on the second beta rollout, database credentials on envvars and harbor stability
  • 2023-08-08: Focus on getting the database credentials on the envvars service to do the second beta rollout

2022

  • 2022-09-27: We started working on the Toolforge Build Service [beta] project!

OKR reports

This are currently tracked in Asana for internal reporting, and copied over here for transparency.


Communication and support

Support and administration of the WMCS resources is provided by the Wikimedia Foundation Cloud Services team and Wikimedia movement volunteers. Please reach out with questions and join the conversation:

Discuss and receive general support
Stay aware of critical changes and plans
Track work tasks and report bugs

Use a subproject of the #Cloud-Services Phabricator project to track confirmed bug reports and feature requests about the Cloud Services infrastructure itself

Read stories and WMCS blog posts

Read the Cloud Services Blog (for the broader Wikimedia movement, see the Wikimedia Technical Blog)

Retrieved from "https://wikitech.wikimedia.org/w/index.php?title=Portal:Toolforge/Ongoing_Efforts/Toolforge_Workgroup/Reports&oldid=2293930"