Feature #5734
Monitor servers
Start date:
2015-01-09
Due date:
2015-11-09
% Done:
100%
Description
As our infrastructure grows and more users and contributors rely on it, we need to monitor it, in order to guarantee more availability, reliability, and integrity of our services.
Subtasks
Feature #8645: Research and decide what monitoring solution to use | Resolved | 100 |
|||
Feature #8646: Research and decide where to host the monitoring software | Resolved | 100 |
|||
Feature #8647: Install an OS on the machine that will host the production monitoring setup | Resolved | 100 |
|||
Feature #8649: Specify our monitoring needs and build an inventory of the services that need monitoring | Resolved | 100 |
|||
Feature #8651: Configure the receiving side of the monitoring notifications | Resolved | 100 |
|||
Feature #9480: Set up a VM for monitoring tools experiments | Resolved | 100 |
|||
Feature #9481: Reset the VM used for monitoring tools experiments to a clean state | Resolved | 100 |
|||
Feature #9482: Create a monitoring setup prototype | Resolved | 100 |
|||
Feature #9483: Puppetize the monitoring setup prototype | Rejected | 100 |
|||
Feature #9484: Deploy the monitoring setup to production | Resolved | 100 |
|||
Feature #9485: Update the local dev environment to replicate our monitoring setup | Rejected | 100 |
|||
Feature #10886: Reset the VM used for monitoring tools experiments | Resolved | 100 |
|||
Feature #11094: Deploy a VPN between the monitoring host and Lizard | Resolved | 100 |
History
#1 Updated by intrigeri 2013-07-25 06:17:58
- Subject changed from monitor services to monitor server services
- Starter set to No
#2 Updated by intrigeri 2013-07-25 06:18:10
- Subject changed from monitor server services to monitor servers
#3 Updated by intrigeri 2013-10-04 06:47:21
- Category set to Infrastructure
#4 Updated by BitingBird 2014-07-01 12:08:40
- Subject changed from monitor servers to Monitor servers
#5 Updated by intrigeri 2015-01-09 17:10:04
- Target version changed from Sustainability_M1 to Tails_1.8
#7 Updated by intrigeri 2015-01-09 17:10:39
- Description updated
#8 Updated by intrigeri 2015-05-28 14:09:43
- blocks #8668 added
#9 Updated by intrigeri 2015-05-28 14:48:38
- Assignee set to bertagaz
#10 Updated by intrigeri 2015-08-26 05:57:01
- Deliverable for set to 268
#11 Updated by bertagaz 2015-12-15 03:37:19
- Target version changed from Tails_1.8 to Tails_2.0
Postponing
#13 Updated by bertagaz 2016-01-06 15:10:13
- Target version changed from Tails_2.0 to Tails_2.2
- Deliverable for changed from 268 to 269
Postponing this part of the monitoring setup, as it will be unlikely done for the previously planed deadline given some subtasks are also postponed
#14 Updated by bertagaz 2016-01-06 15:20:58
- Deliverable for changed from 269 to 268
#15 Updated by bertagaz 2016-02-05 20:46:52
- Target version changed from Tails_2.2 to Tails_2.3
#16 Updated by bertagaz 2016-04-26 04:59:31
- Target version changed from Tails_2.3 to Tails_2.4
#17 Updated by intrigeri 2016-04-26 06:08:54
- blocked by deleted (
#8668)
#18 Updated by intrigeri 2016-05-10 05:34:40
- blocked by
Feature #11366: Document our monitoring setup added
#19 Updated by intrigeri 2016-06-05 13:34:40
- Target version changed from Tails_2.4 to Tails_2.5
(Some subtasks are for 2.5 already.)
#20 Updated by BitingBird 2016-06-26 11:08:01
- Status changed from Confirmed to In Progress
#21 Updated by intrigeri 2016-07-23 06:38:58
- Status changed from In Progress to Resolved
- Assignee deleted (
bertagaz) - QA Check set to Pass
Last blocker resolved, we’re done here. Great job, thank you!
#22 Updated by sajolida 2016-08-01 05:29:35
Congrats!