Provide a libvirt hypervisor for the fleet

During the internal Easter-eggs weekly meeting the idea was submitted. It was approved on principle and Easter-eggs will provide the following hypervisor:

        - cpu : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
        - ram : 64 Go
        - cm : X9DRD-iF
        - HDD : 1*ST3000DM001-1CH1 (3TB) 7200 rpm
        - SSD : 2*INTEL SSDSC2BA10 (100GB)

As well as a range of public IPv4 (16 is possible). Easter-eggs provides the following services:

  • Monitoring of the hardware
  • Disaster recovery in case the machine goes down, including replacing it entirely
  • Backup (except for the Qemu images).

@rlaguerre could be the link between the Hostea project and the larger Easter-eggs sysadmin team who is not directly involved in the Hostea project. The next action could be:

  • @dachary Hostea side: keep working on implementing the task list to allow for the integration of the hypervisor
  • @rlaguerre Easter-eggs side: create and followup tasks in the internal issue tracking to mirror the relevant tasks in the Hostea issue tracker

This will be an interesting showcase of how to implement transparency when it involves non publicly available resources (the internal Easter-eggs issue tracker). I think the best course of action would be to just copy/paste the content of the internal Easter-eggs issue tracker to It means the internal issue tracker must not contain any confidential information, which should not be too difficult.

The associated expenses (hardware, time spent by Raphael and others) are also published as explained in the revenue sharing system. Diligently accounting for time spent is an essential part of the daily activity within the Easter-eggs sysadmin team, it will therefore also be a matter of copy/pasting.

This copy/pasting will be a little tedious and may be automated in the future. But for this first time it should not be too much.

To be continued!


An issue was created to account for the time spent by Easter-eggs when working on providing a libvirt hypervisor for the fleet.

1 Like

@rlaguerre regarding the configuration:

  • 16 IPv4 will be good enough for the foreseeable future
  • disk space: as much as possible, the minimum would be 500GB
  • No need for IPv6

Iā€™m glad you did find a redundant power supply for the hardware :+1: