Brebner, Gavin asked:
>Price ! Why provide expensive redundant storage when cheap disks will do just
>as well ?
Because you are interested in the total cost.
Using excessive network replication rather than local replication makes for a
more expensive
And less robust solution -- as long as the
There are numerous reasons why you would want your Swift Object Server to also
host a NAS server.
But whether you are talking Nova volumes or Swift Objects, you would generally
want the Volume Server
or Object Server to access those "directly" rather than via NAS over a general
network connecti
>
>
> *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.
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
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 integrat
Michaël Van de Borne
> Sent: Friday, March 16, 2012 2:33 PM
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Swift: NAS or DAS?
>
> Hi all,
>
> on the very useful www.referencearchitecture.org website, and in every
> piece of documentation on Swift, I never found
Hey Michael,
*Is there a specific reason why a NAS wouldn't be a good choice to build a
> swift infrastructure?*
Why would that make sense to you?
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
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 wrot
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 infrastru
9 matches
Mail list logo
