Feature #15501

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

Added by intrigeri 2018-04-08 13:01:11 . Updated 2019-08-09 17:03:24 .

Status:
Resolved
Priority:
Elevated
Assignee:
intrigeri
Category:
Infrastructure
Target version:
Start date:
2018-04-08
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Starter:
Affected tool:
Deliverable for:

Description


Subtasks


Related issues

Blocks Tails - Feature #13284: Core work: Sysadmin (Adapt our infrastructure) Confirmed 2017-06-30
Precedes Tails - Bug #16960: Make our CI feedback loop shorter In Progress

History

#1 Updated by intrigeri 2018-04-08 13:01:27

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

#2 Updated by intrigeri 2018-04-08 13:33:36

  • blocked by Bug #10068: Upgrade to Jenkins 2.x, using upstream packages added

#3 Updated by intrigeri 2018-11-05 14:45:47

  • Target version changed from Tails_3.11 to Tails_3.12

#4 Updated by intrigeri 2018-12-01 16:26:23

  • Status changed from Confirmed to In Progress

Applied in changeset commit:tails|38743447d32cbc47c3f32ba4694aba24b9ed1a2a.

#5 Updated by intrigeri 2018-12-01 16:41:12

  • blocks deleted (Bug #10068: Upgrade to Jenkins 2.x, using upstream packages)

#6 Updated by intrigeri 2018-12-01 20:38:09

Updated list of upcoming services and CI infra perf stats, drafted hardware specs for the “Bare metal server dedicated to CI” option.

#7 Updated by intrigeri 2018-12-17 17:08:27

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

#8 Updated by intrigeri 2018-12-30 13:21:10

  • related to #16040 added

#9 Updated by intrigeri 2019-01-02 05:03:11

  • Target version changed from Tails_3.12 to Tails_3.13

#10 Updated by intrigeri 2019-02-15 16:43:55

I’ll benchmark hardware for the “hacker option” once I’ve received it, hopefully during the 3.13 dev cycle, and definitely by the end of 2019Q2.

#11 Updated by intrigeri 2019-03-04 10:10:58

  • % Done changed from 0 to 20

Reported initial benchmarking results and next things I want to try: https://tails.boum.org/blueprint/hardware_for_automated_tests_take3/#hacker-option-benchmark

#12 Updated by intrigeri 2019-03-17 08:43:46

  • Target version changed from Tails_3.13 to Tails_3.14

#13 Updated by intrigeri 2019-05-02 17:25:19

  • Priority changed from Normal to Elevated

#14 Updated by intrigeri 2019-05-08 09:20:09

  • Status changed from In Progress to Resolved
  • % Done changed from 20 to 100

Applied in changeset commit:tails|f86a21bd028be724b0d8dbe06415cf9fcce09eba.

#15 Updated by intrigeri 2019-05-08 09:23:57

I’ve completed my analysis of the “hacker option”. My conclusions are on https://tails.boum.org/blueprint/hardware_for_automated_tests_take3/#hacker-option-benchmark. Reviews & feedback welcome :)

#16 Updated by intrigeri 2019-05-08 09:31:24

I’ve overclocked by +33% on this one, so the next part of the analysis for the hacker option (power consumption, hosting requirements) will be for later.

And I still want to get in touch with ProfitBricks, that donate crazy amounts of VM “hardware” to the Reproducible Builds project. If they’re happy to give us some, this would be, by far, the simplest and cheapest option. AFAIK that’s a simple “here’s a VM, you’re root” setup so it does not have the drawbacks of more powerful & complex cloud systems, apart of course the fact we don’t run the hardware ourselves.

#17 Updated by intrigeri 2019-08-09 17:02:12

  • precedes Bug #16960: Make our CI feedback loop shorter added

#18 Updated by intrigeri 2019-08-09 17:03:24

See you on Bug #16960.