All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Haas <florian@hastexo.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Cc: "Plaetinck, Dieter" <dieter@vimeo.com>, Ross Turk <ross@inktank.com>
Subject: Re: Integration work
Date: Tue, 28 Aug 2012 14:03:16 -0700	[thread overview]
Message-ID: <503D3214.4000503@hastexo.com> (raw)
In-Reply-To: <20120828203235.45f1e3a5@dieter-t420s>

On 08/28/2012 11:32 AM, Plaetinck, Dieter wrote:
> On Tue, 28 Aug 2012 11:12:16 -0700
> Ross Turk <ross@inktank.com> wrote:
> 
>>
>> Hi, ceph-devel! It's me, your friendly community guy.
>>
>> Inktank has an engineering team dedicated to Ceph, and we want to work 
>> on the right stuff. From time to time, I'd like to check in with you to 
>> make sure that we are.
>>
>> Over the past several months, Inktank's engineers have focused on core 
>> stability, radosgw, and feature expansion for RBD. At the same time, 
>> they have been regularly allocating cycles to integration work. 
>> Recently, this has consisted of improvements to the way Ceph works 
>> within OpenStack (even though OpenStack isn't the only technology that 
>> we think Ceph should play nicely with).
>>
>> What other sorts of integrations would you like to see Inktank engineers 
>> work on?
> 
> are we only supposed to give answers wrt. integration with other software?
> if not, I would suggest to write documentation.

If I may say so, the amount of work that John has poured into this in
recent week has been incredible (http://www.ceph.com/docs/master/). So
while it's definitely not complete nor perfect, I'm sure he would
appreciate a little more specific information as to where you believe
documentation is lacking.

I for my part, in the documentation space, would love for the admin
tools to become self-documenting. For example, I would love a "help"
subcommand at any level of the ceph shell, listing the supported
subcommands in that level. As in "ceph help", "ceph mon help", "ceph osd
getmap help".

Even better, the ceph shell could support a general-purpose hook that
bash-completion can use (kind of like "hg" does in Mercurial), and this
and the above-conjectured help facility could arguably share quite a bit
of code.

> and also integration with CM like puppet/chef

+1, although people are already working on both. So maybe this is just
about the need to tell more people about that. :)

Cheers,
Florian

  reply	other threads:[~2012-08-28 21:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 18:12 Integration work Ross Turk
2012-08-28 18:32 ` Plaetinck, Dieter
2012-08-28 21:03   ` Florian Haas [this message]
2012-08-28 21:15     ` Tommi Virtanen
2012-08-28 21:20       ` Josh Durgin
2012-08-30 14:00         ` João Eduardo Luís
2012-08-28 18:51 ` Dieter Kasper
2012-08-28 18:57   ` Smart Weblications GmbH - Florian Wiessner
2012-08-28 20:05     ` Dieter Kasper
2012-08-28 20:46   ` Tren Blackburn
2012-08-29  7:06     ` Amon Ott
2012-08-29  8:20 ` Sylvain Munaut
2012-08-29  9:53   ` Wido den Hollander
2012-08-29 12:35     ` Sylvain Munaut
2012-08-29 13:40       ` Wido den Hollander
2012-08-29 13:43         ` Tommi Virtanen
2012-08-29 15:19           ` Joseph Glanville
2012-08-29 15:19           ` Joseph Glanville
2012-09-01  6:02 ` Ryan Nicholson
2012-09-04 15:52   ` Tommi Virtanen

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=503D3214.4000503@hastexo.com \
    --to=florian@hastexo.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dieter@vimeo.com \
    --cc=ross@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.