Skip to content

Commit 2350c17

Browse files
priteaus10
authored andcommitted
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 8806878) (cherry picked from commit b81439e) (cherry picked from commit 6984210)
1 parent 226f3e9 commit 2350c17

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

doc/source/admin/scheduling.rst

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1112,10 +1112,9 @@ scheduling.
11121112
Usage scenarios
11131113
~~~~~~~~~~~~~~~
11141114

1115-
Since allocation ratios can be set via nova configuration, host aggregate
1116-
metadata and the placement API, it can be confusing to know which should be
1117-
used. This really depends on your scenario. A few common scenarios are detailed
1118-
here.
1115+
Since allocation ratios can be set via nova configuration and the placement
1116+
API, it can be confusing to know which should be used. This really depends on
1117+
your scenario. A few common scenarios are detailed here.
11191118

11201119
1. When the deployer wants to **always** set an override value for a resource
11211120
on a compute node, the deployer should ensure that the

0 commit comments

Comments
 (0)