Bug #11680: Upgrade server hardware (2017-2019 edition)

Bug #11680

Upgrade server hardware (2017-2019 edition)

Added by Dr_Whax 2016-08-20 12:55:53 . Updated 2019-08-09 17:01:57 .

Status:

Resolved

Priority:

Normal

Assignee:

intrigeri

Category:

Infrastructure

Target version:

2019

Start date:

2016-09-19

Due date:

% Done:

100%

Feature Branch:

Type of work:

Sysadmin

Blueprint:

https://tails.boum.org/blueprint/hardware_for_automated_tests_take3/

Starter:

Affected tool:

Deliverable for:

Description

This includes:

storage: update the spreadsheet we did for ~~Feature #10851~~ and draw conclusions wrt. how much more storage we need to add
reproducible builds’ needs
running the test suite on bare metal?
asking server hardware sponsorship or discount to hardware vendors?
using the cloud?

Subtasks

Feature #11806: Update server storage planning needs for at least 2017

Resolved

100

Bug #13425: Upgrade lizard's storage (2017 edition)

Resolved

100

Feature #15501: Server hardware (2017-2019 edition): evaluate some of the options

Resolved

intrigeri

100

Feature #15780: Update server storage planning needs for 2019-2020

Rejected

100

Related issues

Related to Tails - ~~Feature #10851~~: Give lizard enough free storage to host our freezable APT repository	Resolved	2016-01-04
Related to Tails - ~~Feature #14601~~: Know which ressources we would need to run Matomo on our infrastructure	Rejected	2017-09-04
Related to Tails - Bug #16960: Make our CI feedback loop shorter	In Progress

History

#1 Updated by intrigeri 2016-09-19 03:37:32

Subject changed from Upgrade server hardware to Upgrade server hardware (2017 edition)

#2 Updated by intrigeri 2016-09-19 03:37:49

related to ~~Feature #10851~~: Give lizard enough free storage to host our freezable APT repository added

#3 Updated by intrigeri 2016-09-19 03:39:30

Description updated

#4 Updated by intrigeri 2017-03-03 19:19:47

Blueprint set to https://tails.boum.org/blueprint/hardware_for_automated_tests_take3/

#5 Updated by intrigeri 2017-06-05 13:42:12

Target version changed from 2017 to Tails_3.2

I want to start working on this once the migration to Stretch (~~Feature #12160~~) is over, and before I start working on Puppet 4 (~~Feature #11834~~). So I should start making serious progress in September, initially aiming at completing it by the end of November. So putting it on my September radar.

#6 Updated by intrigeri 2017-06-30 11:21:28

blocks Feature #13284: Core work: Sysadmin (Adapt our infrastructure) added

#7 Updated by intrigeri 2017-07-30 08:32:21

blocked by ~~Feature #13436~~: Have Jenkins jobs that reproduce ISOs when a branch ticket is Ready for QA added

#8 Updated by intrigeri 2017-07-30 08:52:27

Target version changed from Tails_3.2 to Tails_3.3

I don’t think I can do more than ~~Bug #11808~~ and ~~Feature #12160~~ in September, and this is blocked by ~~Feature #13436~~ that probably won’t be done before mid-November => postponing.

Tentatively scheduled some time on December 18-20 to better define the problems we need to solve, and refine the options we have (e.g. add actual cost and performance estimates).

#9 Updated by intrigeri 2017-09-05 08:17:17

related to ~~Feature #14601~~: Know which ressources we would need to run Matomo on our infrastructure added

#10 Updated by intrigeri 2017-10-22 13:11:29

Target version changed from Tails_3.3 to Tails_3.5

(Next step described above is in December, that is after 3.3.)

#11 Updated by intrigeri 2017-11-28 09:25:29

blocks deleted (~~~~Feature #13436~~: Have Jenkins jobs that reproduce ISOs when a branch ticket is Ready for QA~~)

#12 Updated by intrigeri 2017-11-28 09:29:02

intrigeri wrote:
> this is blocked by ~~Feature #13436~~ that probably won’t be done before mid-November => postponing.

Enough has been done on ~~Feature #13436~~ to unblock this work :)

> Tentatively scheduled some time on December 18-20 to better define the problems we need to solve, and refine the options we have (e.g. add actual cost and performance estimates).

We’ve scheduled a sprint at the same time so I doubt I can do all of that this during the 3.5 dev cycle. But at least I want to identify the needs (e.g. get fresh stats about how long our feedback loop is) so I can discuss with my team-mates how I should prioritize this, e.g. whether I should first focus on this or on ~~Feature #11834~~.

#13 Updated by intrigeri 2017-12-17 12:12:22

Status changed from Confirmed to In Progress

Applied in changeset commit:b8dabe57a67174572c7a497607515c5f50e1146d.

#14 Updated by intrigeri 2017-12-20 06:23:43

Subject changed from Upgrade server hardware (2017 edition) to Upgrade server hardware (2017-2019 edition)

#15 Updated by intrigeri 2017-12-20 06:24:19

We now have a plan for the next steps, that I’ll document soon.

#16 Updated by intrigeri 2017-12-22 07:43:08

intrigeri wrote:
> We now have a plan for the next steps, that I’ll document soon.

Done: https://tails.boum.org/blueprint/hardware_for_automated_tests_take3/#plan (and updated the blueprint with the notes I took during the discussion we had about this topic at the sysadmin sprint). For now I won’t bother tracking the next steps as subtasks, let’s keep the blueprint updated instead. I’ll try to tackle some of them during the 3.5 cycle but there’s no big hurry. Dear team-mates, feel free to take some of the other tasks if you want and write your name on the blueprint :)