openstack/openstack-manuals
Code Issues Proposed changes

Max partitions/disks in Operational considerations Arch Design Guide misworded

Browse Source 
Revise Scaling Object Storage section of Operational considerations in OpenStack
Architecture Design Guide. Guide uses disks where it should say partitions and
reword incorrect sentence.

Change-Id: Ida78a215ad44da65dc254f5f7f39554f1b8b9dbd
Closes-bug: #1513469
This commit is contained in:
MikeG451 2017-01-31 17:48:03 +00:00
parent 38207463ca
commit 9499a7d293
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/arch-design/source/storage-focus-operational-considerations.rst
View File

@ -218,15 +218,15 @@ careful planning and consideration. In the design phase, it is important
to determine the maximum partition power required by the Object Storage
service, which determines the maximum number of partitions which can
exist. Object Storage distributes data among all available storage, but
a partition cannot span more than one disk, so the maximum number of
partitions can only be as high as the number of disks.
a partition cannot span more than one disk, although a disk can have
multiple partitions.
For example, a system that starts with a single disk and a partition
power of 3 can have 8 (2^3) partitions. Adding a second disk means that
each has 4 partitions. The one-disk-per-partition limit means that this
system can never have more than 8 disks, limiting its scalability.
system can never have more than 8 partitions, limiting its scalability.
However, a system that starts with a single disk and a partition power
of 10 can have up to 1024 (2^10) disks.
of 10 can have up to 1024 (2^10) partitions.
As you add back-end storage capacity to the system, the partition maps
redistribute data amongst the storage nodes. In some cases, this