From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ceph
Date: Fri, 31 Jul 2009 22:24:32 -0700 [thread overview]
Message-ID: <28CF259C-21F4-4071-806E-6D5DA02C985D@sun.com> (raw)
In-Reply-To: <140e7ec30907300931v3dbd8ebdl32a6b74792be144@mail.gmail.com>
On Jul 30, 2009, at 9:31 AM, sqweek wrote:
> 2009/7/30 Roman V Shaposhnik <rvs@sun.com>:
>> This is sort of off-topic, but does anybody have any experience with
>> Ceph?
>> http://ceph.newdream.net/
>>
>> Good or bad war stories (and general thoughts) would be quite
>> welcome.
>
> Not with ceph itself, but the description and terminology they use
> remind me a lot of lustre (seems like it's a userspace version) which
> we use at work. Does a damn fine job - as long as you get a stable
> version. We have run into issues trying out new versions several
> times...
I guess that sums up my impression of ceph so far: I don't see where it
would fit. I think that in HPC it is 99% Lustre, in enterprise it is
either
CIFS or NFS, etc.
There's some internal push for it around here so I was wondering
whether I missed a memo once again...
Thanks,
Roman.
next prev parent reply other threads:[~2009-08-01 5:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 0:43 Roman V Shaposhnik
2009-07-30 16:31 ` sqweek
2009-08-01 5:24 ` Roman Shaposhnik [this message]
2009-08-01 5:41 ` ron minnich
2009-08-01 5:53 ` Roman Shaposhnik
2009-08-01 15:47 ` ron minnich
2009-08-04 1:32 ` Roman V Shaposhnik
2009-08-04 2:56 ` ron minnich
2009-08-04 5:07 ` roger peppe
2009-08-04 8:23 ` erik quanstrom
2009-08-04 8:52 ` roger peppe
2009-08-04 9:55 ` C H Forsyth
2009-08-04 10:25 ` roger peppe
2009-08-04 14:45 ` ron minnich
2009-08-04 23:56 ` Roman V Shaposhnik
2009-08-04 23:51 ` Roman V Shaposhnik
2009-08-04 7:23 ` Tim Newsham
2009-08-05 0:27 ` Roman V Shaposhnik
2009-08-05 3:30 ` Tim Newsham
2009-08-04 8:43 ` Steve Simon
2009-08-05 0:01 ` Roman V Shaposhnik
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=28CF259C-21F4-4071-806E-6D5DA02C985D@sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).