← Back to team overview

openstack team mailing list archive

Re: Swift: NAS or DAS?

 

Paulo,



> *I don't think anything prevents integrating Swift storage nodes with a
> NAS. Latency could be increased but depending on load, network capacity
> (shared vs dedicated), and use of caching, it is possible to achieve a good
> performance.*


Yes, but why would you do so..

Using NAS as storage target for Swift will as said increase the CAPEX price
and latency. And instead of 1 layer you'll have to 2 layers to manage and
maintain, which will increase operating cost. The only reason I can think
of why you might consider this is if you have a shitload of NAS systems in
your DC that you don't want to throw out the door just yet..

They both address the same problem (file storage) through a different
approach. NAS is practical for users, with NFS support built into
practically every OS. But there's a reason why we just don't stick to NAS
systems, they're expensive and hard to scale.

Using NAS as building block of Swift would take away the ease of use for
the user that NFS gives them (and what they're familiar with) but would
still leave you with all the problems at the operational side of the story.
Even worse, it would make it even more expensive and complicated.



*This link shows the integration of NexentaStor (a NAS/SAN integrated
> storage solution) with Openstack Nova:
> http://mirantis.blogspot.com/2011/11/converging-openstack-with-nexenta.html
> *



That's Nova, not Swift..
In case of Nova, a NAS or SAN approach makes very much sense.



Kind regards,
Frederik Van Hecke

*T:*  +32487733713
*E:*  frederik@xxxxxxxxx
*W:* www.cluttr.be



*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.*




On Fri, Mar 16, 2012 at 15:21, Paulo Ricardo Motta Gomes <
pauloricardomg@xxxxxxxxx> wrote:

> I don't think anything prevents integrating Swift storage nodes with a
> NAS. Latency could be increased but depending on load, network capacity
> (shared vs dedicated), and use of caching, it is possible to achieve a good
> performance.
>
> This link shows the integration of NexentaStor (a NAS/SAN integrated
> storage solution) with Openstack Nova:
> http://mirantis.blogspot.com/2011/11/converging-openstack-with-nexenta.html
>
> 2012/3/16 John Dickinson <me@xxxxxx>
>
>> Generally, you would introduce latency in the storage system by using a
>> NAS attached to a storage drive. Also, at scale, your costs will be
>> dominated by drive, so you will want to optimize the storage nodes for
>> dense, cheap storage.
>>
>> --John
>>
>>
>> On Mar 16, 2012, at 8:32 AM, Michaël Van de Borne wrote:
>>
>> > Hi all,
>> >
>> > on the very useful www.referencearchitecture.org 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.
>> > Is there a specific reason why a NAS wouldn't be a good choice to build
>> a swift infrastructure?
>> >
>> > thank you
>> >
>> >
>> > --
>> > Michaël Van de Borne
>> > R&D Engineer, SOA team, CETIC
>> > Phone: +32 (0)71 49 07 45 Mobile: +32 (0)472 69 57 16, Skype:
>> mikemowgli
>> > www.cetic.be, rue des Frères Wright, 29/3, B-6041 Charleroi
>> >
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Paulo Ricardo
>
> --
> European Master in Distributed Computing***
> Royal Institute of Technology - KTH
> *
> *Instituto Superior Técnico - IST*
> *http://paulormg.com*
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>

Follow ups

References