Re: [Openstack] suggestion for data location compliance in swift

The idea to make ring implementation pluggable seems nice. At the same time I am thinking that many developers might not will feel comfortable with modifying existing ring structure, since it *works* :) Probably, the other viable option for allowing data location compliance is to implement

Re: [Openstack] suggestion for data location compliance in swift

j...@piston.cc *To:* Rostyslav Slipetskyy rslipets...@yahoo.com *Cc:* OpenStack openstack@lists.launchpad.net *Sent:* Tue, May 31, 2011 1:45:01 AM *Subject:* Re: [Openstack] suggestion for data location compliance in swift This was one of the use cases that drove the design discussion

Re: [Openstack] suggestion for data location compliance in swift

Well, since the pluggable ring idea *was* about this as well (I'm pretty sure, since I proposed it), maybe it's time to talk merkle trees ;) I'll circle back with notmyname and see what makes sense for breaking up this discussion into manageable chunks. Joshua McKenty Piston Cloud Computing,

Re: [Openstack] suggestion for data location compliance in swift

This was one of the use cases that drove the design discussion on decoupling the swift ring implementation from the rest of swift (along with supporting multiple tiers of hardware). See https://blueprints.launchpad.net/swift/+spec/swift-pluggable-hashing-ring for the basic proposal, however,