Open Stack

On 21 February 2014 16:50, Adam Lawson <alawson at aqorn.com> wrote:

> This is a first for me as well so I'm learning as I go here. But I'm
> planning to build the rings with r1z100, r2z200 etc with each device. I
> found help over at Swiftstack with their articles if that helps. More than
> willing to share any/all successes we see along the way.
>
>
Hi Adam,

Could you specify which articles in particular helped?

Thanks,
Luis


>
> *Adam Lawson*
> AQORN, Inc.
> 427 North Tatnall Street
> Ste. 58461
> Wilmington, Delaware 19801-2230
> Toll-free: (888) 406-7620
>
>
>
> On Fri, Feb 14, 2014 at 4:18 PM, Remo Mattei <remo at italy1.com> wrote:
>
>> Just adding a question,
>> what config options have you used to make the multi-region? I have done a
>> few swift but none with multi.
>>
>> Thanks
>> On Feb 14, 2014, at 15:59, Richard Raseley <richard at raseley.com> wrote:
>>
>> On Tue, Feb 11, 2014 at 3:38 PM, Adam Lawson <alawson at aqorn.com> wrote:
>>
>>> Hola peoples.
>>>
>>> I'm working on a general purpose Swift deployment that needs to scale
>>> globally. For example, nodes in West Coast, East Coast, EU and APAC. We
>>> have a Swift PoC cluster that spans West Coast and EU and it works fine,
>>> replicating using zones for now.
>>>
>>> For those who are scaling to that degree, are you building multiple
>>> unique clusters and replicating between them somehow or using regions and
>>> replicating within essentially one giant cluster and using affinity rules
>>> like read_affinity and write_affinity*?
>>>
>>
>> Utilizing the region capability of Swift is a good option depending on
>> your use case (I've used a region-based configuration in one production
>> deployment). Can you talk more about your data structure / access patterns
>> in order to help myself (and others) give better advice?
>>
>>
>>>
>>> *Adam Lawson*
>>> AQORN, Inc.
>>> 427 North Tatnall Street
>>> Ste. 58461
>>> Wilmington, Delaware 19801-2230
>>> Toll-free: (888) 406-7620
>>>
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to     : openstack at lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>>
>> !DSPAM:1,52feb08f274501761617984!
>> _______________________________________________
>>
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>> !DSPAM:1,52feb08f274501761617984!
>>
>>
>>
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140221/8a1279c7/attachment.html>