This is already supported in Swift with the concept of availability zones. Swift will place each replica in different availability zones, if possible. If you only have one zone, Swift will place the replicas on different machines. If you only have one machine, Swift will place the replicas on different drives.
There are active discussions right now about how Swift can support a tier above these availability zones: "regions". A region would be defined by a hogher latency link and can provide additional data durability, and, depending on your deployment details, better availability. http://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/ has more info on the ideas we're talking about. --John On Nov 1, 2012, at 8:45 AM, Leandro Reox <leandro.r...@gmail.com> wrote: > Hi guys, > > Any plans to implement something like hadoop rack-awareness where we can > define "rack" spaces to guarantee that a copy of an object is stored for > example on another datacenter, on another coast. Or should this be managed by > container sync to the other datacenter > > I think that this can be a nice-to-have feature, i dont know if its on the > dev roadmap > > Best > Lean > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : firstname.lastname@example.org > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp
Description: S/MIME cryptographic signature
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : email@example.com Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp