From: Pascal <pa5ca1@gmx.de>
To: ceph-devel@vger.kernel.org
Subject: Re: CephFS: stable release?
Date: Wed, 20 Mar 2013 21:22:27 +0100 [thread overview]
Message-ID: <20130320212227.51db2b47@thinky> (raw)
In-Reply-To: 655D5B8BA34841288B351F2C19C68F34@inktank.com
Am Sun, 24 Feb 2013 14:41:27 -0800
schrieb Gregory Farnum <greg@inktank.com>:
> On Saturday, February 23, 2013 at 2:14 AM, Gandalf Corvotempesta
> wrote:
> > Hi all,
> > do you have an ETA about a stable realease (or something usable in
> > production) for CephFS?
>
> Short answer: no.
>
> However, we do have a team of people working on the FS again as of a
> month or so ago. We're doing a lot of stabilization (bug fixes), code
> cleanups, and utility work in the coming months; we can estimate the
> utility and cleanup work but not the bugs that we'll find, and those
> are our main concern right now. Depending on how the next couple
> months of QA and bug fixing go we should be able to publicize real
> estimates soonish. -Greg
>
> --
> 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
>
Hello Gregory,
is your response still up-to-date?
The FAQ (http://ceph.com/docs/master/faq/) says: "Ceph’s object store (RADOS) is production ready."
Regards,
Pascal
--
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
next prev parent reply other threads:[~2013-03-20 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 10:14 CephFS: stable release? Gandalf Corvotempesta
2013-02-24 22:41 ` Gregory Farnum
2013-03-20 20:22 ` Pascal [this message]
2013-03-20 20:36 ` Greg Farnum
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=20130320212227.51db2b47@thinky \
--to=pa5ca1@gmx.de \
--cc=ceph-devel@vger.kernel.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.