Open Stack

On Tue, May 20, 2014 at 5:32 PM, Kuo Hugo <tonytkdk at gmail.com> wrote:

> Hi Clint,
>
> No it's not necessary to separate a cluster into several zones in general.
> The region and zone information will be invoked by ring-builder to assign
> partitions as-unique-as possible.
> If you do have several nodes be placed in a remote datacenter with higher
> network latency, then these nodes should be in a different region.
> If you do have several nodes in different room but in same building with
> low network latency, you can indicate these nodes are in different zone.
>
> So basically, for all nodes in same rack, room, DC. You can simply to use
> a single zone without any problem.
>
>
Thanks for the information and clarification


> I observed the replica been set to 1 only. Is this a production
> environment ?  In current Swift implementation, the replica number is not
> able to change dynamically(Storage policy will make it more flexible). You
> may want to have at least 3 replicas in production cluster.
>
> For part power, that's fine with higher value. The impact is on the
> performance and memory consumption. If your cluster will expand to more
> nodes with over 500TB capacity in the future, you definitely don't want
> part power 8. It's not hurt with current value. Don't to worry about it for
> a testing cluster.
>
>
>
It's a Research Installation, at the moment requirements are not fully
defined so I am sure I will end up re-installing the installation several
times.  For the moment I rebuilt the rings going with 8 2 1



> Cheers // Hugo
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140521/38a78cd4/attachment.html>