User:MSantos/Maps

This page describes the technical aspects of deploying Maps service on Wikimedia Foundation infrastructure.

Intro

Maps service component diagram

Maps service deployment diagram

The maps service consists of Kartotherian - a nodejs service to serve map tiles, Tilerator - a non-public service to prepare vector tiles (data blobs) from OSM database into Cassandra storage, and TileratorUI - an interface to manage Tilerator jobs. There are four servers in the maps group: maps-test200{1,2,3,4}.codfw.wmnet that run Kartotherian (port 6533, NCPU instances), Tilerator (port 6534, half of NCPU instance), TileratorUI (port 6535, 1 instance). Also, there are four Varnish servers per datacenter in the cache_maps group.

The infrastructure

• OSM Database
• Tile storage
• Kartotherian
• Tilerator

Miscellaneous

• Dynamic tile sources

Development processes

• Kartotherian/Tilerator deployment

Puppetization and Automation

Prerequisites

• passwords and postgres replication configuration is set in Ops private repo (root@palladium:~/private/hieradata/role/(codfw|eqiad)/maps/server.yaml)
• other configuration in puppet/hieradata/role/(codfw|common|eqiad)/maps/*.yaml
• cassandra::rack is defined in puppet/hieradata/hosts/maps*.yaml
• the role::maps::master / role::maps::slave roles are associated to the maps nodes (site.pp)

Monitoring

• KPI dashboard
• Usage dashboard
• Usage - varnish
• Kartotherian - Grafana
• Kartotherian - Logstash
• Maps Cassandra - Logstash
• Tilerator - Grafana
• Tilerator - Logstash