openstack
/
openstack-manuals
Code Issues Proposed changes

[arch-design] Rewrite segregation example 

In the chapter "massively scalable", the description of segregation
example doesn't match the figure. This patch fix the description
so that it matches the figure.

Change-Id: Ib3429c2efcbfa1e1ecc994e8fb7f6dae9f241f1f
Closes-Bug: #1484771
This commit is contained in:
KATO Tomoyuki 2015-12-26 14:57:41 +09:00
parent 26f534d25e
commit 755d7176f8
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/arch-design/source/massively-scalable-technical-considerations.rst
View File

@ -98,10 +98,13 @@ to schedule instances to a non-default availability zone of nova.
Segregation example
-------------------
In this example the cloud is divided into two regions, one for each site, with
two availability zones in each based on the power layout of the data centers.
In this example, the cloud is divided into two regions, an API cell and
three child cells for each region, with three availability zones in each
cell based on the power layout of the data centers.
The below figure describes the relationship between them within one region.
.. figure:: figures/Massively_Scalable_Cells_regions_azs.png
A number of host aggregates enable targeting of virtual machine instances
using flavors, that require special capabilities shared by the target hosts
such as SSDs, 10 GbE networks, or GPU cards.
.. figure:: figures/Massively_Scalable_Cells_regions_azs.png