Thanks for the timeline. We would like to see file striping. Instead of replicating the data it would be even better if we are able to maintain parity amongst the objects. No opensource project has this. What do you think? On Fri, Sep 24, 2010 at 6:48 PM, Sage Weil <sage@xxxxxxxxxxxx> wrote: > I've been working on keeping the roadmap in the project tracker up to date > with the current release schedule and the features targetting each > version. ÂThat can be found at > > Â Â Â Âhttp://tracker.newdream.net/projects/ceph/roadmap > > The main exception is that many bugs end up accumulating with the next > stable release as a target (e.g., v0.21.4), and then (when they're not > resolved) get pushed off to the next release. ÂAnd as releases get further > into the future the picture gets a bit for hazy. > > Those caveats aside, the basic schedule and goals are: > > v0.22 (1-2 weeks away) > Â- Stable and usable clustered MDS in non-failure conditions. ÂWe will > encourage anybody to test the clustered MDS for correctness, performance, > and stability, and to report any and all issue. > Â- Background OSD scrubbing. ÂThis will help us catch remaining object > replication/recovery problems sooner rather than later. > Â- Stable RBD. > > v0.23 (6 weeks away) > Â- Stable clustered MDS failure recovery. > Â- Stable directory fragmentation and defragmetnation. Â(Fragmentation is > what faciliates very large directories and the distribution of large > directories over multiple nodes in the MDS cluster.) > Â- RBD image locking. > Â- Stable radosgw (S3 compatible REST proxy) > > v1.0 (Christmas!) > Â- Some basic fsck functionality > Â- Cautious use in production setting. > > This is all, of course, subject to change depending on what issues come up > as we ramp up our testing and QA. > > I'm also interested in hearing from you what features or issues you are > most interested in seeing us focus on. ÂWhat are your use cases? ÂIf you > have done any testing, what problems have you run into? ÂIf you haven't, > what is preventing you from testing (besides some promise of stability or > production readiness)? > > sage > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at Âhttp://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
