Feature #8646

Research and decide where to host the monitoring software

Added by intrigeri 2015-01-09 17:13:01 . Updated 2015-10-05 08:21:24 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2015-01-09
Due date:
% Done:

100%

Feature Branch:
Type of work:
Research
Starter:
Affected tool:
Deliverable for:
268

Description


Subtasks


Related issues

Related to Tails - Feature #10244: Research and decide where to host the lizard failover Rejected 2015-09-25
Blocks Tails - Feature #8647: Install an OS on the machine that will host the production monitoring setup Resolved 2015-12-15
Blocked by Tails - Feature #8649: Specify our monitoring needs and build an inventory of the services that need monitoring Resolved 2015-01-09

History

#1 Updated by intrigeri 2015-01-09 17:13:15

  • blocked by Feature #8645: Research and decide what monitoring solution to use added

#2 Updated by intrigeri 2015-01-09 17:13:56

  • blocks Feature #8647: Install an OS on the machine that will host the production monitoring setup added

#3 Updated by Dr_Whax 2015-05-26 21:55:49

  • Assignee changed from bertagaz to Dr_Whax

#4 Updated by intrigeri 2015-05-27 06:05:06

  • blocks #8668 added

#5 Updated by intrigeri 2015-05-28 14:14:16

  • blocked by Feature #8649: Specify our monitoring needs and build an inventory of the services that need monitoring added

#6 Updated by intrigeri 2015-05-28 14:15:04

Specs will be on the blueprint created as part of Feature #8649.

#7 Updated by intrigeri 2015-05-28 14:48:51

  • Target version changed from Tails_1.8 to Tails_1.5

#8 Updated by intrigeri 2015-05-28 14:50:01

  • Target version changed from Tails_1.5 to Tails_1.6

#9 Updated by intrigeri 2015-05-28 19:59:12

  • Blueprint set to https://tails.boum.org/blueprint/monitor_servers/

There’s a section about hosting on the blueprint. DrWhax, please check it carefully and see if anything in there is wrong, unclear, missing, etc.

#10 Updated by Dr_Whax 2015-07-07 12:26:37

  • Target version changed from Tails_1.6 to Tails_1.5

#11 Updated by Dr_Whax 2015-07-18 14:32:19

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

The discussion was started to the relevant e-mail list and people.

#12 Updated by Dr_Whax 2015-08-13 11:02:56

  • Target version changed from Tails_1.5 to Tails_1.6

After some brainstorming of where we would like to host this machine. I send a e-mail to the first group on the list. I haven’t heard back yet. Hence why i’m postponing.

#13 Updated by intrigeri 2015-08-18 05:32:48

> After some brainstorming of where we would like to host this machine. I send a e-mail to the first group on the list.

I suggest emailing several of them at once (making it clear to them that you’re asking to several groups).

#15 Updated by bertagaz 2015-09-23 01:32:19

  • Target version changed from Tails_1.6 to Tails_1.7

#16 Updated by intrigeri 2015-09-25 07:33:05

  • related to Feature #10244: Research and decide where to host the lizard failover added

#17 Updated by intrigeri 2015-09-25 07:35:59

I could not find the system requirements for that machine. Where are they documented?

#18 Updated by Dr_Whax 2015-09-26 05:32:40

Requirements, depending on how long we want to store data.

1 CPU core.
512MB ram.
30GB of data.

#19 Updated by intrigeri 2015-09-26 07:29:10

  • Assignee changed from Dr_Whax to intrigeri

We’ll know more about this at the end of next week. And then, depending on the info we’ll have we should see how to go on, how much time it can take, and who will handle it.

#20 Updated by intrigeri 2015-09-26 07:33:39

Dr_Whax wrote:
> 30GB of data.

We’ll see after Feature #8652. 20GB could probably be fine.

#21 Updated by intrigeri 2015-10-05 08:20:19

  • blocks deleted (Feature #8645: Research and decide what monitoring solution to use)

#22 Updated by intrigeri 2015-10-05 08:21:24

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 10 to 100

We’ll use our VM at tachanka, since it finally won’t be used for its initial purpose.