From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Erasure Code Alpha Testing
Date: Sat, 01 Mar 2014 14:01:05 +0100 [thread overview]
Message-ID: <5311DA11.7020900@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]
Hi Ceph,
The code implementing Erasure Code in Ceph has been merged in Firefly[1] and is being tested. The unit tests are run at compile time with make check. The integration tests are run by teuthology [2], the Q&A tool dedicated to Ceph. A few workloads have been added for erasure code [3] and their success/failure can be observed daily from the pulpito [4] dashboard [5].
Seven organizations volunteered to alpha test erasure code a few months ago and were encouraged to run teuthology locally. Combined with manual testing, teuthology is a convenient way to encode a use case and explain the steps to reproduce a problem. I will make myself available to help install teuthlology. If you want to participate, feel free to send me an email or ping me on irc.oftc.net#ceph-devel nick loicd
There are many ways to contribute to stabilize erasure code before Firefly is released:
* Run the rados [6] teuthlogy [2] Q&A suite [7] locally
* Try manually after compiling Firefly [1] from sources [8]
rm -fr dev out ; mkdir -p dev ; LC_ALL=C MON=1 OSD=10 bash -x ./vstart.sh -d -n -X -l mon osd
./ceph osd crush rule create-erasure ecruleset erasure-code-k=2 erasure-code-m=1 erasure-code-ruleset-failure-domain=osd
./ceph osd pool create ecpool 12 12 erasure crush_ruleset=ecruleset erasure-code-k=2 erasure-code-m=1
the pool ecpool is erasure coded and ready to be used manually.
* Diagnose problems found by the daily teuthology runs from Intank [2]
* Proofread the Firefly code [1]
* Report bugs [9]
* Fix unassigned erasure code bugs from the queue [10] and send a pull request [11]
Cheers
[1] Firefly branch https://github.com/ceph/ceph/tree/firefly
[2] Teuthology Q&A tool https://github.com/ceph/teuthology/
[3] ec-* workloads https://github.com/ceph/ceph-qa-suite/tree/master/suites/rados/thrash/workloads
[4] Pulpito, the Teuthology dashboard https://github.com/ceph/pulpito
[5] Firefly rados suite results http://pulpito.ceph.com/?branch=firefly&suite=rados
[6] Rados suite https://github.com/ceph/ceph-qa-suite/tree/master/suites/rados
[7] Teuthology Q&A suite https://github.com/ceph/ceph-qa-suite/
[8] Building from sources http://ceph.com/docs/master/install/build-ceph/
[9] Bug tracker http://tracker.ceph.com/projects/ceph/issues/new
[10] "erasure code" or "ec" in the subject http://tracker.ceph.com/projects/ceph/issues?query_id=47
[11] Ceph pull requests https://github.com/ceph/ceph/pulls
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
reply other threads:[~2014-03-01 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5311DA11.7020900@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
/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.