Aggregated news from external sources
The v0.19 release is finally here. The focus this past cycle was on stability and the disk format, and things have improved greatly in that area. Our plan is to make any future disk format changes roll forward, so that users won’t need to rebuild their file systems. The protocol has also grown feature bits that so it is at least possible to make protocol changes transparent; whether we do so or not will depend on the severity of the change and cost of maintaining compatibility.
Overall, things are looking good. If you’ve been standing on the sidelines waiting for something more stable to test, now is a good time to try things out. There are some lingering OSD performance problems (see below), and we are still a long ways off from something we would recommend for use in a production environment, but otherwise this release is looking pretty good for evaluation purposes.
Changes since v0.18 include:
On the kernel client side of things,
Notably, there are major revisions underway with the way the storage daemon cosd interacts with btrfs, and these are sufficiently intrusive and untested that they did not make it into this release. They should be in v0.20. That means that OSD performance is still not great in v0.19. (So far performance with the new code is much much better.)
The primary focus areas for v0.20 will be