Wikimedia Cloud Services team/Ownership
Jump to navigation
Jump to search
| Service | AKA | Phabricator Tag | Category | Admin docs | Alerts | Support level |
|---|---|---|---|---|---|---|
| PAWS | paws | Tool | 
| |||
| Quarry | quarry | Tool | 
| |||
| Superset | superset.wmcloud.org | Tool |
| |||
| Toolhub | toolhub | Tool | toolhub.wikimedia.org |
| ||
| Toolsadmin | Striker | striker | Tool | toolsadmin.wikimedia.org |
| |
| OpenStack Browser | Tool | Tool:Openstack-browser |
| |||
| Toolforge (grid engine) | toolforge | Platform Service |
| |||
| Toolforge (k8s) | toolforge | Platform Service |
| |||
| Toolforge Jobs Service | Platform Service |
| ||||
| Toolforge Envvars Service | Platform Service |
| ||||
| Toolforge Build Service | tbs | Platform Service |
| |||
| Toolsdb (Db-as-a-service) | Managed Service |
| ||||
| Volumes (storage-as-a-service) | OpenStack Cinder | Managed Service |
| |||
| Databases (Db-as-a-service) | OpenStack Trove | Managed Service | Portal:Cloud VPS/Admin/Trove |
| ||
| Kubernetes (k8s-as-a-service) | OpenStack Magnum | Managed Service | Portal:Cloud VPS/Admin/Magnum |
| ||
| Compute (VM-as-a-service) | OpenStack Nova | Managed Service |
| |||
| DNS (DNS-as-a-service) | OpenStack Designate | Managed Service | Portal:Cloud VPS/Admin/DNSPortal:Cloud VPS/Admin/DNS/Designate |
| ||
| Cloud Dashboards | OpenStack Horizon | Managed Service | Portal:Cloud VPS/Admin/Horizon |
| ||
| Puppet/nova integration + Horizon UI | Managed Service |
| ||||
| Nova proxy service | Managed Service |
| ||||
| VM backups | Managed Service | Portal:Cloud VPS/Admin/Instance backups |
| |||
| Cinder Backups | Managed Service |
| ||||
| Openstack | Foundational infrastructure |
| ||||
| metricsinfra | Foundational infrastructure |
| ||||
| cloudmetrics | Foundational infrastructure |
| ||||
| Ceph | Foundational infrastructure | Portal:Cloud VPS/Admin/Ceph |
| |||
| read/write NFS | Foundational infrastructure |
| ||||
| Kubernetes | Foundational infrastructure |
|
Support levels
Fully supported. These services should be working and available to users at all times; any downtime will be publicly announced and documented. Users can rely on these services as reliable, long-term foundations for their work.
Partial support. Service should be useful for some use cases and running most of the time but some features may be broken or consciously neglected. Outages will be tracked but not necessarily addressed immediately. Approach with caution when relying on these services for major projects.
Little staff support. Service may be experimental, a work in progress, volunteer-maintained, or in the process of being phased out. Outages may be ignored entirely. Do not rely on stability of these services for your work.
All WMCS projects are held to a 'best effort' standard. We do not guarantee particular uptime metrics, and even urgent work will not take priority over sleep, crying babies, meals, etc.