Project

General

Profile

Bug #11680

Upgrade server hardware (2017-2019 edition)

Added by Dr_Whax almost 2 years ago. Updated 3 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
09/19/2016
Due date:
% Done:

67%

QA Check:
Feature Branch:
Type of work:
Sysadmin

Description

team: intrigeri, bertagaz

This includes:

  • storage: update the spreadsheet we did for #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 2017Resolved

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

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


Related issues

Related to Tails - Feature #10851: Give lizard enough free storage to host our freezable APT repository Resolved 01/04/2016
Related to Tails - Feature #14601: Know which ressources we would need to run Matomo on our infrastructure Confirmed 09/04/2017

Associated revisions

Revision e90aa56f (diff)
Added by intrigeri over 1 year ago

Add notes about next server hardware iteration (refs: #11680).

Mostly so that my thoughts about using the cloud are not only stored
in 2 people's email INBOX.

Revision b8dabe57 (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: update all the things! (refs: #11680)

- Update the problem statement with more recent usage+performance data and to
match the fact we've already deployed the reproducible builds CI changes we
wanted.
- Mention upcoming needs for non-CI services.
- Entirely revamp the cloud section to be based on a hypothesis that can
possibly work, and discuss some of the potentially hard problems.

Revision 80c51879 (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: cons++ (refs: #11680)

Revision 444b510f (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: cons++ (refs: #11680)

Revision 46f7208d (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: add more performance data (refs: #11680)

Revision 7f3f8a80 (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: drop a potential issue (refs: #11680)

According to our data, our ISO builds are not slower recently than they were
before we switched to Vagrant, go figure. But we've lost the data from the
months immediately before the switch, so it's hard to tell whether I'm comparing
apples and oranges or what. Also, I guess we probably optimized other stuff
which compensates the nested virtualization overhead. Now it's too late to
measure the difference between the old & new setups when doing the exact same
job, so let's just give up.

Revision 6f3889b5 (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: minor rephrasing (refs: #11680)

Revision 5df8af36 (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: document next steps (refs: #11680)

Revision 6866f2ad (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: add Weblate (refs: #11680)

Revision df7d14da (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: this option can be a first step (refs: #11680)

Revision b5b56a0e (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: give examples of bare metal that would work (refs: #11680)

Revision ffd9fc5e (diff)
Added by intrigeri 7 months ago

Next server hardware iteration: update options & plans (refs: #11680)

History

#1 Updated by intrigeri almost 2 years ago

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

#2 Updated by intrigeri almost 2 years ago

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

#3 Updated by intrigeri almost 2 years ago

  • Description updated (diff)

#4 Updated by intrigeri over 1 year ago

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

#5 Updated by intrigeri about 1 year ago

  • Target version changed from 2017 to Tails_3.2

I want to start working on this once the migration to Stretch (#12160) is over, and before I start working on Puppet 4 (#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 about 1 year ago

  • Blocks Feature #13284: Core work 2017Q2→2019Q1: Sysadmin (Adapt our infrastructure) added

#7 Updated by intrigeri 12 months ago

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

#8 Updated by intrigeri 12 months ago

  • Target version changed from Tails_3.2 to Tails_3.3

I don't think I can do more than #11808 and #12160 in September, and this is blocked by #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 11 months ago

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

#10 Updated by intrigeri 9 months ago

  • 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 8 months ago

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

#12 Updated by intrigeri 8 months ago

intrigeri wrote:

this is blocked by #13436 that probably won't be done before mid-November => postponing.

Enough has been done on #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 #11834.

#13 Updated by intrigeri 7 months ago

  • Status changed from Confirmed to In Progress

#14 Updated by intrigeri 7 months ago

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

#15 Updated by intrigeri 7 months ago

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

#16 Updated by intrigeri 7 months ago

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 :)

#17 Updated by intrigeri 6 months ago

  • Target version changed from Tails_3.5 to Tails_3.8

I probably won't come back to this topic before May or June.

#18 Updated by intrigeri 3 months ago

  • Blocks deleted (Feature #13284: Core work 2017Q2→2019Q1: Sysadmin (Adapt our infrastructure))

#19 Updated by intrigeri 3 months ago

  • Target version deleted (Tails_3.8)

(I've created #15501 to track the part that's on our roadmap this year.)

Also available in: Atom PDF