On 2. 12. 2021, at 13:19, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Hi, just a quick update on current issues in trying to build oVirt Node and the engine appliance outside Jenkins.

1) Using GitHub Actions: an attempt to build it is in progress here: https://github.com/sandrobonazzola/ovirt-appliance/pull/1

it's currently failing due to lorax not being able to perform the build. It kind of make sense as we are trying to do a virt-install within a container without the needed virtualization hardware exposed.

I'm currently investigating how to make use of software virtualization in order to drop the requirement on missing hardware / nested virtualization.

Also investigating on how to use self hosted runners for providing a build system with usable virtualization hardware.

2) Using COPR: we have basically the same issue: lorax fails not having access to the virtualization hardware

3) Using CentOS Community Build System

This is a fully fledged Koji instance and it allows to build using the image-build variant. It has a completely different configuration system and it is more similar to what we are doing within the downstream build of oVirt Node. An attempt of providing the configuration started here: https://gerrit.ovirt.org/c/ovirt-appliance/+/117801

The issue there is that all the packages needed to be included within Node and Appliance must be built within CentOS Community Build System build root.

The system has no external access to the internet so everything we need it needs to come from CentOS infra.

I haven't started digging into oVirt Node but the build flow is very similar to the appliance one, so once one is solved, the other should be simple.

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.