This page documents the requirements we have for worker hosts to be added to the https://ci.debian.net fleet.
To keep things manageable we prefer one or two big hosts per architecture over lots of smaller host, as we can run debci-worker in parallel.
Some specs of our current fleet can be found here.
Per host:
- The ci.d.n team doesn't do hosting, so hosting need to be dealt with
- ssh access with sudo rights
The hosts are constantly downloading source and binaries from deb.debian.org, so high network bandwidth is needed or additional disk space for a proxy is required (at time of writing seems to need around 40 GB). Network bandwidth without the proxy needs to be > 15 MB/s per debci-worker.
- mainline kernel support for the hardware we run our hosts on (or at being worked on with upstream, but then there needs to be a repository where up-to-date kernel packages are available). kernel CVE's fixed in Debian suite used for the kernel packages must not be open on our hosts for more than a two weeks)
RAM/CPU requirements go together with the "size" of the host, so a bit hard to give, take the inventory as a guide. The testbeds are using a tmpfs filesystem, so RAM size matters for that, not disk size (although usually lots of SWAP is configured to ensure the host hardly ever run out of memory).
Sum of an architecture:
support at least 20 parallel instances of debci-worker
- out of band reboot access to at least a subset of the hosts to cover the majority of test processing capacity