packages on download.ceph.com

packages on download.ceph.com

[Deneau, Tom]

I'm trying to gather information on what it would take to get packages
for an architecture other than x86_64 up on http://download.ceph.com 

-- Tom Deneau, AMD

Re: packages on download.ceph.com

[Mark Nelson]

On 03/09/2015 02:06 PM, Deneau, Tom wrote:
> I'm trying to gather information on what it would take to get packages
> for an architecture other than x86_64 up on http://download.ceph.com

What we've done in the past for certain non-X86 architectures (such as 
ARM) is to get build nodes in place that can be used with our gitbuilder 
setup to continuously make development builds:

http://www.ceph.com/gitbuilder.cgi

Which get put here:

http://gitbuilder.ceph.com/

Usually the problem is two fold:  Someone's time to set it up, and 
making sure we have enough (or fast enough) build systems for that 
architecture to keep up.

Mark

>
> -- Tom Deneau, AMD
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: packages on download.ceph.com

[Danny Al-Gaaf]

Am 09.03.2015 um 20:35 schrieb Mark Nelson:
> 
> 
> On 03/09/2015 02:06 PM, Deneau, Tom wrote:
>> I'm trying to gather information on what it would take to get packages
>> for an architecture other than x86_64 up on http://download.ceph.com
> 
> What we've done in the past for certain non-X86 architectures (such as
> ARM) is to get build nodes in place that can be used with our gitbuilder
> setup to continuously make development builds:
> 
> http://www.ceph.com/gitbuilder.cgi
> 
> Which get put here:
> 
> http://gitbuilder.ceph.com/
> 
> Usually the problem is two fold:  Someone's time to set it up, and
> making sure we have enough (or fast enough) build systems for that
> architecture to keep up.

It would be much easier to use OpenBuildService [1] for package build.
It supports many distributions and architectures.

If you don't care that it's openSUSE infrastructure you/we could use
build.opensuse.org to build packages e.g. for RHEL/Centos/Fedora,
openSUSE/SLES, Debian, Ubuntu and others (I did so in the past.)

At least openSUSE/SLES packages could be also build on armv7l and e.g.
ppc/s390x ... for other distros we have to check.

The question is: should we build packages (and which) or is this more a
task for the distributions?

Danny

[1] http://openbuildservice.org
[2] https://build.opensuse.org

RE: packages on download.ceph.com

[Deneau, Tom]

> -----Original Message-----
> From: Danny Al-Gaaf [mailto:danny.al-gaaf@bisect.de]
> Sent: Monday, March 09, 2015 3:46 PM
> To: Mark Nelson; Deneau, Tom; ceph-devel
> Subject: Re: packages on download.ceph.com
> 
> Am 09.03.2015 um 20:35 schrieb Mark Nelson:
> >
> >
> > On 03/09/2015 02:06 PM, Deneau, Tom wrote:
> >> I'm trying to gather information on what it would take to get packages
> >> for an architecture other than x86_64 up on http://download.ceph.com
> >
> > What we've done in the past for certain non-X86 architectures (such as
> > ARM) is to get build nodes in place that can be used with our gitbuilder
> > setup to continuously make development builds:
> >
> > http://www.ceph.com/gitbuilder.cgi
> >
> > Which get put here:
> >
> > http://gitbuilder.ceph.com/
> >
> > Usually the problem is two fold:  Someone's time to set it up, and
> > making sure we have enough (or fast enough) build systems for that
> > architecture to keep up.
> 
> It would be much easier to use OpenBuildService [1] for package build.
> It supports many distributions and architectures.
> 
> If you don't care that it's openSUSE infrastructure you/we could use
> build.opensuse.org to build packages e.g. for RHEL/Centos/Fedora,
> openSUSE/SLES, Debian, Ubuntu and others (I did so in the past.)
> 
> At least openSUSE/SLES packages could be also build on armv7l and e.g.
> ppc/s390x ... for other distros we have to check.
> 
> The question is: should we build packages (and which) or is this more a
> task for the distributions?
> 
> Danny
> 
> [1] http://openbuildservice.org
> [2] https://build.opensuse.org

Building packages should indeed be a task for the distributions but some distros are
slow to add new packages so this would be a stopgap measure until they do.

-- Tom

Re: packages on download.ceph.com

[Sage Weil]

On Mon, 9 Mar 2015, Danny Al-Gaaf wrote:
> Am 09.03.2015 um 20:35 schrieb Mark Nelson:
> > On 03/09/2015 02:06 PM, Deneau, Tom wrote:
> >> I'm trying to gather information on what it would take to get packages
> >> for an architecture other than x86_64 up on http://download.ceph.com

I'm guessing you're interested in 64-bit arm (aarch64?)?

I would love to have packages built for all architectures people are 
interested in.  In practice, there are two limitations: build hardware and 
the maintenance overhead.  For example, we have all this armv7l gear but 
stopped doing builds because it was time consuming to keep it running.  
The moment someone signs up to do that management we can set up vpn 
access to the lab and add it back it.  The other problem we hit was that 
the armv7l builds took so much longer than the x86_64 ones and the current 
release process is easier when it's all done it one go.  I suspect what 
we'd end up with is a situation where the packages for some architectures 
get posted before others (which probably isn't a big deal).  Alfredo, you 
should chime in if there are other reasons why this would make things 
harder.

> It would be much easier to use OpenBuildService [1] for package build.
> It supports many distributions and architectures.
> 
> If you don't care that it's openSUSE infrastructure you/we could use
> build.opensuse.org to build packages e.g. for RHEL/Centos/Fedora,
> openSUSE/SLES, Debian, Ubuntu and others (I did so in the past.)
> 
> At least openSUSE/SLES packages could be also build on armv7l and e.g.
> ppc/s390x ... for other distros we have to check.
> 
> The question is: should we build packages (and which) or is this more a
> task for the distributions?

I tried OBS way back when but found it difficult to use and not 
particularly flexible.  My main concern is that we will run into problems 
and not have the ability to address them (for example, missing or broken
distro dependencies or something like that).

More generally, I think it has been hugely valuable to have up to date 
packages on ceph.com as the distros tend to relatively slow to release 
things.  Users also typically choose between several different major ceph 
releases.  I'm pretty hesitant to abandon this...

sage

RE: packages on download.ceph.com

[Deneau, Tom]

> -----Original Message-----
> From: Sage Weil [mailto:sweil@redhat.com]
> Sent: Monday, March 09, 2015 4:05 PM
> To: Danny Al-Gaaf
> Cc: Mark Nelson; Deneau, Tom; ceph-devel
> Subject: Re: packages on download.ceph.com
> 
> On Mon, 9 Mar 2015, Danny Al-Gaaf wrote:
> > Am 09.03.2015 um 20:35 schrieb Mark Nelson:
> > > On 03/09/2015 02:06 PM, Deneau, Tom wrote:
> > >> I'm trying to gather information on what it would take to get
> > >> packages for an architecture other than x86_64 up on
> > >> http://download.ceph.com
> 
> I'm guessing you're interested in 64-bit arm (aarch64?)?
> 
> I would love to have packages built for all architectures people are
> interested in.  In practice, there are two limitations: build hardware and
> the maintenance overhead.  For example, we have all this armv7l gear but
> stopped doing builds because it was time consuming to keep it running.
> The moment someone signs up to do that management we can set up vpn access to
> the lab and add it back it.  The other problem we hit was that the armv7l
> builds took so much longer than the x86_64 ones and the current release
> process is easier when it's all done it one go.  I suspect what we'd end up
> with is a situation where the packages for some architectures get posted
> before others (which probably isn't a big deal).  Alfredo, you should chime
> in if there are other reasons why this would make things harder.
> 
> > It would be much easier to use OpenBuildService [1] for package build.
> > It supports many distributions and architectures.
> >
> > If you don't care that it's openSUSE infrastructure you/we could use
> > build.opensuse.org to build packages e.g. for RHEL/Centos/Fedora,
> > openSUSE/SLES, Debian, Ubuntu and others (I did so in the past.)
> >
> > At least openSUSE/SLES packages could be also build on armv7l and e.g.
> > ppc/s390x ... for other distros we have to check.
> >
> > The question is: should we build packages (and which) or is this more
> > a task for the distributions?
> 
> I tried OBS way back when but found it difficult to use and not particularly
> flexible.  My main concern is that we will run into problems and not have the
> ability to address them (for example, missing or broken distro dependencies
> or something like that).
> 
> More generally, I think it has been hugely valuable to have up to date
> packages on ceph.com as the distros tend to relatively slow to release
> things.  Users also typically choose between several different major ceph
> releases.  I'm pretty hesitant to abandon this...
> 
> sage

Sage --

Yes, my original question was for aarch64.

On that topic, since Ceph is part of Red Hat,
can the Ceph developers lobby for getting some version of Ceph
included in the first RHEL aarch64 release?  My understanding is that currently
Ceph packages are not planned to be included in the default package lists.

-- Tom

RE: packages on download.ceph.com

[Sage Weil]

Hi Tom,

On Wed, 11 Mar 2015, Deneau, Tom wrote:
> On that topic, since Ceph is part of Red Hat,
> can the Ceph developers lobby for getting some version of Ceph
> included in the first RHEL aarch64 release?  My understanding is that currently
> Ceph packages are not planned to be included in the default package lists.

Including packages in RHEL generally means they are fully supported, and 
since we don't have any aarch64 hardware in our labs doing Ceph testing 
yet and the storage team isn't focusing on this right now, that doesn't 
surprise me.  I'll ping some people internally though and find out what 
the ARM folks' plans are... I don't know too much about that project!

sage