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

Feature #10244

Research and decide where to host the lizard failover

Added by intrigeri 2015-09-25 07:32:33 . Updated 2017-08-26 17:16:53 .

Status:

Rejected

Priority:

Normal

Assignee:

bertagaz

Category:

Infrastructure

Target version:

Start date:

2015-09-25

Due date:

% Done:

20%

Feature Branch:

Type of work:

Sysadmin

Blueprint:

Starter:

Affected tool:

Deliverable for:

Description

Once we have updated specs (~~Feature #10243~~) we can find a place to host it. Take into account that we already have an unused VM at tachanka, TTP may be able to host something for us now, and we need another system for monitoring (~~Feature #8646~~).

Subtasks

Related issues

Related to Tails - ~~Feature #8646~~: Research and decide where to host the monitoring software	Resolved	2015-01-09
Blocked by Tails - ~~Feature #10243~~: Update system requirements for lizard failover	Resolved	2015-09-25
Blocks Tails - ~~Feature #6250~~: Configure the lizard failover	Rejected	2013-08-22

History

#1 Updated by intrigeri 2015-09-25 07:32:41

Parent task set to ~~Feature #6185~~

#2 Updated by intrigeri 2015-09-25 07:32:53

blocked by ~~Feature #10243~~: Update system requirements for lizard failover added

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

related to ~~Feature #8646~~: Research and decide where to host the monitoring software added

#4 Updated by intrigeri 2015-09-25 07:33:28

blocks ~~Feature #6250~~: Configure the lizard failover added

#5 Updated by intrigeri 2015-09-30 08:33:17

Assignee set to bertagaz

bertagaz has the up-to-date info and will report back + email the hoster we’ve picked. I think this should have a milestone less far in the future, e.g. 1.8.

#6 Updated by bertagaz 2015-09-30 08:55:30

Target version changed from 2016 to Tails_1.7

Agree, I even made it earlier, given we made quite good progress. Will report later.

#7 Updated by intrigeri 2015-10-14 01:15:11

Status changed from Confirmed to In Progress
% Done changed from 0 to 20

#8 Updated by bertagaz 2015-11-03 02:23:44

Priority changed from Normal to Elevated
Target version changed from Tails_1.7 to Tails_1.8

Postponing and raising priority.

#9 Updated by bertagaz 2015-12-15 03:36:29

Target version changed from Tails_1.8 to Tails_2.0

Postponing

#10 Updated by bertagaz 2016-01-06 13:17:11

Target version changed from Tails_2.0 to Tails_2.2

Already have to work on the monitoring host, so postponing this other new machine ticket.

#11 Updated by bertagaz 2016-03-10 18:51:05

Target version changed from Tails_2.2 to Tails_2.3

#12 Updated by bertagaz 2016-04-23 06:27:32

Target version changed from Tails_2.3 to Tails_2.4

#13 Updated by bertagaz 2016-06-07 12:31:32

Target version changed from Tails_2.4 to Tails_2.5

#14 Updated by bertagaz 2016-07-19 04:17:22

Target version changed from Tails_2.5 to Tails_2.6

#15 Updated by anonym 2016-09-20 16:53:35

Target version changed from Tails_2.6 to Tails_2.7

#16 Updated by bertagaz 2016-09-22 05:31:56

Target version changed from Tails_2.7 to Tails_2.9.1

#17 Updated by bertagaz 2016-10-27 14:04:50

Had a discussion with the cool guy that agreed to host it during a Tor dev meeting. Seems like things are settling for his project, so he offered to go forward setting up the system. I’ll send him by email the specifications we drafted in the coming weeks, so that he can start putting things in place on his side.

#18 Updated by intrigeri 2016-10-27 16:06:03

> Had a discussion with the cool guy that agreed to host it during a Tor dev meeting. Seems like things are settling for his project, so he offered to go forward setting up the system. I’ll send him by email the specifications we drafted in the coming weeks, so that he can start putting things in place on his side.

Cool. Did you discuss pricing?