Wikimedia Site Reliability Engineering

Group:	Technology
Team members:	In teams: Data Center Operations Willy Pao; Rob Halsell, Chris Johnson, Papaul Tshibamba Data Persistence Lukasz Sobanski; Manuel Arostegui, Jaime Crespo, Stevie Beth Mhaol, Matthew Vernon, Amir Sarabadani, Eric Evans Infrastructure Foundations Joanna Boruń; John Bond, Riccardo Coccioli, Chris Danis, Cathal Mooney, Moritz Mühlenhoff, Arzhel Younsi, Jesse Hathaway, Simon Lyngshede Observability Leo Mata; Filippo Giunchedi, Keith Herron, Cole White, Andrea Denisse Gómez-Martínez Service Operations Alexandros Kosiaris, Lukasz Sobanski; Giuseppe Lavagetto, Reuven Lazarus, Effie Mouzeli, Daniel Zahn, Janis Meybohm, Kunal Mehta, Jelto Wodstrcil, Arnold Okoth, Clément Goubert Traffic Kwaku Addo Ofori; Brandon Black, Brett Cornwall, Valentin Gutierrez, Emanuele Rocca, Sukhbir Singh, Marc Mandere
Management:	Mark Bergsma, Faidon Liambotis

The Site Reliability Engineering team, or SRE for short, is the team responsible for developing and maintaining Wikimedia's production infrastructure. Previously known as Technical Operations, they are in charge of making sure all Wikimedia's sites and services used by the public (including MediaWiki and all associated services) run reliably, securely, and with high performance.

Notify us of emergencies with Klaxon.

#wikimedia-sre ^connect

Additional documentation related to our infrastructure and the team's work can be found on Wikitech.

The team's structure[edit]

Data Center Operations[edit]

The Data Center Operations team is responsible for all of Wikimedia’s data center deployments and logistics as well as maintaining our presence in locations across the world. They perform on-site work and maintain the full 5-year life cycle (specs, purchasing, physical install, break/fix and decommissioning) for all hardware.

#wikimedia-dcops ^connect

Infrastructure Foundations[edit]

The team focuses on building and maintaining our base platform (“metal cloud”) that forms the foundations upon which nearly everything else in our infrastructure builds upon. On top of our bare metal deployments, their responsibilities include (but are not limited to) configuration management systems, infrastructure automation, orchestration tooling, infrastructure security and network operations.

#wikimedia-sre-foundations ^connect

Observability[edit]

The Observability team, or "o11y" for short, works across SRE and Technology to provide teams with tools, platforms, and insights into how systems and services are performing. It leverages technologies such as Grafana, Kibana/Logstash, Prometheus, AlertManager and more.

#wikimedia-observability ^connect

Traffic[edit]

The Traffic team is responsible for the critical first layer of high-traffic infrastructure which now spans much of the globe, including our TLS termination and caching layers (ATS, Varnish), load balancing, DNS and our own network.

#wikimedia-traffic ^connect

Data Persistence[edit]

The Data Persistence team focuses on Wikimedia’s persistent data storage and retrieval systems, including (No)SQL databases, (distributed) object storage, file storage and backup systems.

#wikimedia-data-persistence ^connect

Service Operations[edit]

The Service Operations team takes care of public and “user-visible” services alongside Technology and Product teams. This means, for example, our MediaWiki platform, but also the newer (micro)services that comprise our stack. It also includes miscellaneous services and components that we rely upon (think Phabricator, mail systems, VRTS, etc…). The team is also building our new SOA service infrastructure based on Kubernetes.

#wikimedia-serviceops ^connect

Contacting the team[edit]

If you need to get in touch with the team, there are detailed instructions on wikitech:SRE Team requests