Skip to content

Commit 8806878

Browse files
committed
Remove outdated comment about allocation ratios
Setting allocation ratios via host aggregate metadata has not been possible since Ocata. Change-Id: Ia1a14a56739ec4c3f6930f1947a7423fd447fe34
1 parent ee9ed0f commit 8806878

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
@@ -1152,10 +1152,9 @@ scheduling.
11521152
Usage scenarios
11531153
~~~~~~~~~~~~~~~
11541154

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

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

0 commit comments

Comments
 (0)