[ovirt-devel] Re: Updates on oVirt Node and oVirt appliance building outside Jenkins

[Michal Skrivanek]

> On 2. 12. 2021, at 13:19, Sandro Bonazzola  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.

it can usually be worked around by bypassing libvirt and/or using full 
emulation.
can we somehow get to the virt-install log?

> 
> 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 
> sbona...@redhat.com    
>  
> Red Hat respects your work life balance. Therefore there is no need to answer 
> this email out of your office hours.
> 
> 

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/P7SNY6SSQYNNLFVV5NQIRPURDOEIIQAD/

[ovirt-devel] Re: Updates on oVirt Node and oVirt appliance building outside Jenkins

[Michal Skrivanek]

> On 2. 12. 2021, at 14:07, Michal Skrivanek  wrote:
> 
> 
> 
>> On 2. 12. 2021, at 13:19, Sandro Bonazzola > > 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.
> 
> it can usually be worked around by bypassing libvirt and/or using full 
> emulation.
> can we somehow get to the virt-install log?

I played with it a bit and couldn't make it work. It does start but the full 
emulation seems to make it so slow that it is entirely unusable. Nesting won't 
work since those are azure vms.
But it's ok - the fact that it start all right means there won't be an issue 
doing this on our own runner.

> 
>> 
>> 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 
>> sbona...@redhat.com    
>>     
>> Red Hat respects your work life balance. Therefore there is no need to 
>> answer this email out of your office hours.
>> 
>> 
> 

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/3Z3T4CA3LN5XTDBO7MW4CFVQML3KG3NH/