Hi everyone, I wanted to mention just a few things on this thread. The first is obvious: we are extremely concerned about stability. However, Ceph is a big project with a wide range of use cases, and it is difficult to cover them all. For that reason, Inktank is (at least for the moment) focusing in specific areas (rados, librbd, rgw) and certain platforms. We have a number of large production customers and non-customers now who have stable environments, and we are committed to a solid experience for them. We are investing heavily in testing infrastructure and automation tools to maximize our ability to test with limited resources. Our lab is currently around 14 racks, with most of the focus now on utilizing those resources as effectively as possible. The teuthology testing framework continues to evolve and our test suites continue to grow. Unfortunatley, this has been an area where it has been difficult for others to contribute. We are eager to talk to anyone who is interested in helping. Overall, the cuttlefish release has gone much more smoothly than bobtail did. That said, there are a few lingering problems, particularly with the monitor's use of leveldb. We're waiting on some QA on the pending fixes now before we push out a 0.61.3 that I believe will resolve the remaining problems for most users. However, as overall adoption of ceph increases, we move past the critical bugs and start seeing a larger number of "long-tail" issues that affect smaller sets of users. Overall this is a good thing, even if it means a harder job for the engineers to triage and track down obscure problems. The mailing list is going to attract a high number of bug reports because that's what it is for. Although we believe the quality is getting better based on our internal testing and our commercial interactions, we'd like to turn this into a more metrics driven analysis. We welcome any ideas on how to do this, as the obvious ideas (like counting bugs) tend to scale with the number of users, and we have no way of telling how many users there really are. Thanks- sage On Thu, 30 May 2013, Youd, Douglas wrote: > Completely agree as well. I'm very keen to see widespread adoption of Ceph, but battling against the major vendors is a massive challenge not helped by even a small amount of instability. > > Douglas Youd > Direct +61 8 9488 9571 > > > -----Original Message----- > From: ceph-users-bounces@xxxxxxxxxxxxxx [mailto:ceph-users-bounces@xxxxxxxxxxxxxx] On Behalf Of Chen, Xiaoxi > Sent: Thursday, 30 May 2013 1:40 AM > To: Wolfgang Hennerbichler > Cc: ceph-users@xxxxxxxxxxxxxx > Subject: Re: increasing stability > > Cannot agree more,when I trying to promote ceph to internal state holder,they always complaining the stability of ceph,especially when they are evaluating ceph with high enough pressure, ceph cannot stay heathy during the test. > > > > ???? iPhone > > ? 2013-5-29?19:13?"Wolfgang Hennerbichler" <wolfgang.hennerbichler@xxxxxxxxxxxxxxxx> ??? > > > Hi, > > > > as most on the list here I also see the future of storage in ceph. I > > think it is a great system and overall design, and sage with the rest > > of inktank and the community are doing their best to make ceph great. > > Being a part-time developer myself I know how awesome new features > > are, and how great it is to implement them. > > On the other hand I think cuttlefish is in a state where I am not > > feeling easy when saying: ceph is stable, go ahead, use it. I do > > happen to have to do a lot of presentations on ceph recently, and I'm > > doing a lot of lobbying for it. > > I also realize that it's not easy to develop a distributed system like > > ceph, and I know it needs time and a community to test. I'm just > > wondering if it might be better for the devs to keep their focus right > > now on fixing nasty bugs (even more as they do already), and make the > > mon's and osd's super-stable. > > I have no insight on the development cycles, so chances are you're > > doing this right now already. I'm just saying: I'd love to see ceph > > take over the storage world, and for that we need it in super stable states. > > > > Then ceph can succeed big time. > > > > Sorry for the noise, but I really wanted to get rid of this :) > > Wolfgang _______________________________________________ > > ceph-users mailing list > > ceph-users@xxxxxxxxxxxxxx > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > ________________________________ > > ZettaServe Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately if you have received this email by mistake and delete this email from your system. Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. ZettaServe Pty Ltd accepts no liability for any damage caused by any virus transmitted by this email. > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |