<font color="#000000"><font><font face="courier new,monospace">Niceeee, a good reason to wait to Grizzly (?) with our arms wide open!</font></font></font><div><font color="#000000"><font><font face="courier new,monospace"><br>
</font></font></font></div><div><font color="#000000"><font><font face="courier new,monospace">Thanks for confirming that John / Lean !</font></font></font></div><div class="gmail_extra"><br clear="all"><div><font><b><br>
</b></font></div><div><font><b><img src="http://s14.postimage.org/sg1lztqep/cloudbuilders_Logo_last_small.png" width="96" height="58"><br></b></font></div><font><b>Alejandro Comisario <br>
#melicloud CloudBuilders</b></font><br>
<font color="#666666"><span style="font-size:6pt;color:gray" lang="ES">Arias 3751, Piso 7 (C1430CRG) <br>
Ciudad de Buenos Aires -
Argentina<br>
Cel: +549(11) 15-3770-1857<br>
Tel : +54(11) 4640-8443</span></font><br>
<br><br><div class="gmail_quote">On Thu, Nov 1, 2012 at 2:07 PM, Leandro Reox <span dir="ltr"><<a href="mailto:leandro.reox@gmail.com" target="_blank">leandro.reox@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ale, <br><br>Guess that what <a href="http://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/" style="font-family:arial,sans-serif;font-size:13px" target="_blank">http://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/</a> link latency feature is meant to be ... but John can confirm that :)<br>
<br>Best<br>Lean<div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 1, 2012 at 1:49 PM, Alejandro Comisario <span dir="ltr"><<a href="mailto:alejandro.comisario@mercadolibre.com" target="_blank">alejandro.comisario@mercadolibre.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font color="#000000" face="courier new, monospace">John, what i think would be terrific ( i hope is not implemented, if not im gonna feel a dunce ) if, for latency matters, suppose you have 4 zones, 2 on each datacenter, and on each datacenter, you have 2 proxies for example.</font><div>
<font color="#000000" face="courier new, monospace"><br></font></div><div><font color="#000000" face="courier new, monospace">De idea would be that there were some kind of mechanism to tell the ring, what nodes are under what proxies, to give some kind of prefferece regarding latency, and for example not having a proxy on DC1 to cross the country to get an object from a datanode in DC2.</font></div>
<div><font color="#000000" face="courier new, monospace"><br></font></div><div><font color="#000000" face="courier new, monospace">Have you thought anything like it?</font></div><div><font color="#000000" face="courier new, monospace">If not, im wondering how, for example rackspace handles this kind of issues ( ignoring all the CDN thing )</font></div>
<div><font color="#000000" face="courier new, monospace"><br></font></div><div><font color="#000000" face="courier new, monospace">Cheers.<br></font><div class="gmail_extra"><br clear="all"><div><font><b>---------------</b></font></div>
<div><b>Alejandrito</b></div><br><div class="gmail_quote"><div>On Thu, Nov 1, 2012 at 12:55 PM, John Dickinson <span dir="ltr"><<a href="mailto:me@not.mn" target="_blank">me@not.mn</a>></span> wrote:<br>
</div><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
<br>
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. <a href="http://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/" target="_blank">http://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/</a> has more info on the ideas we're talking about.<br>
<br>
--John<br>
<div><div><br>
<br>
<br>
<br>
On Nov 1, 2012, at 8:45 AM, Leandro Reox <<a href="mailto:leandro.reox@gmail.com" target="_blank">leandro.reox@gmail.com</a>> wrote:<br>
<br>
> Hi guys,<br>
><br>
> 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<br>
><br>
> I think that this can be a nice-to-have feature, i dont know if its on the dev roadmap<br>
><br>
> Best<br>
> Lean<br>
</div></div>> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
<br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div></div></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>