<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-12-17 8:38 GMT+01:00 Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">On 16 December 2017 at 00:53, Nir Soffer <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>> wrote:<br>
> On Fri, Dec 15, 2017 at 10:30 PM Barak Korren <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>> wrote:<br>
>><br>
>> Hi to all project maintainers,<br>
>><br>
>> As you may know, over the last few months the oVirt project had got<br>
>> some code contributions geared towards enabling the use of s390x<br>
>> (Mainframe) machines as hypervisor hosts.<br>
>><br>
>> As you may also know, if you've followed the relevant thread, some<br>
>> work had been done in collaboration with the Fedora community to<br>
>> enable os390x support in oVirt`s CI system.<br>
>><br>
>> We're now at the point where we can take the final step and enable<br>
>> automated builds of node components for s390x/fc27. Looking at what we<br>
>> curently build for ppc64le, I already took the time and submitted<br>
>> patches to enable build jobs for vdsm [2], ovirt-host [3], and<br>
>> ioprocess [4]. The relevant maintainers should have had these patches<br>
>> land in thair inbpx already.<br>
>><br>
>> Few questions remain however:<br>
>> 1. When would be the best time to merge the patches mentioned above? Given<br>
>> that some of the projects do not support fc27 yet, that the new<br>
>> build jobs may<br>
>> raise issues and that the 4.2 release is fast approaching, the<br>
>> right timing should<br>
>> be considered carefully.<br>
><br>
><br>
> We should prepare a fedora 27 build for all projects before we enable<br>
> the jobs in the CI. But if we can disable problematic jobs in the CI easily<br>
> (and it seems we can), I think this is not a problem.<br>
<br>
</div></div>I don't want to have the code in 'master' diverge from what actually<br>
exists in jenkins.<br>
<span class="gmail-"><br>
> You can merge the ioprocess change now if you like.<br>
<br>
</span>Maybe its better to make sure fc27/x86_64 builds first? Please state<br>
your intent on the relevant patch.<br>
<span class="gmail-"><br>
>> 2. Which additional projects need to be build? I can see we build some SDK<br>
>> components for ppc64le as wel, are those dependences of vdsm? Will we<br>
>> need<br>
>> to build then for s390x?<br>
><br>
><br>
> For vdsm we need:<br>
> - ioprocess (nsoffer)<br>
> - ovirt-imageio-daemon (derez)<br>
> - ovirt-imageio-common (derez)<br>
> - pthreading (ybronhei)<br>
> - subprocess32 (sbonazzo?)<br>
<br>
</span>I wonder how come the last 4 don't have ppc64le builds. </blockquote><div><br></div><div>These are noarch:</div><div> - ovirt-imageio-daemon (derez)<br> - ovirt-imageio-common (derez)<br></div><div><br></div><div>These are provided by Fedora and CentOS Virt SIG</div><div>- pthreading (ybronhei)<br>- subprocess32 (sbonazzo?)<br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The last 2<br>
don't seem to even have proper build jobs.<br>
<br>
> For engine:<br>
<br>
AFAIK there is no intention to support running engine on anything<br>
other then x86_64 at this point.<br>
<span class="gmail-"><br>
> This is only (some) the components that we build. We have also tons of<br>
> dependencies that are part of Fedora (e.g. sanlock, libvirt). I hope these<br>
> projects are built for s390x.<br>
<br>
</span>There is a full fedora build for s390x, so I suppose those are available there.<br>
Also, those are all mentioned in vdsm.spec right? So build-artifacts<br>
will not pass if they are missing right?<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
--<br>
Barak Korren<br>
RHV DevOps team , RHCE, RHCi<br>
Red Hat EMEA<br>
<a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a> | TRIED. TESTED. TRUSTED. | <a href="http://redhat.com/trusted" rel="noreferrer" target="_blank">redhat.com/trusted</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>SANDRO</span> <span>BONAZZOLA</span></p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D</span></p><p style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat <span>EMEA</span></a></p><table border="0" style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"><img src="https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png" width="90" height="auto"></a></td><td style="font-size:10px"><div><a href="https://redhat.com/trusted" style="color:rgb(204,0,0);font-weight:bold" target="_blank">TRIED. TESTED. TRUSTED.</a></div></td></tr></tbody></table><br></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div></div>