|
|
This is about [[!tails_ticket 16960]] and related tickets.
|
|
|
This is about tails/tails#16960 and related tickets.
|
|
|
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
[[!toc levels=3]]
|
|
|
|
|
|
# Rationale
|
|
|
|
|
|
In 2016 we gave our main server some more RAM, as a temporary solution
|
|
|
to cope with our workload, and as a way to learn about how to scale
|
|
|
it. See [[blueprint/hardware_for_automated_tests_take2]] for our
|
|
|
it. See [hardware for automated tests take2](hardware_for_automated_tests_take2) for our
|
|
|
reasoning, lots of benchmark results, and conclusions.
|
|
|
|
|
|
It's working relatively well so far, but we may need to upgrade again
|
... | ... | @@ -21,7 +23,7 @@ area: |
|
|
* When Jenkins has built an ISO from one of our main branches or from
|
|
|
a branch that _Needs Validation_, since October 2017 we rebuild in
|
|
|
in a slightly different build environment to ensure it can be
|
|
|
[[rebuilt reproducibly|blueprint/reproducible_builds]].
|
|
|
[rebuilt reproducibly](reproducible_builds).
|
|
|
This increased substantially the number of ISO image we build
|
|
|
which sometimes creates congestion in our CI pipeline (see below
|
|
|
for details).
|
... | ... | @@ -103,10 +105,10 @@ area: |
|
|
task performance limitations described above.
|
|
|
- survey platform
|
|
|
- Under consideration:
|
|
|
- [[!tails_ticket 14601 desc="Matomo"]] will require huge amounts
|
|
|
- Matomo (tails/tails#14601) will require huge amounts
|
|
|
of resources and put quite some load on the system where we run
|
|
|
it; it needs to be hosted on hardware we control.
|
|
|
- [[!tails_ticket 9960 desc="Request tracker for help desk"]]):
|
|
|
- Request tracker for help desk (tails/tails#9960)):
|
|
|
unknown resources requirements; needs to be hosted on hardware
|
|
|
we control.
|
|
|
- WIP and will need more resources once they reach production
|
... | ... | @@ -148,7 +150,7 @@ Extra options: |
|
|
|
|
|
* If we want to drop nested virtualization to get more performance,
|
|
|
then we have non-negligible development costs and hard sysadmin
|
|
|
problems to solve ([[!tails_ticket 9486]]):
|
|
|
problems to solve (tails/tails#9486):
|
|
|
- We currently _reboot_ isotesters between test suite runs ⇒ if we
|
|
|
go this way we need to learn how to clean up after various kinds
|
|
|
of test suite failure.
|
... | ... | @@ -260,9 +262,9 @@ Cons: |
|
|
* Intel: in the ninth generation NUC9i7 (availability: 2020Q1),
|
|
|
NUC9V7QNX is the one that supports vPro
|
|
|
* Other vendors have started selling UCFF boards/kits with fast CPUs.
|
|
|
* Similar smallish [[!wikipedia Computer_form_factor desc="form
|
|
|
factors"]] would be worth investigating, e.g. there are plenty of
|
|
|
[[!wikipedia Mini-ITX]] options on the market that could give us
|
|
|
* Similar smallish [form
|
|
|
factors](https://en.wikipedia.org/wiki/Computer%5Fform%5Ffactor) would be worth investigating, e.g. there are plenty of
|
|
|
[Mini-ITX](https://en.wikipedia.org/wiki/Mini%2DITX) options on the market that could give us
|
|
|
the high density we need.
|
|
|
- [Supermicro X11SCL-IF](https://www.supermicro.com/products/motherboard/X11/X11SCL-iF.cfm), $200
|
|
|
+ <https://www.intel.com/content/www/us/en/products/processors/xeon/e-processors.html?Intel+Technology=900393> 300€
|
... | ... | @@ -322,7 +324,7 @@ testing but this is not what we have set up on lizard at the moment: |
|
|
there's a risk that a failed test job leaves the system in a bad shape
|
|
|
and breaks the following build job as we don't reboot after build
|
|
|
jobs. We might need to either make test jobs more robust on failure
|
|
|
([[!tails_ticket 17216]]),
|
|
|
(tails/tails#17216),
|
|
|
or to start rebooting the Jenkins slaves after build jobs as well.
|
|
|
|
|
|
To utilize more fully such nodes, we may need to raise the number of
|
... | ... | @@ -427,7 +429,7 @@ Cons: |
|
|
- builds & tests:
|
|
|
(30 minutes/build * 450 builds/month + 105 minutes/test * 350 tests/month)
|
|
|
/ 60 * 0.173€ = 145€/month
|
|
|
- second build for reproducibility ([[!tails_ticket 13436]]):
|
|
|
- second build for reproducibility (tails/tails#13436):
|
|
|
30 minutes / 60 * 250 builds/month * 0.173€ = 22€/month
|
|
|
- total = 167€/month
|
|
|
|
... | ... | @@ -584,3 +586,4 @@ Cons: |
|
|
is ready, and ask friendly potential cloud providers such as
|
|
|
universities, HPC cluster admins, etc.</strike> [CANCELED: we won't do
|
|
|
cloud]
|
|
|
|