Skip to content

Commit 5d47851

Browse files
committed
minor corrections in doc
1 parent 4158421 commit 5d47851

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

source/adminguide/vm_volume_allocators.rst

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Use global configuration parameter:
5454
Volme Allocator
5555
--------------
5656

57-
VOlume allocator returns suitable storage pools available in the cluster where volumes of the given instance can be created.
57+
Volume allocator returns suitable storage pools available in the cluster where volumes of the given instance can be created.
5858
To decide the storage pools, it considers factors such as disk offering, storage capactiy, availability scope etc.
5959

6060
Volume allocator supports following algorithms to select a host in the cluster:
@@ -65,15 +65,16 @@ Volume allocator supports following algorithms to select a host in the cluster:
6565
Algorithm Description
6666
============================= ========================
6767
random Selects a storage pool in the cluster randomly.
68-
firstfit Selects the first available storage pool in the cluster.
69-
userdispersing Selects the storage pool running least instances for the account, aims to spread out the instances belonging to a single user account.
68+
firstfit Selects the first available storage pool in the cluster.
69+
userdispersing Selects the storage pool running least instances for the account, aims to spread out the instances belonging to a single user account.
7070
userconcentratedpod_random Selects the storage pool randomly aiming to keep all instances belonging to single user account in same pod.
7171
userconcentratedpod_firstfit Selects the first suitable pool from a pod running most instances for the user.
7272
firstfitleastconsumed Selects the first storage pool after sorting eligible pools by least allocated resources.
7373
============================= ========================
7474

75-
Before 4.21.0, there was no named algorithm setting like vm.allocation.algorithm and volume allocator used to use the algorithm configured for VM allocator.
75+
.. note::
76+
Since 4.21.0, dedicated named configuration is provided for admin to configure volume allocation algorithm.
77+
78+
**volume.allocation.algorithm**: random (default)
7679

77-
Since 4.21.0, dedicated named configuration is provided for user to configure volume allocation algorithm:
78-
79-
**volume.allocation.algorithm**: random (default)
80+
Before 4.21.0, **vm.allocation.algorithm** was used for both VM as well as Volume allocation.

0 commit comments

Comments
 (0)