From: Josh Durgin <josh.durgin@inktank.com>
To: Mandell Degerness <mandell@pistoncloud.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Documentation and Versions
Date: Wed, 01 Aug 2012 17:34:45 -0700 [thread overview]
Message-ID: <5019CB25.6060405@inktank.com> (raw)
In-Reply-To: <CA+jddaP4OGoA6bVC_ciJv_sob_V3g_PbtzWuUpiWJR0HZUaJNw@mail.gmail.com>
On 08/01/2012 11:53 AM, Mandell Degerness wrote:
> Thank you.
>
> I'd like to make two additional, related requests:
>
> 1) The internal ceph --help output should include the new command options
Yeah, the help output could certainly be improved. The client tool
needs to talk to the monitors to determine what basic commands are
available, but it would help to give each subsystem a "help" command
that queried them as necessary to report available commands.
Some commands (like ceph osd tell ...) are implemented on the osds,
so the available subcommands could vary if osd versions differed, but
it's still possible to provide usage info for a given osd.
I've opened http://www.tracker.newdream.net/issues/2894 for this.
> 2) The internal error information should be better written. Right
> now, "ceph osd crush set ..." seems to work (on 0.48). If, however,
> you type "ceph osd crush get" (i.e. trying to see what other options
> work), you get the result "unknown command crush" which implies to me
> that none of the crush subcommands are implemented, rather than that
> the "get" subcommand is not implemented.
Yeah, the command processing could be a lot better.
I created http://www.tracker.newdream.net/issues/2895 for this
particular error.
Josh
> Regards,
> Mandell Degerness
>
> On Wed, Aug 1, 2012 at 10:12 AM, Josh Durgin <josh.durgin@inktank.com> wrote:
>> On 07/31/2012 03:10 PM, Mandell Degerness wrote:
>>>
>>> I was looking through the latest documentation on ceph.com and I
>>> really like some of the new ways of doing things. What I find
>>> confusing, however, is the lack of documentation as to what version of
>>> ceph you need to be running in order to use the commands. In
>>> particular, what is the required version of ceph to run the "ceph osd
>>> crush ..." commands?
>>
>>
>> Yeah, there should probably be versions in the docs. The 'ceph osd crush'
>> commands were added in 0.46, but there are bug fixes for
>> 'ceph osd crush set' in 0.48 and 'ceph osd crush move' in 0.49.
>>
>>> Regards,
>>> Mandell Degerness
>>
>>
prev parent reply other threads:[~2012-08-02 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 22:10 Documentation and Versions Mandell Degerness
2012-08-01 17:12 ` Josh Durgin
2012-08-01 18:53 ` Mandell Degerness
2012-08-02 0:34 ` Josh Durgin [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=5019CB25.6060405@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mandell@pistoncloud.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.