From 2350c179f9db133f9d7c0b2c12e495195ff1b32a Mon Sep 17 00:00:00 2001 From: Pierre Riteau Date: Mon, 6 Nov 2023 21:15:11 +0100 Subject: [PATCH] Remove outdated comment about allocation ratios Setting allocation ratios via host aggregate metadata has not been possible since Ocata. Change-Id: Ia1a14a56739ec4c3f6930f1947a7423fd447fe34 (cherry picked from commit 88068781d494b263a875b44bcbb6dcd5a98671f3) (cherry picked from commit b81439e2a2e9d965c3447ebd243043afb6c031a3) (cherry picked from commit 698421064b4604087634f8ea219795dad0b4928c) --- doc/source/admin/scheduling.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/source/admin/scheduling.rst b/doc/source/admin/scheduling.rst index e0e5b7188b33..5296cd95f585 100644 --- a/doc/source/admin/scheduling.rst +++ b/doc/source/admin/scheduling.rst @@ -1112,10 +1112,9 @@ scheduling. Usage scenarios ~~~~~~~~~~~~~~~ -Since allocation ratios can be set via nova configuration, host aggregate -metadata and the placement API, it can be confusing to know which should be -used. This really depends on your scenario. A few common scenarios are detailed -here. +Since allocation ratios can be set via nova configuration and the placement +API, it can be confusing to know which should be used. This really depends on +your scenario. A few common scenarios are detailed here. 1. When the deployer wants to **always** set an override value for a resource on a compute node, the deployer should ensure that the