[ovirt-devel] Adding s390 support to oVirt

[Dan Horák]

On Mon, 20 Nov 2017 09:24:00 +0100
Martin Sivak <msivak at redhat.com> wrote:

> Dan Horak used to be part of this project. Lets see if he still
> remembers that.
> 
> Dan: Can you please tell us how the s390 builds in Fedora are/were
> done when no hw was available?

AFAIK Fedora was always building its packages on real mainframe HW,
using a dedicated LPAR on the Red Hat's machine.


		Dan
 
> Martin Sivak
> 
> On Sat, Nov 18, 2017 at 12:14 PM, Barak Korren <bkorren at redhat.com>
> wrote:
> > On 16 November 2017 at 19:38, Martin Sivak <msivak at redhat.com>
> > wrote:
> >>> Koji is very opinionated about how RPMs and specfiles should look,
> >>> AFAIK
> >>
> >> Actually, koji does not care much. Fedora packaging rules are
> >> enforced by package reviewers.
> >>
> >>> More specifically, Koji usually assumes the starting point for the
> >>> build process would be a specfile
> >>
> >> This is correct though.
> >>
> >>> Does fedora have an s390x server associated to it?
> >>
> >> They used to have s390 emulators running for that purpose iirc.
> >
> > I wonder if someone could provide more information about this. Is
> > this done via qemu? Or built-in to mock perhaps? It this exists, I
> > can pave the way to enabling s390x build support on oVirt infra.
> >
> >
> > --
> > Barak Korren
> > RHV DevOps team , RHCE, RHCi
> > Red Hat EMEA
> > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted