You are browsing a read-only backup copy of Wikitech. The live site can be found at

Maps: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Effie Mouzeli
No edit summary
(→‎Development processes: add redlink to an overview of the packages involved in showing maps)
Line 22: Line 22:

== Development processes ==
== Development processes ==
* [ Kartotherian/Tilerator deployment]
* [[Maps/Services_deployment|Kartotherian/Tilerator deployment]]
* [[Maps/Kartotherian packages|Kartotherian/Packages]]

== Puppetization and Automation ==
== Puppetization and Automation ==

Latest revision as of 09:22, 30 May 2022

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

The service is being actively redesigned, documentation can me found under Maps/v2


Maps service component diagram
Maps service deployment diagram
File:Maps @ PI@2x.png
Kartotherian internals focus

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 20 servers in the maps group: maps20[01-10].codfw.wmnet and maps10[01-10].eqiad.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


Development processes

Puppetization and Automation


  • passwords and postgres replication configuration is set in Ops private repo (root@puppetmaster1001:/srv/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)