All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Kirkwood <mark.kirkwood-6STWZtX7tXAqAMOr+u8IRA@public.gmane.org>
To: Sage Weil <sage-BnTBU8nroG7k1uMJSBkQmQ@public.gmane.org>,
	Blair Bethwaite
	<blair.bethwaite-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Ceph Development
	<ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ceph-users-Qp0mS5GaXlQ@public.gmane.org
Subject: Re: cephfs survey results
Date: Wed, 05 Nov 2014 10:11:53 +1300	[thread overview]
Message-ID: <54594119.5000006@catalyst.net.nz> (raw)
In-Reply-To: <alpine.DEB.2.00.1411040057280.15135-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>

On 04/11/14 22:02, Sage Weil wrote:
> On Tue, 4 Nov 2014, Blair Bethwaite wrote:
>> On 4 November 2014 01:50, Sage Weil <sage-BnTBU8nroG7k1uMJSBkQmQ@public.gmane.org> wrote:
>>> In the Ceph session at the OpenStack summit someone asked what the CephFS
>>> survey results looked like.
>>
>> Thanks Sage, that was me!
>>
>>>   Here's the link:
>>>
>>>          https://www.surveymonkey.com/results/SM-L5JV7WXL/
>>>
>>> In short, people want
>>>
>>> fsck
>>> multimds
>>> snapshots
>>> quotas
>>
>> TBH I'm a bit surprised by a couple of these and hope maybe you guys
>> will apply a certain amount of filtering on this...
>>
>> fsck and quotas were there for me, but multimds and snapshots are what
>> I'd consider "icing" features - they're nice to have but not on the
>> critical path to using cephfs instead of e.g. nfs in a production
>> setting. I'd have thought stuff like small file performance and
>> gateway support was much more relevant to uptake and
>> positive/pain-free UX. Interested to hear others rationale here.
>
> Yeah, I agree, and am taking the results with a grain of salt.  I
> think the results are heavily influenced by the order they were
> originally listed (I whish surveymonkey would randomize is for each
> person or something).
>
> fsck is a clear #1.  Everybody wants multimds, but I think very few
> actually need it at this point.  We'll be merging a soft quota patch
> shortly, and things like performance (adding the inline data support to
> the kernel client, for instance) will probably compete with getting
> snapshots working (as part of a larger subvolume infrastructure).  That's
> my guess at least; for now, we're really focused on fsck and hard
> usability edges and haven't set priorities beyond that.
>
> We're definitely interested in hearing feedback on this strategy, and on
> peoples' experiences with giant so far...
>

Heh, not necessarily - I put multi mds in there, as we want the cephfs 
part to be of similar to the rest of ceph in its availability.

Maybe its because we are looking at plugging it in with an Openstack 
setup and for that you want everything to 'just look after itself'. If 
on the other hand we were wanting merely an nfs replacement, then sure 
multi mds not so important there.

regards

Mark

  parent reply	other threads:[~2014-11-04 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 14:50 cephfs survey results Sage Weil
     [not found] ` <alpine.DEB.2.00.1411030649070.15135-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-11-03 23:36   ` Blair Bethwaite
2014-11-04  9:02     ` Sage Weil
     [not found]       ` <alpine.DEB.2.00.1411040057280.15135-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-11-04  9:35         ` Wido den Hollander
2014-11-04 21:11         ` Mark Kirkwood [this message]
     [not found]           ` <54594119.5000006-6STWZtX7tXAqAMOr+u8IRA@public.gmane.org>
2014-11-04 22:47             ` Sage Weil
2014-11-04 23:04               ` Mark Kirkwood
2014-11-04 23:47         ` Shain Miley
     [not found]     ` <CA+z5DszyU+vDYWnLmvecZ9P6U=9uWOB28Eg7E7=vLtuUQz8Q4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-04 15:33       ` Mariusz Gronczewski
     [not found]         ` <20141104163357.400f83d1-8+6u88+ljCDmz4jMrfixpVaTQe2KTcn/@public.gmane.org>
2014-11-04 16:22           ` Scottix
2014-11-04 16:32           ` Blair Bethwaite
2014-11-04 18:16     ` Patrick Hahn

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=54594119.5000006@catalyst.net.nz \
    --to=mark.kirkwood-6stwztx7txaqamor+u8ira@public.gmane.org \
    --cc=blair.bethwaite-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    --cc=sage-BnTBU8nroG7k1uMJSBkQmQ@public.gmane.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.