On Jun 23, 2015, at 1:17 PM, Stephen John Smoogen
On 23 June 2015 at 10:29, Filipe Miranda <fmiranda(a)redhat.com> wrote:
> I would like to suggest a great addition to the EPEL, the z Systems
> architecture (s390x).
> I have seem a great number of requests around EPEL for z Systems, its
> definitely a growing platform around Linux as IBM keeps offering better and
> more efficient servers that are basically a datacenter in a box - which is a
> great way for customers to reduce costs by consolidating Linux workloads.
> EPEL repository to s390x can be a great way to allow customers to try an
> unsupported package that still not available to RHEL on z Systems - that can
> in time mature, and can skip some of the processes to make into the RHEL for
> z Systems distro.
> The idea is to offer more technology options (Fedora Packages) to customers
> using RHEL on z Systems - this can flag us what packages are customers
> really interested into for RHEL on z Systems that are still not available in
> the Enterprise distro.
> Please let’s brainstorm this suggestion here, IBMers, community members,
> Fedora members, RedHatter, you are all welcome to join this discussion.
1) How would such items be built? The rest of EPEL is built with our
builders in PHX2. We don't have an s390 system in PHX2. Build
engineering requires access and the ability to 'rebuild' builders when
needed. EPEL has no
We (Red Hat) have a z Systems server in Westford, and the Fedora for s390x is built over
there, maybe we could use the same environment (same LPAR, just add a few VMs with Fedora
to do so) maybe Dan Horak can help sort his out.
2) How would developers test these builds? Much of the pushback we
have in EPEL for other architectures is that developers have no
systems which they can test to see why something is broken or not.
This means we end up with a large amount of spec files with
ExcludeArch: ppc etc etc. The lack of hardware and cost-free software
(eg CentOS port) pretty much make any build problem get the hammer of
This can be addressed maybe by IBM, by offering build systems to help developers test
3) There isn't really a way to tell you which packages customers
interested in for two reasons:
a) If we build packages for an arch, then every EPEL package gets
built for it (except those with the ExcludeArch hammer)
The idea is to start with what IBM thinks it will be good to have there, then if the
project gets traction, we can have feedback from customers using bugzilla.
b) User logs of yum does not show which package is requested... it
will show an estimate of users which for PPC is mainly engineers
inside of RH and IBM and a handful of sites. From talking with people
using PPC EPEL, they mirror it internally and no usage is seen.
Thank you for sharing these thoughts Stephen, let’s see what others have to say about it,
> Thank you,
> Kind Regards,
> Filipe Miranda
> Global Lead for Red Hat Products on IBM z Systems and Power Systems
> GPG Info: DF13EF21 (C79D 437C D56C ABC0 6878 D4D6 8BD5 2B72 DF13 EF21)
> Red Hat Inc.
> M. 949 572 3463
> W. 650 254 4170
> epel-devel mailing list
Stephen J Smoogen.
epel-devel mailing list