<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Fri, Dec 15, 2017 at 10:30 PM Barak Korren <<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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></blockquote><div><br></div></div><div dir="ltr"><div class="gmail_quote"><div>We should prepare a fedora 27 build for all projects before we enable</div><div>the jobs in the CI. But if we can disable problematic jobs in the CI easily</div><div>(and it seems we can), I think this is not a problem.</div><div><br></div><div>You can merge the ioprocess change now if you like.</div></div></div><div dir="ltr"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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 need<br>
to build then for s390x?<br></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>For vdsm we need:</div><div>- ioprocess (nsoffer)</div><div>- ovirt-imageio-daemon (derez)</div><div>- ovirt-imageio-common (derez)</div><div>- pthreading (ybronhei)</div><div>- subprocess32 (sbonazzo?)</div><div><br></div><div>For engine:</div><div><div>- ovirt-imageio-common</div><div>- ovirt-imageio-proxy</div><br class="m_-5881134502178403612inbox-inbox-Apple-interchange-newline"></div><div>This is only (some) the components that we build. We have also tons of</div><div>dependencies that are part of Fedora (e.g. sanlock, libvirt). I hope these</div><div>projects are built for s390x.</div><div><br></div><div>Added some maintainers.</div></div></div><div dir="ltr"><div class="gmail_quote"><div><br></div><div>Nir</div></div></div><div dir="ltr"><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
[1]: <a href="http://jenkins.ovirt.org/search/?q=master_build-artifacts-el7-ppc64le" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/search/?q=master_build-artifacts-el7-ppc64le</a><br>
[2]: <a href="https://gerrit.ovirt.org/c/85487" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/c/85487</a><br>
[3]: <a href="https://gerrit.ovirt.org/c/85486" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/c/85486</a><br>
[4]: <a href="https://gerrit.ovirt.org/c/85485" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/c/85485</a><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>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
</blockquote></div></div></div>