From: Loic Dachary <loic@dachary.org>
To: John Wilkins <john.wilkins@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Erasure Code user guide
Date: Mon, 03 Mar 2014 21:18:54 +0100 [thread overview]
Message-ID: <5314E3AE.9000308@dachary.org> (raw)
In-Reply-To: <CAM2gkg49zGSwVV8a0ui+MyNbdy0fL_TEFYDtOkPteVbGioOZyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]
Hi John,
Thanks for the guidance, I'll do as you suggest.
Cheers
On 03/03/2014 21:14, John Wilkins wrote:
> Sorry Loic. I didn't see this earlier.
>
> I recommend putting it here: http://ceph.com/docs/master/rados/operations/
>
> We already have a guide for pools here: http://ceph.com/docs/master/rados/operations/pools/
>
> You could either add it to the pools.rst document or create another one for erasure coding and cache tiering.
>
> Regards,
>
>
> John
>
>
>
> On Mon, Mar 3, 2014 at 8:11 AM, Wido den Hollander <wido@42on.com <mailto:wido@42on.com>> wrote:
>
> On 03/03/2014 04:35 PM, Loic Dachary wrote:
>
>
>
> On 03/03/2014 15:47, Wido den Hollander wrote:
>
> On 03/03/2014 02:20 PM, Loic Dachary wrote:
>
> Hi John,
>
> I'd like to draft a user guide for erasure coded pools, oriented toward system administrators. Where do you advise me to insert this ? Should I get inspiration from an example ?
>
>
> the docs dir isn't good for that? If not, might be that the Wiki is a proper location?
>
>
> Are you suggesting something like doc/dev/erasure-coded-pool.rst next to doc/dev/cache-pool.rst ? I'm not sure about the wiki.
>
>
> Yes, why not? That way all the docs are in a central place.
>
>
> Cheers
>
>
> Thanks in advance for any pointers or advice :-)
>
>
>
>
>
>
> --
> Wido den Hollander
> 42on B.V.
>
> Phone: +31 (0)20 700 9902 <tel:%2B31%20%280%2920%20700%209902>
> Skype: contact42on
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/__majordomo-info.html <http://vger.kernel.org/majordomo-info.html>
>
>
>
>
> --
> John Wilkins
> Senior Technical Writer
> Intank
> john.wilkins@inktank.com <mailto:john.wilkins@inktank.com>
> (415) 425-9599
> http://inktank.com
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-03-03 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 13:20 Erasure Code user guide Loic Dachary
2014-03-03 14:47 ` Wido den Hollander
2014-03-03 15:35 ` Loic Dachary
2014-03-03 16:11 ` Wido den Hollander
[not found] ` <CAM2gkg49zGSwVV8a0ui+MyNbdy0fL_TEFYDtOkPteVbGioOZyA@mail.gmail.com>
2014-03-03 20:18 ` Loic Dachary [this message]
[not found] ` <CANygib86bmr_Bh=95XZ9M7a5V8PTN7inByhWLQ4vOzqctv1dmQ@mail.gmail.com>
2014-03-03 22:58 ` 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=5314E3AE.9000308@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=john.wilkins@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.