openstack
/
nova
Code Issues Proposed changes

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 88068781d4)
(cherry picked from commit b81439e2a2)
(cherry picked from commit 698421064b)
This commit is contained in:
Pierre Riteau 2023-11-06 21:15:11 +01:00 committed by Vlad Gusev
parent 226f3e95c1
commit 2350c179f9
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/admin/scheduling.rst
View File

@ -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