Go to file
Balazs Gibizer f20e13f0b2 Add round-robin candidate generation strategy
The previous patch introduced [placement]max_allocation_candidates
config option to limit the number of candidates generated for a single
query.

If the number of generated allocation candidates are limited by that
config option then it is possible to get candidates from a limited set of
root providers (computes, anchoring providers) as placement uses a
depth-first strategy, generating all candidates from the first root
before considering the next one.

To avoid unbalanced results this patch introduces a new config option
[placement]allocation_candidates_generation_strategy with the possible
values:
* depth-first, the original strategy that generates all candidate from
  the first root before moving to the next. This is will be the default
  strategy for backward compatibility
* breadth-first, a new possible strategy that generates candidates from
  available roots in a round-robin fashion, one candidate from each
  root before taking the second candidate from the first root.

Closes-Bug: #2070257
Change-Id: Ib7a140374bc91cc9ab597d0923b0623f618ec32c
2025-01-09 09:29:07 +01:00
2022-09-19 13:42:15 +00:00
2024-10-15 10:40:27 +09:00
2019-09-24 15:45:11 +00:00
2019-04-19 19:41:22 +00:00
2022-07-08 21:46:57 +05:30
2023-03-30 05:36:29 +00:00
2010-05-27 23:05:26 -07:00
2023-03-30 05:36:29 +00:00
2024-11-21 18:48:30 +00:00
2020-04-07 17:30:34 +00:00
2024-05-01 01:27:18 +09:00
2024-10-01 21:59:42 +00:00

If you are viewing this README on GitHub, please be aware that placement development happens on OpenStack git and OpenStack gerrit.

OpenStack Placement

image

OpenStack Placement provides an HTTP service for managing, selecting, and claiming providers of classes of inventory representing available resources in a cloud.

API

To learn how to use Placement's API, consult the documentation available online at:

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

To learn how to deploy and configure OpenStack Placement, consult the documentation available online at:

In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:

Developers

For information on how to contribute to Placement, please see the contents of CONTRIBUTING.rst.

Further developer focused documentation is available at:

Description
OpenStack resource provider inventory allocation service
Readme 22 MiB
Languages
Python 94.5%
PHP 4.2%
Shell 1.2%