Feature #6185
Failover for lizard
Start date:
2013-07-24
Due date:
% Done:
100%
Starter:
0
Affected tool:
Deliverable for:
Description
Team: bertagaz, intrigeri
Subtasks
| Feature #6186: Specify system requirements for lizard failover | Resolved | intrigeri | 0 |
||
| Feature #6190: Ask TTP if they have capacity to host lizard failover | Resolved | intrigeri | 0 |
||
| Feature #6191: Ask a VM to tachanka for lizard failover | Resolved | 0 |
|||
| Feature #6249: Get access to the new VM | Resolved | intrigeri | 100 |
||
| Feature #6250: Configure the lizard failover | Rejected | intrigeri | 20 |
||
| Feature #10243: Update system requirements for lizard failover | Resolved | 100 |
|||
| Feature #10244: Research and decide where to host the lizard failover | Rejected | bertagaz | 20 |
History
#1 Updated by intrigeri 2013-07-25 04:17:18
- 20GB of disk space, and growing (will jump to a few dozens GB once we distribute source packages (
Feature #5987) and get ourselves a freezable APT repo (Feature #5926)). - low CPU usage
- 1GB of RAM should be enough
- datacenter-class bandwidth
#2 Updated by intrigeri 2013-12-29 03:23:42
- Category set to Infrastructure
#3 Updated by sajolida 2014-11-03 21:36:06
- Target version set to Sustainability_M1
#4 Updated by sajolida 2015-08-14 11:49:03
- Description updated
#5 Updated by sajolida 2015-09-07 10:53:43
- Target version changed from Sustainability_M1 to 2016
#6 Updated by intrigeri 2015-09-25 07:41:56
- Blueprint set to https://tails.boum.org/blueprint/lizard_failover/
#9 Updated by intrigeri 2015-09-29 07:06:54
See updated specs on the blueprint.
#10 Updated by BitingBird 2016-06-26 11:04:39
- Status changed from Confirmed to In Progress
#11 Updated by Dr_Whax 2016-08-20 12:57:14
- Target version changed from 2016 to 2017
#12 Updated by BitingBird 2017-08-26 17:18:57
- Status changed from In Progress to Rejected
We budgeted money to replace lizard in a hurry if it fails, instead.