Disable limit if affinity(anti)/same(different)host is requested
When max_placement_results is less than the total number of nodes in
a deployment it may not be possible to use the affinity, anti-affinity,
same host or different host filters as there is no guarantee
for placement to return the expected hosts under such situations. This
patch disables the max_placement_results parameter when nova queries
placement for ``GET /allocation_candidates`` if the
request_spec.scheduler_hints containts any of group, same_host or
different_host keys.
Reviewed: https:/ /review. opendev. org/658110 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=2f9e972ba33 58fc5bc9bdc06fa f47b21d509e20f
Committed: https:/
Submitter: Zuul
Branch: master
commit 2f9e972ba3358fc 5bc9bdc06faf47b 21d509e20f
Author: Surya Seetharaman <email address hidden>
Date: Thu May 9 16:22:13 2019 +0200
Disable limit if affinity( anti)/same( different) host is requested
When max_placement_ results is less than the total number of nodes in results parameter when nova queries candidates` ` if the spec.scheduler_ hints containts any of group, same_host or
a deployment it may not be possible to use the affinity, anti-affinity,
same host or different host filters as there is no guarantee
for placement to return the expected hosts under such situations. This
patch disables the max_placement_
placement for ``GET /allocation_
request_
different_host keys.
Change-Id: Ia2d5f80b6db59a 8f6da03344aeaa6 aa599407672
Closes-Bug: #1827628