Re: [ovirt-devel] Adding s390 support to oVirt
by Viktor Mihajlovski
On 21.11.2017 11:26, Dan Horák wrote:
[...]
>> qemu s390x emulation does not work with code compiled for z12.
>> Would a real virtual machine be what you need?
>> The Fedora team DOES have access to a z13. Not sure how much
>> resources are available, but can you contact Dan Horak (on cc) if
>> there is enough spare capacity.
>
> Christian is right, we have a publicly accessible guest running Fedora
> on the Marist College z13 mainframe. It's currently used by ~5 projects
> (for example glibc and qemu) as their build and CI host, so adding
> another project depends how intensive ovirt's usage would be.
As a first step one could only build the packages needed for the KVM
host. At this point in time that would be vdsm and ovirt-host, both are
building rather quickly.
It should be possible to ensure that only these are built on a s390
system using appropriate node filters.
[...]
--
Mit freundlichen Grüßen/Kind Regards
Viktor Mihajlovski
5 years, 9 months
Re: [ovirt-devel] Adding s390 support to oVirt
by Barak Korren
On 16 November 2017 at 19:38, Martin Sivak <msivak(a)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
5 years, 10 months
Re: [ovirt-devel] Adding s390 support to oVirt
by Viktor Mihajlovski
On 16.11.2017 18:27, Barak Korren wrote:
> On 16 November 2017 at 18:52, Viktor Mihajlovski
> <mihajlov(a)linux.vnet.ibm.com> wrote:
>>
>> Short update, with yesterday's API model 4.2.25 release, there's basic
>> support for s390 available in ovirt-engine. At this point in time, there
>> are no ovirt yum repositories for the s390x architecture - not sure what
>> the process would be to add s390x repositories and how to build the
>> binary RPMs at least for the host packages (i.e. vdsm-*). Maybe it would
>> possible to use the s390-koji infrastructure used to build Fedora for s390x?
>
> Koji is very opinionated about how RPMs and specfiles should look,
> AFAIK A pretty massive amount of work would be needed to make
> everything that is needed for a node to build on it, and then we would
> end up with a process that is quite different with how we currently do
> builds for other platforms.
>
> (I might be wrong about this, since some oVirt packages get also built
> as part of the CentOS virt SIG, and that is done using Koji as well)
>
> More specifically, Koji usually assumes the starting point for the
> build process would be a specfile, while in oVirt we typically
> generated the specfile and then the RPM as part of a bigger build
> process.
>
> Does fedora have an s390x server associated to it?
There's a build system for Fedora on s390x:
https://s390.koji.fedoraproject.org/koji
> We do use the same basic environment setup tool - mock - as the basis
> of our build infrastructure, so if Fedora is actually emulating s390x
> is some way while using mock, we might be able to do the same thing.
>
> Just for general knowledge, the process for building oVirt repos, is
> to have *-build-artifacts-* jobs for each project that build RPM's
> after patches get merged, and then have the change-queue to collect
> the built packages, rung them through ovirt-system-tests (a.k.a. OST)
> and finally deposit them into the 'tested' rpoe, from which they are
> copied nightly to the '*-snapshot' repos.
>
> OST only tests for CentOS 7/x86_64 ATM, but we bring along packages
> for other distros and architectures via the same process while
> assuming that if a package for a given commit works for CentOS
> 7/x86_64 it would probably work for other platforms as well...
>
I've noticed that there's no test automation for non-x86 arches. How are
the ppc64le packages then built and stored in the repos?
Would it be conceivable to do the following?
After a successfull build and OST of a package, take the SRPM and submit
to s390-koji to produce the s390x binary RPMs.
Then copy the binary RPMs into the respective repository, e.g.
*-snapshot/rpm/el7/s390x (and update the repository metadata).
--
Mit freundlichen Grüßen/Kind Regards
Viktor Mihajlovski
5 years, 10 months
Re: [ovirt-devel] Adding s390 support to oVirt
by Viktor Mihajlovski
On 18.09.2017 09:30, Viktor Mihajlovski wrote:
> Hi,
>
> as a heads up: I'd like to contribute some basic support for the s390
> architecture to oVirt. For that purpose I'll post some patches to
> gerrit, mostly for the following repositories: VDSM,
> ovirt-engine-api-model and ovirt-engine. There might be some collateral
> patches that need to go into ovirt-host[-deploy] since not all of the
> pre-requisite RPMs are available on s390, but this probably needs a
> separate discussion.
>
> I've started to hang out on the #ovirt OFTC channel, feel free to ping
> me if you have questions related to s390. Thanks!
>
Short update, with yesterday's API model 4.2.25 release, there's basic
support for s390 available in ovirt-engine. At this point in time, there
are no ovirt yum repositories for the s390x architecture - not sure what
the process would be to add s390x repositories and how to build the
binary RPMs at least for the host packages (i.e. vdsm-*). Maybe it would
possible to use the s390-koji infrastructure used to build Fedora for s390x?
--
Mit freundlichen Grüßen/Kind Regards
Viktor Mihajlovski
5 years, 10 months
