Add region in ring structure & deployment guide

Deployment guide does not talk about the region. Also, it does not
specify that regions and zones need to be ints.

This patch adds brief description about region and changes numbers
to int. Also, adds region in the document that talks about ring data
struture.

Change-Id: I04ce42fb3e5c1f08e7f7ff6be23482cee8bdeb71
Partial-Bug: #1583551
This commit is contained in:
Mohit Motiani 2016-05-23 21:10:08 +00:00
parent 1ba56c64e9
commit 90627f903a
2 changed files with 8 additions and 3 deletions

View File

@ -101,8 +101,12 @@ into consideration can include physical location, power availability, and
network connectivity. For example, in a small cluster you might decide to
split the zones up by cabinet, with each cabinet having its own power and
network connectivity. The zone concept is very abstract, so feel free to use
it in whatever way best isolates your data from failure. Zones are referenced
by number, beginning with 1.
it in whatever way best isolates your data from failure. Each zone exists
in a region.
A region is also an abstract concept that may be used to distinguish between
geographically separated areas as well as can be used within same datacenter.
Regions and zones are referenced by a positive integer.
You can now start building the ring with::

View File

@ -80,7 +80,8 @@ the list of devices is a dictionary with the following keys:
====== ======= ==============================================================
id integer The index into the list devices.
zone integer The zone the devices resides in.
zone integer The zone the device resides in.
region integer The region the zone resides in.
weight float The relative weight of the device in comparison to other
devices. This usually corresponds directly to the amount of
disk space the device has compared to other devices. For