commit d65c18a0a9f02e6d37f2b87ff61f1740c8bfc867
Author: Matt Riedemann <email address hidden>
Date: Wed Nov 28 17:07:11 2018 -0500
Note the aggregate allocation ratio restriction in scheduler docs
This borrows from the release note in change
I01f20f275bbd5451ace5c1e6f41ab38d488dae4e to document the
regression, introduced in Ocata, where allocation ratio settings
in the aggregate core/ram/disk filters are not honored because
of placement being used by the FilterScheduler.
While there is related work going on around this in
blueprint initial-allocation-ratios and
blueprint placement-aggregate-allocation-ratios, it is still
a limitation in the current code base and needs to be called
out in the docs.
Reviewed: https:/ /review. openstack. org/620713 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=d65c18a0a9f 02e6d37f2b87ff6 1f1740c8bfc867
Committed: https:/
Submitter: Zuul
Branch: master
commit d65c18a0a9f02e6 d37f2b87ff61f17 40c8bfc867
Author: Matt Riedemann <email address hidden>
Date: Wed Nov 28 17:07:11 2018 -0500
Note the aggregate allocation ratio restriction in scheduler docs
This borrows from the release note in change bd5451ace5c1e6f 41ab38d488dae4e to document the
I01f20f275b
regression, introduced in Ocata, where allocation ratio settings
in the aggregate core/ram/disk filters are not honored because
of placement being used by the FilterScheduler.
While there is related work going on around this in allocation- ratios and aggregate- allocation- ratios, it is still
blueprint initial-
blueprint placement-
a limitation in the current code base and needs to be called
out in the docs.
Change-Id: Ifaf596a8572637 f843f47daf5adce 394b0365676
Related-Bug: #1804125