From: Loic Dachary <loic@dachary.org>
To: David Zafman <david.zafman@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: mon_command
Date: Thu, 20 Mar 2014 08:08:29 +0100 [thread overview]
Message-ID: <532A93ED.2010305@dachary.org> (raw)
In-Reply-To: <39217F03-EC3A-4542-B00B-F62251B8CC98@inktank.com>
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
Hi David,
On 20/03/2014 03:40, David Zafman wrote:>
> My understanding is that are going to be using rados_mon_command() to create pools according to Tracker #7586: deprecate rados_pool_create. What I found when building a test case for EC is that after using the mon_command to create the pool I need to use wait_for_latest_osdmap() in order to wait for the change to propagate. The replicated pool test case using pool_create() doesn’t need to wait_for_latest_osdmap().
>
> Should we be deprecating librados calls in favor of the very generic mon_command() interface?
> I would suggest that we add the appropriate librados features to manipulate erasure coded pools.
What do you have in mind ? There are osd erasure-code-profile, osd crush rule create-erasure and the additional arguments to osd pool create can be used with rados_mon_command (or mon_command with the suggested implicit wait_for_latest_osdmap ). Anything else ?
https://github.com/ceph/ceph/blob/master/doc/dev/erasure-coded-pool.rst
Cheers
>
> David Zafman
> Senior Developer
> http://www.inktank.com
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2014-03-20 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 2:40 mon_command David Zafman
2014-03-20 7:08 ` Loic Dachary [this message]
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=532A93ED.2010305@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=david.zafman@inktank.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.