Sorry I flaked this morning for the RGW Snapshot blueprint discussion. I thought the summit was next week; I was completely unprepared. I see the pad was updated with some new details. I like the better direction. I've always had concerns that the independent rados snapshots were going to cause atomicity problems, but I'm pretty sure that it could work for my use case. That's because I have a pretty easy use case, and I can work around the edge cases. This blueprint has a much broader appeal to other users. Unfortunately, this new blueprint is beyond my abilities. I'm struggling to implement my original blueprint. Having RadosGW manage it's own snapshots requires a much deeper understanding of the codebase than something a weekend coder is going to be able to do. I'm still able to work on documentation and testing, just not coding. Where does that leave this blueprint? -- 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
