Hey Michael,<div><br></div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<i><font color="#666666">Is there a specific reason why a NAS wouldn't be a good choice to build a swift infrastructure?</font></i></blockquote><div><br></div><div>Why would that make sense to you?</div><div><br></div>
<div>The idea of Swift is to distribute the files over a large amount of "inexpensive" servers and prevent data loss by keeping multiple copies. Whereas in a NAS you typically have fat servers with lots of disks with a RAID on top of them to take care of the data loss.</div>
<div><br></div><div>Using NAS underneath Swift would therefore in my opinion make no sense at all. On the other hand, using Swift as a building block for a NAS system would. (although that would require a file system, since Swift is purely object based).</div>
<div><br></div><div><br></div><div><br></div><div>Kind regards,<div>Frederik Van Hecke</div><div><br></div><div><font color="#999999"><b>T:</b> <a href="tel:%2B32487733713" value="+32487733713" target="_blank">+32487733713</a></font></div>
<div><font color="#999999"><b>E:</b> <a href="mailto:frederik@cluttr.be" target="_blank">frederik@cluttr.be</a></font></div>
<div><font color="#999999"><b>W:</b> <a href="http://www.cluttr.be" target="_blank">www.cluttr.be</a></font></div><div><br></div><div><img src="http://cluttr.be/logo.mail.png"></div><div><br></div><div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif"><pre style="white-space:pre-wrap">
<font color="#999999"><i>This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s)named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation.</i></font></pre>
</span></div><br>
<br><br><div class="gmail_quote">On Fri, Mar 16, 2012 at 14:32, Michaël Van de Borne <span dir="ltr"><<a href="mailto:michael.vandeborne@cetic.be" target="_blank">michael.vandeborne@cetic.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
on the very useful <a href="http://www.referencearchitecture.org" target="_blank">www.referencearchitecture.org</a> website, and in every piece of documentation on Swift, I never found anything like a NAS attached to a storage node. It was all about DAS solution.<br>
Is there a specific reason why a NAS wouldn't be a good choice to build a swift infrastructure?<br>
<br>
thank you<span><font color="#888888"><br>
<br>
<br>
-- <br>
Michaël Van de Borne<br>
R&D Engineer, SOA team, CETIC<br>
Phone: <a href="tel:%2B32%20%280%2971%2049%2007%2045" value="+3271490745" target="_blank">+32 (0)71 49 07 45</a> Mobile: <a href="tel:%2B32%20%280%29472%2069%2057%2016" value="+32472695716" target="_blank">+32 (0)472 69 57 16</a>, Skype: mikemowgli<br>
<a href="http://www.cetic.be" target="_blank">www.cetic.be</a>, rue des Frères Wright, 29/3, B-6041 Charleroi<br>
<br>
<br>
______________________________<u></u>_________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~<u></u>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/~<u></u>openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/<u></u>ListHelp</a><br>
</font></span></blockquote></div><br></div>