View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005485 | Taler | deployment and operations | public | 2018-11-26 11:56 | 2019-06-24 21:38 |
| Reporter | Florian Dold | Assigned To | Marcello Stanisci | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Summary | 0005485: periodic deployment health checks | ||||
| Description | We should have periodic health checks running for all services. If one of them fails, we should receive emails about it. Specifically we should at least 1. have very simple curl-based checks run periodically by buildbot 2. update/fix and re-enable the selenium-based tests once we're on the new server We also may think about running taler-exchange-benchmark against the live exchange periodically, with only a small number of transactions to not overwhelm the system. Eventually, we also might want a taler-merchant-benchmark that (in addition to testing the merchant's performance) periodically runs transactions (including tipping!) against the live merchant. | ||||
| Tags | No tags attached. | ||||
| Given the last reports from users, we should make sure the health-checks run on the 'demo' deployment too. | |
| The sanity checks should also make sure that Postgresql and nginx (and all the corollary services) are running, and TLS certificates are valid. | |
| @13366, exists: https://buildbot.taler.net/#/builders/4 | |
| Closing because: 1) Demo services *are* checked by the Buildbot (via Curl, see [1]). 2) Benchmarks-driven tests will be replaced by the headless wallet. 3) No reason to keep this open just for the far-fetched Selenium-based tests. If need be, we'll open a dedicate issue for that. 4) What says note 13511 does not apply here. [1] https://git.taler.net/deployment.git/tree/buildbot/checks.sh?id=72adb0fdd752978cf89301a102880cfac3fa40cc | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-11-26 11:56 | Florian Dold | New Issue | |
| 2018-11-26 12:13 | Marcello Stanisci | Note Added: 0013366 | |
| 2019-01-29 12:34 | Marcello Stanisci | Note Added: 0013511 | |
| 2019-01-31 18:16 | Christian Grothoff | Severity | minor => feature |
| 2019-06-24 16:40 | Marcello Stanisci | Note Added: 0014576 | |
| 2019-06-24 21:29 | Marcello Stanisci | Note Added: 0014585 | |
| 2019-06-24 21:29 | Marcello Stanisci | Note Edited: 0014585 | |
| 2019-06-24 21:30 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2019-06-24 21:30 | Marcello Stanisci | Status | new => closed |
| 2019-06-24 21:30 | Marcello Stanisci | Resolution | open => no change required |
| 2019-06-24 21:38 | Marcello Stanisci | Note Edited: 0014585 |