> We're currently working on rbd snapshots and there were a few header > changes. Currently snapshot creation is being done via the rbd kernel > driver, but we're planning in adding that capability to the rbdtool. > Once this works, it'll be easy to implement the kvm-rbd snapshots. > Note that at this point snapshots are read-only. Adding a writable > snapshots, as well as snapshots branching would be awesome, however, > it looks like it's not going to be easy to integrate it easily into > the current system. So probably the easiest at this point would be to > have some revert-to-snapshot capability. This is great news. > The next thing would be making it safer for multiple clients to > collaborate on a single rbd image., e.g., adding atomic header > modification operations and such. This requires some changes in the > osd (new ops), and will probably require adding some new librados api > functions. Another thing that would be interesting is support for releasing sectors (aka TRIM support). However I think this would require some kind of sector map, where we store information about allocated and released sectors. At the moment I'm not sure if it is worth the effort and the performance impact. Maybe we should add a flag to the header, that indicates the existence of a sector map. This way we could decide about this feature later without changing the header again. Christian -- 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
