Re: packages on download.ceph.com

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

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




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux