All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zenon Panoussis <oracle@provocation.net>
To: ceph-devel@vger.kernel.org
Subject: Re: crush rule definitions
Date: Wed, 04 May 2011 22:34:54 +0200	[thread overview]
Message-ID: <4DC1B86E.5070704@provocation.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1105041225010.648@cobra.newdream.net>


On 05/04/2011 09:28 PM, Sage Weil wrote:

>> As an aside, I think that, to a certain extent, improving the 
>> documentation could contribute more to the code base...

> The replication is covered by
> http://ceph.newdream.net/wiki/Adjusting_replication_level

> Any specific suggestions on how that should be improved?

The wiki is a reasonably good instruction in getting ceph up and running,
but it could do a lot better in explaining the hows and whys of the system.

http://ceph.newdream.net/wiki/Adjusting_replication_level is a good example
of this. It tells you exactly how to adjust the overall replication level,
but it doesn't tell you how to control where the replicas are put. So you
go searching and you find http://ceph.newdream.net/wiki/Custom_data_placement_with_CRUSH
and it explains pretty well how to implement crush rules, but it doesn't
tell what each rule parametre actually does, nor does it (appear to) give
an exhaustive list of all parametres that are available.

So, all in all, I think that what is mostly needed in the wiki is a general
introduction to ceph, an explanation and diagram of how it works and how
its internals relate to each-other. All of this is in your thesis, I know,
but it is very difficult to connect an abstract academic paper to a concrete
configuration problem and configuration parametre.

I happily contribute to the wiki when I'm 100% sure that what I'm writing is
correct, but most of the time when I see a potential improvent of the wiki,
I lack the solid understanding that's needed for me to make that improvement
myself.

Z


      parent reply	other threads:[~2011-05-04 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 18:16 crush rule definitions Zenon Panoussis
2011-05-04 18:21 ` Sage Weil
2011-05-04 19:20   ` Zenon Panoussis
2011-05-04 19:28     ` Sage Weil
2011-05-04 19:31       ` Sage Weil
2011-05-04 20:34       ` Zenon Panoussis [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=4DC1B86E.5070704@provocation.net \
    --to=oracle@provocation.net \
    --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.