This is an automated email from the ASF dual-hosted git repository.
rohit pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/main by this push:
new 05e083d Add cluster ordering by host capacityType doc (#524)
05e083d is described below
commit 05e083d208e9c9e19d4a7b4d655888d4377dccf0
Author: Manoj Kumar <[email protected]>
AuthorDate: Tue Jul 15 16:41:14 2025 +0530
Add cluster ordering by host capacityType doc (#524)
---
source/adminguide/vm_volume_allocators.rst | 61 +++++++++++++++++++++++++++++-
1 file changed, 60 insertions(+), 1 deletion(-)
diff --git a/source/adminguide/vm_volume_allocators.rst
b/source/adminguide/vm_volume_allocators.rst
index 3844279..c15ebd8 100644
--- a/source/adminguide/vm_volume_allocators.rst
+++ b/source/adminguide/vm_volume_allocators.rst
@@ -77,4 +77,63 @@ firstfitleastconsumed Selects the first storage
pool after sorting elig
**volume.allocation.algorithm**: random (default)
- Before 4.21.0, **vm.allocation.algorithm** was used for both VM as well as
Volume allocation.
\ No newline at end of file
+ Before 4.21.0, **vm.allocation.algorithm** was used for both VM as well as
Volume allocation.
+
+
+Cluster, Pod and Host Ordering
+==============================
+
+Overview
+--------
+
+`The host.capacityType.to.order.clusters` is a global advanced configuration
parameter in Apache CloudStack that controls how pods, clusters,
+and hosts are prioritized during Instance deployment, based on available CPU,
RAM, or a weighted combination of both in Host.
+This configuration is specifically leveraged when the VM allocation algorithm
is set to `firstfitleastconsumed`.
+
+Configuration
+-------------
+
+Key: `host.capacityType.to.order.clusters`
+
+.. cssclass:: table-striped table-bordered table-hover
+
+========= ========================
+Value Behavior
+========= ========================
+CPU Prioritizes resources with the most available CPU.
+RAM Prioritizes resources with the most available memory.
+COMBINED Uses a weighted formula to balance CPU and RAM in
prioritization.
+========= ========================
+
+**Additional Configuration for COMBINED**
+
+- Key: `host.capacityType.to.order.clusters.cputomemoryweight`
+- Type: Float(0.0 to 1.0)
+- Default: 0.5
+- Purpose: Determines the weight of CPU vs RAM in the combined capacity
calculation.
+
+Capacity calculation formula:
+
+.. code:: bash
+
+ capacity = (host.capacityType.to.order.clusters.cputomemoryweight * CPU) +
((1 - host.capacityType.to.order.clusters.cputomemoryweight) * RAM)
+
+
+This allows flexible tuning of prioritization depending on workload
sensitivity.
+
+Example Configuration
+---------------------
+
+.. code:: bash
+
+ host.capacityType.to.order.clusters: COMBINED
+ host.capacityType.to.order.clusters.cputomemoryweight: 0.7
+
+Above config prioritizes CPU at 70% weight and RAM at 30% when ranking pods,
clusters, and hosts.
+
+.. note::
+ - `host.capacityType.to.order.clusters` is only respected for host ordering
when:
+ .. code:: bash
+
+ vm.allocation.algorithm: firstfitleastconsumed
+ - When using COMBINED, make sure to tune cpu.to.memory.capacity.weight to
reflect your environment’s resource constraints and workload profiles.
