Open Stack

When deploying Swift globally, this thread helped:

Unique as possible replicates in this order:
Regions > Zones > Servers > Devices > Device with fewest replicas

http://lists.openstack.org/pipermail/openstack-dev/2013-March/006802.html

The above config helped. Here's what I'm thinking:

*Logical setup:*

Region 1
> Zone 10
> 10.1.10.100
> sdb1
> sdc1
> sdd1
> sde1
> sdf1
> Zone 11
> 10.1.11.100
> sdb1
> sdc1
> sdd1
> sde1
> sdf1
> Region 2
> Zone 20
> 10.2.20.100
> sdb1
> sdc1
> sdd1
> sde1
> sdf1
> Zone 21
> 10.2.21.100
> sdb1
> sdc1
> sdd1
> sde1
> sdf1
> # Create ring
> swift-ring-builder account.builder create 10 3 1
> swift-ring-builder account.builder add r1z10-10.1.10.100:6002/sdb1 100
> swift-ring-builder account.builder add r1z10-10.1.10.100:6002/sdc1 100
> swift-ring-builder account.builder add r1z10-10.1.10.100:6002/sdd1 100
> swift-ring-builder account.builder add r1z10-10.1.10.100:6002/sde1 100
> swift-ring-builder account.builder add r1z10-10.1.10.100:6002/sdf1 100
> swift-ring-builder account.builder add r1z11-10.1.20.100:6002/sdb1 100
> swift-ring-builder account.builder add r1z11-10.1.20.100:6002/sdc1 100
> swift-ring-builder account.builder add r1z11-10.1.20.100:6002/sdd1 100
> swift-ring-builder account.builder add r1z11-10.1.20.100:6002/sde1 100
> swift-ring-builder account.builder add r1z11-10.1.20.100:6002/sdf1 100
> swift-ring-builder account.builder add r2z20-10.2.20.100:6002/sdb1 100
> swift-ring-builder account.builder add r2z20-10.2.20.100:6002/sdc1 100
> swift-ring-builder account.builder add r2z20-10.2.20.100:6002/sdd1 100
> swift-ring-builder account.builder add r2z20-10.2.20.100:6002/sde1 100
> swift-ring-builder account.builder add r2z20-10.2.20.100:6002/sdf1 100
> swift-ring-builder account.builder add r2z21-10.2.21.100:6002/sdb1 100
> swift-ring-builder account.builder add r2z21-10.2.21.100:6002/sdc1 100
> swift-ring-builder account.builder add r2z21-10.2.21.100:6002/sdd1 100
> swift-ring-builder account.builder add r2z21-10.2.21.100:6002/sde1 100
> swift-ring-builder account.builder add r2z21-10.2.21.100:6002/sdf1 100
>
> # Rebalance
> swift-ring-builder account.builder rebalance


Haven't run this yet but pretty sure the ring builder will work fine.




*Adam Lawson*
AQORN, Inc.
427 North Tatnall Street
Ste. 58461
Wilmington, Delaware 19801-2230
Toll-free: (888) 406-7620



On Fri, Feb 21, 2014 at 2:20 PM, Luis de Bethencourt <luis at debethencourt.com
> wrote:

> 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/72bfa4af/attachment.html>