On Mon, 2016-06-27 at 22:18 +0000, Sage Weil wrote: > Hi Sebastien, > > Do you mind updating us on the current status of > libradosstriper? Where does it stand feature-wise with what you > need, how are you currently using it or how do you plan to use it, > and what is still missing? Most of the feature we need are there and they are being used, including in production. However, I have a couple of improvements to propose, in particular a faster remove implementation (using async removal of the subparts) and the few async APIs I've mentioned at the ceph day. I've just prepared the commits in the plane yesterday, I'll try to create the pull request this week. > Also, one thing we really want to see is test coverage for the code > so that we can comfortably point users toward it. This ideally would > look something like the ceph_test_rados_api_* tests that verify > individual operations behave as expected, and/or something like > ceph_test_rados that throws random operations at is and verifies it > returns correct results that match its in-memory model. I believe the test coverage for individual operations is complete for what exists, and the new improvements will come with their tests too. They are called ceph_test_radosstriper. Now I do not think I have the random operation one. Probably something to be added. Cheers, Sebastien -- 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
