Getting a small Hetzner dedicated server for buildbtw development and testing
Hey guys, I intend to get a small Hetzner box (most probably AX41-NVMe) for buildbtw development and testing, trying a bunch of things in the capacity of a proof-of-concept. We don't exactly know where we're going with this yet. We need a hardware machine as we need it to be able to do virtualization. Hetzner cloud VMs can't do virtualization. It will be a special gitlab-runner executor. The idea is to fork the libvirt runner and add a bunch of buildbtw-specific stuff to it. It will not be managed by devops. I will give root to people involved in the buildbtw project. Costs will be <€40/month. It will be decommissioned after development. Any thoughts or objections?
Hi On 20/11/2024 12:16, Sven-Hendrik Haase wrote:
Hey guys,
I intend to get a small Hetzner box (most probably AX41-NVMe) for buildbtw development and testing, trying a bunch of things in the capacity of a proof-of-concept. We don't exactly know where we're going with this yet. We need a hardware machine as we need it to be able to do virtualization. Hetzner cloud VMs can't do virtualization.
Any links where I can follow the PoC state? Will this fork all the packaging repos or just use a subset in a separate namespace on GitLab?
It will be a special gitlab-runner executor. The idea is to fork the libvirt runner and add a bunch of buildbtw-specific stuff to it.
It will not be managed by devops. I will give root to people involved in the buildbtw project. Costs will be <€40/month. It will be decommissioned after development.
40 euro seems reasonably cheap especially if we don't need to pay for setup fees. How long would this PoC run?
On 20.11.24 12:27, Jelle van der Waa wrote:
Hi
On 20/11/2024 12:16, Sven-Hendrik Haase wrote:
Hey guys,
I intend to get a small Hetzner box (most probably AX41-NVMe) for buildbtw development and testing, trying a bunch of things in the capacity of a proof-of-concept. We don't exactly know where we're going with this yet. We need a hardware machine as we need it to be able to do virtualization. Hetzner cloud VMs can't do virtualization.
Any links where I can follow the PoC state? Will this fork all the packaging repos or just use a subset in a separate namespace on GitLab?
There's this board [1] and then there's this issue [2]. The PoC code lives here [3]. That should provide a good overview. We will start with a subset of packages in a separate namespace and eventually move to try to build all packages.
It will be a special gitlab-runner executor. The idea is to fork the libvirt runner and add a bunch of buildbtw-specific stuff to it.
It will not be managed by devops. I will give root to people involved in the buildbtw project. Costs will be <€40/month. It will be decommissioned after development.
40 euro seems reasonably cheap especially if we don't need to pay for setup fees. How long would this PoC run?
We have no idea currently. It will be a couple of months at least. It's just really hard to judge from the current project's state. [1] https://gitlab.archlinux.org/archlinux/buildbtw/-/boards [2] https://gitlab.archlinux.org/archlinux/buildbtw/-/issues/3 [3] https://gitlab.archlinux.org/archlinux/buildbtw/-/tree/proof-of-concept?ref_...
On 20.11.2024 12.16, Sven-Hendrik Haase wrote:
Hey guys,
I intend to get a small Hetzner box (most probably AX41-NVMe) for buildbtw development and testing, trying a bunch of things in the capacity of a proof-of-concept. We don't exactly know where we're going with this yet. We need a hardware machine as we need it to be able to do virtualization. Hetzner cloud VMs can't do virtualization.
It will be a special gitlab-runner executor. The idea is to fork the libvirt runner and add a bunch of buildbtw-specific stuff to it.
It will not be managed by devops. I will give root to people involved in the buildbtw project. Costs will be <€40/month. It will be decommissioned after development.
Any thoughts or objections?
Hi Sven, Thanks for typing this up in a email. The plan SGTM :)
On 20.11.24 12:16, Sven-Hendrik Haase wrote:
Hey guys,
I intend to get a small Hetzner box (most probably AX41-NVMe) for buildbtw development and testing, trying a bunch of things in the capacity of a proof-of-concept. We don't exactly know where we're going with this yet. We need a hardware machine as we need it to be able to do virtualization. Hetzner cloud VMs can't do virtualization.
It will be a special gitlab-runner executor. The idea is to fork the libvirt runner and add a bunch of buildbtw-specific stuff to it.
It will not be managed by devops. I will give root to people involved in the buildbtw project. Costs will be <€40/month. It will be decommissioned after development.
Any thoughts or objections?
The machine has been ordered! It's a AX41-NVMe in Helsinki for €37.30 per month for the duration of buildbtw research and development.
On 26.11.24 12:06, Sven-Hendrik Haase wrote:
On 20.11.24 12:16, Sven-Hendrik Haase wrote:
Hey guys,
I intend to get a small Hetzner box (most probably AX41-NVMe) for buildbtw development and testing, trying a bunch of things in the capacity of a proof-of-concept. We don't exactly know where we're going with this yet. We need a hardware machine as we need it to be able to do virtualization. Hetzner cloud VMs can't do virtualization.
It will be a special gitlab-runner executor. The idea is to fork the libvirt runner and add a bunch of buildbtw-specific stuff to it.
It will not be managed by devops. I will give root to people involved in the buildbtw project. Costs will be <€40/month. It will be decommissioned after development.
Any thoughts or objections?
The machine has been ordered! It's a AX41-NVMe in Helsinki for €37.30 per month for the duration of buildbtw research and development.
And the server has been cancelled now that we have the production stack in place (based on cheap VMs, the build servers are separate).
participants (3)
-
Jelle van der Waa
-
Kristian Klausen
-
Sven-Hendrik Haase