All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ken Dreyer <kdreyer@redhat.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: jerasure packaging and Ceph
Date: Fri, 07 Aug 2015 21:27:43 +0200	[thread overview]
Message-ID: <55C506AF.4080309@dachary.org> (raw)
In-Reply-To: <55C4EA1C.3080601@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

Hi Ken,

On 07/08/2015 19:25, Ken Dreyer wrote:
> Hi Loic,
> 
> I was looking through Ceph's bundled libraries recently and I was
> wondering why Ceph bundles its own copy of jerasure.
> 
> Could you give some background on that? Why don't we link to an separate
> system package?

Mainly because there is no proper non regression testing of the packages found in the distributions. It is absolutely critical for Ceph to ensure there is no regression because it would mean data loss. The packagers do not have that concern in mind right now, nor do they have the infrastructure to run non regression tests, to the best of my knowledge.

Even if they had non regression tests, whenever a new package is published, we would need to run Ceph integration tests before it lands in the distribution repositories to ensure that everything is fine from the Ceph perspective. The recent work with teuthology and OpenStack simplified this quite a lot and anyone can run teuthology now. However the level of coordination it would require between the jerasure packager and the ceph packager is far from what is going on currently.

I offered to package jerasure for Debian to solve that problem in the Debian / Ubuntu realm. I thought a first step to decouple ceph from jerasure could be that I care for jerasure because I have access to the test infrastructure and I understand what Ceph needs. And I could gradually make it possible for any packager to do the same, somehow (I have no idea how to do that, honestly). Unfortunately the person responsible for packaging jerasure did not respond favorably to my offer. Nor does he plan to implement integration or non regression tests.

Hopefully that will change in the future, but for now I think bundling jerasure with Ceph is the best way to preserve the data of our users.

Cheers

> 
> - Ken
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-08-07 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 17:25 jerasure packaging and Ceph Ken Dreyer
2015-08-07 19:27 ` Loic Dachary [this message]
2015-08-07 20:09   ` Ken Dreyer
2015-08-07 20:33     ` Loic Dachary

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=55C506AF.4080309@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=kdreyer@redhat.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.