From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: teuthology erasure coded pools : warning
Date: Tue, 01 Jul 2014 09:05:35 +0200 [thread overview]
Message-ID: <53B25DBF.9000205@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
Hi,
TL;DR: if teuthology ec_pool workloads break, ping me or check https://github.com/ceph/teuthology/pull/271 for errors
A new way of creating the erasure coded pools in teuthology was merged a few hours ago https://github.com/ceph/teuthology/pull/271
It has not yet been tested and should not introduce any change. But it has not been tested for real and there is room for error. There is a potential for breakage for every workload containing ec_pool: true in the yaml description.
The general idea of the change is to replace hardcoded parameters with erasure code profiles read from the yaml file, with a default profile that matches the former parameters defaults.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next reply other threads:[~2014-07-01 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 7:05 Loic Dachary [this message]
2014-07-01 10:54 ` teuthology erasure coded pools : warning 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=53B25DBF.9000205@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.