Tracking task for creating a canary deploy process in response to next steps identified in https://wikitech.wikimedia.org/wiki/Incident_documentation/20160601-MediaWiki
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | thcipriani | T136883 Create canary deploy process for MediaWiki | |||
| Resolved | None | T136886 Create ability to deploy-to and run-checks-on canary for MediaWiki deploys | |||
| Resolved | • mobrovac | T136839 Create a script to run test requests for the MediaWiki service | |||
| Resolved | None | T110068 Basic scap{2,3} canary deployment process & checks | |||
| Resolved | dduvall | T109515 Scap3 should support post-deploy checks | |||
| Resolved | mmodell | T114284 Implement nrpe config parser to easily hook into Puppet managed checks | |||
| Resolved | thcipriani | T121597 Implement MediaWiki pre-promote checks | |||
| Resolved | fgiunchedi | T204383 Update Debian Package for Scap to 3.8.7-1 |
Event Timeline
Comment Actions
For MediaWiki we are currently running a basic swagger check to check responses for a small number of endpoints, and a logstash check to monitor drastic changes in the error rate for logs during for each deployment. Scap3 deployments provide a mechanism for repository maintainers to write and run their own checks as well as respond to nrpe checks.
I think we have the basics of a canary process for both MediaWiki and scap3 deploys of other repositories and services. Calling this resolved.