Feature #6250
Configure the lizard failover
Start date:
2013-08-22
Due date:
% Done:
20%
Description
Once we have our hands in the new machine, we have to setup all the services it is supposed to run.
Subtasks
Related issues
Blocked by Tails - |
Resolved | 2013-08-22 | |
Blocked by Tails - |
Rejected | 2015-09-25 | |
Blocked by Tails - |
Resolved | 2015-12-15 |
History
#1 Updated by BitingBird 2014-06-22 15:41:36
- Description updated
#2 Updated by bertagaz 2015-09-02 02:53:49
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 20
The base system has been installed at the end of last week. It’s now waiting to take some decisions regarding the way we’ll manage the services there.
#3 Updated by intrigeri 2015-09-25 07:33:28
- blocked by
Feature #10244: Research and decide where to host the lizard failover added
#4 Updated by intrigeri 2015-09-25 07:34:22
- Target version set to 2016
bertagaz wrote:
> The base system has been installed at the end of last week. It’s now waiting to take some decisions regarding the way we’ll manage the services there.
We’re waiting to find out if that VM is still up to the task 2 years later (Feature #10243) and to draw conclusions about it (Feature #10244).
#5 Updated by intrigeri 2015-09-25 08:13:30
- blocked by
Feature #10245: Decide how to manage systems outside of lizard added
#6 Updated by intrigeri 2015-12-15 12:21:34
- blocked by
Feature #10760: Decide how to manage ecours and other systems with Puppet added
#7 Updated by intrigeri 2015-12-15 12:23:11
- blocks deleted (
)Feature #10245: Decide how to manage systems outside of lizard
#8 Updated by intrigeri 2015-12-15 12:24:00
- Description updated
#9 Updated by BitingBird 2016-06-26 11:07:36
- Assignee set to intrigeri
#10 Updated by intrigeri 2016-08-27 10:01:37
- Target version changed from 2016 to 2017
#11 Updated by intrigeri 2016-08-27 10:49:08
- Target version deleted (
2017)
#12 Updated by BitingBird 2017-08-26 17:18:04
- Status changed from In Progress to Rejected