Page MenuHomePhabricator

Move Kartotherian to Kubernetes
Open, MediumPublic

Description

Following discussion in standup (21/02/2019), it was agreed to move the main components of the maps platform. This would make more sense and also reduce coupling of Maps components making them easier to manage and maintain.

Pipeline documentation:

Subtasks to follow.

Event Timeline

Change 534179 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[integration/config@master] layout: [mediawiki/services/kartotherian] Drop the kartotherian-node10-browser-docker jobs

https://gerrit.wikimedia.org/r/534179

Change 534180 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[integration/config@master] layout: Archive the kartotherian and tilerator deploy repos now they use the pipeline

https://gerrit.wikimedia.org/r/534180

Change 534181 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[integration/config@master] jjb: Drop kartotherian-deploy-npm-node-6-docker and kartotherian-node10-browser-docker

https://gerrit.wikimedia.org/r/534181

Change 534182 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[integration/config@master] dockerfiles: Drop node10-kartotherian and npm-test-maps-service

https://gerrit.wikimedia.org/r/534182

@Mathew.onipe and @Jdforrester-WMF just FYI: I have tested kartotherian with debian buster and upstream mapnik library and it works just fine, which is a good thing since our backported mapnik library is outdated in comparison with debian stable (buster).

@Mathew.onipe and @Jdforrester-WMF just FYI: I have tested kartotherian with debian buster and upstream mapnik library and it works just fine, which is a good thing since our backported mapnik library is outdated in comparison with debian stable (buster).

Wow, that's great. Is the next step writing and landing the changes to move directly to that?

@Mathew.onipe and @Jdforrester-WMF just FYI: I have tested kartotherian with debian buster and upstream mapnik library and it works just fine, which is a good thing since our backported mapnik library is outdated in comparison with debian stable (buster).

\o/

@Mathew.onipe and @Jdforrester-WMF just FYI: I have tested kartotherian with debian buster and upstream mapnik library and it works just fine, which is a good thing since our backported mapnik library is outdated in comparison with debian stable (buster).

Wow, that's great. Is the next step writing and landing the changes to move directly to that?

Yes! But no rush for that, the kubernetes migration is still ongoing.

hi, is that still worked on? Asking cause CI still has to maintain a Jessie based image / NodeJS 6.

Change 534180 abandoned by Hashar:
[integration/config@master] layout: Archive the kartotherian and tilerator deploy repos now they use the pipeline

Reason:
Abandoning for now since the repository is not ready yet

https://gerrit.wikimedia.org/r/534180

Change 534182 abandoned by Hashar:
[integration/config@master] dockerfiles: Drop node10-kartotherian and npm-test-maps-service

Reason:
Abandoning for now since the repository is not ready yet

https://gerrit.wikimedia.org/r/534182

Change 534181 abandoned by Hashar:
[integration/config@master] jjb: Drop old kartotherian jobs, now unused

Reason:
Abandoning for now since the repository is not ready yet

https://gerrit.wikimedia.org/r/534181

Change 534179 abandoned by Hashar:
[integration/config@master] layout: [mediawiki/services/kartotherian] Drop the kartotherian-node10-browser-docker jobs

Reason:
Abandoning for now since the repository is not ready yet

https://gerrit.wikimedia.org/r/534179

Is the migration of Maps (Kartotherian) / Maps (Tilerator) to Kubernetes / Node 10 on some people radar? The reason I ask is that CI still has to maintain images based on Debian Jessie (EOL since April 2020) with Node JS 6 (long EOL) and we would really like to be able to dispose of those legacy bits.

@hashar yes it is, not a priority currently though. FWIW, Maps (Kartotherian) and Maps (Tilerator) do not use node 6 or Debian Jessie in the current production setup, we already migrated to node 10 and debian stretch.

Change 662698 had a related patch set uploaded (by Hashar; owner: Hashar):
[integration/config@master] Remove tilerator / kartotherian NodeJS 6 jobs

https://gerrit.wikimedia.org/r/662698

I have removed the Jenkins jobs for tilerator and kartotherian. They used NodeJS 6 and we were no more able to maintain them after the removal of Jessie from our infrastructure in April 2020.

Change 662698 merged by jenkins-bot:
[integration/config@master] Remove tilerator / kartotherian NodeJS 6 jobs

https://gerrit.wikimedia.org/r/662698

Should be upgraded to reflect tilerator's demise. Maybe geoshapes should be a separate service, maybe not?

Change 852913 had a related patch set uploaded (by Awight; author: Awight):

[mediawiki/services/kartotherian@mapnik-3.1] Upgrade blubber description to node-16 and libmapnik-3.1

https://gerrit.wikimedia.org/r/852913

Change 852913 merged by WMDE-Fisch:

[mediawiki/services/kartotherian@mapnik-3.1] Upgrade blubber description to node-16 and libmapnik-3.1

https://gerrit.wikimedia.org/r/852913

awight renamed this task from Move Kartotherian and Tilerator to Kubernetes to Move Kartotherian to Kubernetes.Nov 8 2022, 7:12 AM
awight updated the task description. (Show Details)