Portal:Toolforge/Ongoing Efforts/Toolforge Workgroup/Reports

Phabricator project: #tbs
From Wikitech


Toolforge Workgroup


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.

Decision records

Ongoing
Decided

Progress reports

Read the latest sync meeting notes.

Previous years meeting notes (read-only).


2024

  • 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!

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)