All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: Mark Nelson <mnelson@redhat.com>,
	"Deneau, Tom" <tom.deneau@amd.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: packages on download.ceph.com
Date: Mon, 09 Mar 2015 21:45:32 +0100	[thread overview]
Message-ID: <54FE066C.2070902@bisect.de> (raw)
In-Reply-To: <54FDF605.9000302@redhat.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

  reply	other threads:[~2015-03-09 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 19:06 packages on download.ceph.com Deneau, Tom
2015-03-09 19:35 ` Mark Nelson
2015-03-09 20:45   ` Danny Al-Gaaf [this message]
2015-03-09 21:03     ` Deneau, Tom
2015-03-09 21:04     ` Sage Weil
2015-03-11 18:38       ` Deneau, Tom
2015-03-13 23:20         ` Sage Weil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54FE066C.2070902@bisect.de \
    --to=danny.al-gaaf@bisect.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mnelson@redhat.com \
    --cc=tom.deneau@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.