From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: Roadmap to production
Date: Thu, 29 Jul 2010 05:45:53 +0000 (UTC) [thread overview]
Message-ID: <i2r4ih$nki$1@dough.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1007271024060.28672@cobra.newdream.net
Am Wed, 28 Jul 2010 11:25:40 -0700 schrieb Sage Weil:
> On Thu, 22 Jul 2010, Thomas Mueller wrote:
>> reading http://ceph.newdream.net/roadmap/ leaves me with some
>> questions. :)
>>
>> * is there some roadmap when CEPH will be official announced
>> "production ready"
>
> These are good questions. :)
>
> I've made the Ceph site link directly into the redmine roadmap, where
> we'll be maintaining a detailed set of issues (features, bugs) for each
> upcoming release along with a target release date. The roadmap now
> includes a v1.0, which will be something we at least will cautiously
> deploy in production. I would like to get there (or close to it) by the
> end of the year.
>
> I prefer to avoid "production ready" as that is a bit of a subjective
> term. Different people have different stability requirements and
> expectations. That said, I would like v1.0 to be something I am
> comfortable encouraging people to use in real (but non-critical)
> deployments.
>
answering here the question from another thread because IMHO it fits
better:
> > what leads me to my other question: when will ceph be considered
> > "stable"?
> Soon? I'd be interested in hearing what you (or anyone else) expect
> from a "stable" v1.0 release.
as storage is a fundamental service there are for sure other "stable"
demands than for a newsreader/mailclient/whateveruncriticalapp.
I'll give it a try to describe my idea of stable:
- stable means promised features (http://ceph.newdream.net/about/) work
reliable
- no workarounds needed to use these features
- (at least) in a series of stable releases (aka "1.x") i can upgrade
without downtime
- in a series of stable releases a can do a rolling upgrade
- in a stable series there no design changes introduced
- Thomas
next prev parent reply other threads:[~2010-07-29 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 12:13 Roadmap to production Thomas Mueller
2010-07-28 18:25 ` Sage Weil
2010-07-29 5:45 ` Thomas Mueller [this message]
2010-07-29 12:31 ` Anton VG
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='i2r4ih$nki$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--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.