-
Notifications
You must be signed in to change notification settings - Fork 117
Documentation related to VM and Volume allocators #499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,79 @@ | ||
.. Licensed to the Apache Software Foundation (ASF) under one | ||
or more contributor license agreements. See the NOTICE file | ||
distributed with this work for additional information# | ||
regarding copyright ownership. The ASF licenses this file | ||
to you under the Apache License, Version 2.0 (the | ||
"License"); you may not use this file except in compliance | ||
with the License. You may obtain a copy of the License at | ||
http://www.apache.org/licenses/LICENSE-2.0 | ||
Unless required by applicable law or agreed to in writing, | ||
software distributed under the License is distributed on an | ||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | ||
KIND, either express or implied. See the License for the | ||
specific language governing permissions and limitations | ||
under the License. | ||
|
||
|
||
VM and Volume Allocators | ||
====================== | ||
|
||
Each Instance must be deployed in suitable deployment destination. Deployment destination is set of recommended resources that you can choose for deploying an instance. | ||
A deployment planner provides the suitable deployment destination that is required for a instance. | ||
|
||
Allocators are used to figure out suitable host and storage pools for deploying the Instance: | ||
|
||
#. VM Allocator | ||
#. Volume Allocator | ||
|
||
|
||
VM Allocator | ||
------------ | ||
|
||
VM allocator returns suitable hosts in the cluster where you can deploy the given instance. Various parameters e.g. CPU and | ||
RAM capacity, current state of the host are considered to decide the host. | ||
|
||
VM allocator supports following algorithms to select a host in the cluster: | ||
|
||
.. cssclass:: table-striped table-bordered table-hover | ||
|
||
============================= ======================== | ||
Algorithm Description | ||
============================= ======================== | ||
random Selects a host in the cluster randomly. | ||
firstfit Selects the first available host in the cluster. | ||
userdispersing Selects the host running least instances for the account, aims to spread out the instances belonging to a single user account. | ||
userconcentratedpod_random Selects the host randomly aiming to keep all instances belonging to single user account in same pod. | ||
userconcentratedpod_firstfit Selects the first suitable host from a pod running most instances for the user. | ||
firstfitleastconsumed Selects the first host after sorting eligible hosts by least allocated resources (such as CPU or RAM). | ||
============================= ======================== | ||
|
||
Use global configuration parameter: | ||
**vm.allocation.algorithm** to specify the algorithm that the Allocator must use. By default it is configured to use "random" algorithm. | ||
|
||
|
||
Volme Allocator | ||
-------------- | ||
|
||
VOlume allocator returns suitable storage pools available in the cluster where volumes of the given instance can be created. | ||
To decide the storage pools, it considers factors such as disk offering, storage capactiy, availability scope etc. | ||
|
||
Volume allocator supports following algorithms to select a host in the cluster: | ||
|
||
.. cssclass:: table-striped table-bordered table-hover | ||
|
||
============================= ======================== | ||
Algorithm Description | ||
============================= ======================== | ||
random Selects a storage pool in the cluster randomly. | ||
firstfit Selects the first available storage pool in the cluster. | ||
userdispersing Selects the storage pool running least instances for the account, aims to spread out the instances belonging to a single user account. | ||
userconcentratedpod_random Selects the storage pool randomly aiming to keep all instances belonging to single user account in same pod. | ||
userconcentratedpod_firstfit Selects the first suitable pool from a pod running most instances for the user. | ||
firstfitleastconsumed Selects the first storage pool after sorting eligible pools by least allocated resources. | ||
============================= ======================== | ||
|
||
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. | ||
sudo87 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
Since 4.21.0, dedicated named configuration is provided for user to configure volume allocation algorithm: | ||
|
||
**volume.allocation.algorithm**: random (default) |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.