Scap3 provides mechanism to deploy configurations from templates. Moving to scap3 for deplyoing configuration would provide a nice decoupling between application, configuration and puppet. This is required to modify logging level for Kartotherian. It would also greatly simplify the testing of the new postgresql tiles storage (T147223).
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Gehel | T148116 Raise file logging for Kartotherian from info to warn | |||
Resolved | Gehel | T150021 Deploy kartotherian / tilerator / tileratorui configuration via scap3 |
Event Timeline
Change 321374 had a related patch set uploaded (by Gehel):
Kartotherian: deploy application configuration with scap3
Change 321375 had a related patch set uploaded (by Gehel):
Kartotherian: deploy application configuration with scap3
Change 321376 had a related patch set uploaded (by Gehel):
Kartotherian: deploy application configuration with scap3
I'm thinking about how to deploy this in nice steps with sufficient testing as we don't have a test environment yet. My idea so far:
- manually create /etc/kartotherian/config-vars.yaml on maps-test2001
- merge the configuration change to kartotherian-deploy (https://gerrit.wikimedia.org/r/#/c/321376)
- deploy it only on maps-test2001 (scap deploy-local)
- test / check / compare new config to old one, ...
- disable puppet on all maps servers
- merge the puppet side of the change (https://gerrit.wikimedia.org/r/#/c/321374/)
- run puppet on maps-test2001
- test, check, ...
- run puppet on all maps servers
- deploy kartotherian on all maps servers
@Yurik does this look good to you? Can we try to deploy that on Monday 21st?
Change 321376 merged by Gehel:
Kartotherian: deploy application configuration with scap3
Test deployment on maps-test2001 done, with manually generated config-vars.yaml file. The part in the kartotherian-deploy repo seems to be working just fine, diff shows only minor formatting differences with current config file. Changes to kartotherian-deploy repo have been reverted for the moment.
The full test will be during actual deployment, with the puppet changes as well, but I understand those much better than I understand the scap3 part.
Change 324073 had a related patch set uploaded (by Gehel):
Kartotherian: deploy application configuration with scap3
Change 321375 abandoned by Gehel:
Kartotherian: deploy application configuration with scap3
Reason:
All changes related to kartotherian config deplyoment are merged in a single commit
Change 324073 merged by Gehel:
Kartotherian: deploy application configuration with scap3
Mentioned in SAL (#wikimedia-operations) [2016-11-29T13:54:02Z] <gehel> deploying kartotherian config with scap3 - T150021
Change 321374 merged by Gehel:
Kartotherian: deploy application configuration with scap3
Change 324185 had a related patch set uploaded (by Gehel):
kartotherian : deploy config with scap3
Change 324187 had a related patch set uploaded (by Gehel):
Kartotherian - deploy config with scap3
Main config file for kartotherian is now deployed via scap3. Same work now needs to be done for tilerator / tileratorui.
Change 324190 had a related patch set uploaded (by Gehel):
node service - allow empty entry point
Change 324760 had a related patch set uploaded (by Gehel):
tilerator - deplyo config with scap3
Change 324761 had a related patch set uploaded (by Gehel):
tilerator: deploy config with scap3