CEPH filesystem development
 help / color / mirror / Atom feed
From: Dieter Kasper <d.kasper@kabelmail.de>
To: Ross Turk <ross@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	"Dieter Kasper (KD)" <d.kasper@kabelmail.de>
Subject: Re: Integration work
Date: Tue, 28 Aug 2012 20:51:16 +0200	[thread overview]
Message-ID: <20120828185116.GC9872@oder.mch.fsc.net> (raw)
In-Reply-To: <503D0A00.2080905@inktank.com>

Hi Ross,

focusing on core stability and feature expansion for RBD was the right appoach 
in the past and I feel you have reached an adequate maturity level here.

Performance enhancements - especially to reduce the latency of a single IO / increase IOPS -
and a stronger engagement on the CephFS client would be very much appreciated.
A stable and fast CephFS client would allow an efficient integration with
- (clustered) NFS (v3 and v4)
- (clustered) Samba v4


Cheers,
-Dieter


On Tue, Aug 28, 2012 at 08:12:16PM +0200, Ross Turk 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? For example, are you interested in seeing Inktank spend more of 
> its resources improving interoperability with Apache CloudStack or 
> Eucalyptus? How about Xen?
> 
> Please share your thoughts. We want to contribute in the best way 
> possible with the resources we have, and your input can help.
> 
> Thx,
> Ross
> 
> --
> Ross Turk
> Community, Ceph
> @rossturk @inktank @ceph
> 
> 
> 
> --
> 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


  parent reply	other threads:[~2012-08-28 18:52 UTC|newest]

Thread overview: 19+ 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
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 [this message]
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-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=20120828185116.GC9872@oder.mch.fsc.net \
    --to=d.kasper@kabelmail.de \
    --cc=ceph-devel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox