SRE/Service Operations: Difference between revisions

From Wikitech
< SRE
Content deleted Content added
No edit summary
No edit summary
Line 1: Line 1:
'''Service Operations''' (aka "serviceops") is a subteam of the Wikimedia Foundations's [[SRE]] team. 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, OTRS, etc…). The team is also responsible for our new service infrastructure in production based on Kubernetes.
'''Service Operations''' (aka "serviceops") is a subteam of the Wikimedia Foundations's [[SRE]] team. 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. The team is responsible for our new service infrastructure in production based on Kubernetes, plus a subset of the caching and storage service - memcached and redis. It also attends to the infrastructure of the supporting services and its components that we rely upon (think GitLab, Phabricator, mailing list systems, OTRS, etc…). We also coordinate the efforts around the implementation of Service Level Objectives within the foundation.


The best way to initiate a conversation about project ABC with Service Operations is to open a "New Service Request ABC" Phabricator task and in addition tag the team "serviceops". [https://phabricator.wikimedia.org/project/profile/1305/ New Task Example]
We are happy to talk to you about the operational architecture of your system, and discuss implementation options such as database, caching, or the operational aspects of running on kubernetes. The best way to start that conversation is to open a Phabricator task. You can use this template, [https://phabricator.wikimedia.org/project/profile/1305/ New Task Example], but set the title to: Architecture Conversation Project ABC, if your project is named ABC. In addition tag the team "serviceops".

Once you are ready to implement, the best way to restart the conversation about your project named "ABC" is to open a "New Service Request ABC" Phabricator task and in addition tag the team "serviceops". [https://phabricator.wikimedia.org/project/profile/1305/ New Task Example]


* [[Kubernetes]]
* [[Kubernetes]]

Revision as of 19:03, 24 May 2021

Service Operations (aka "serviceops") is a subteam of the Wikimedia Foundations's SRE team. 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. The team is responsible for our new service infrastructure in production based on Kubernetes, plus a subset of the caching and storage service - memcached and redis. It also attends to the infrastructure of the supporting services and its components that we rely upon (think GitLab, Phabricator, mailing list systems, OTRS, etc…). We also coordinate the efforts around the implementation of Service Level Objectives within the foundation.

We are happy to talk to you about the operational architecture of your system, and discuss implementation options such as database, caching, or the operational aspects of running on kubernetes. The best way to start that conversation is to open a Phabricator task. You can use this template, New Task Example, but set the title to: Architecture Conversation Project ABC, if your project is named ABC. In addition tag the team "serviceops".

Once you are ready to implement, the best way to restart the conversation about your project named "ABC" is to open a "New Service Request ABC" Phabricator task and in addition tag the team "serviceops". New Task Example

See mw:Wikimedia Site Reliability Engineering#Service Operations for more.