Bug 1547255 - [RFE] Utilize placement to increase scheduler performance
Summary: [RFE] Utilize placement to increase scheduler performance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M2
: 14.0 (Rocky)
Assignee: Dan Smith
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-20 21:10 UTC by Dan Smith
Modified: 2023-09-14 04:20 UTC (History)
10 users (show)

Fixed In Version: openstack-nova-18.0.0-0.20180710150340.8469fa7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:48:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 546282 0 None MERGED Honor availability_zone hint via placement 2020-08-10 10:20:02 UTC
Red Hat Issue Tracker OSP-28669 0 None None None 2023-09-14 04:20:31 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:49:22 UTC

Description Dan Smith 2018-02-20 21:10:17 UTC
Description of problem:

Now that placement is deployed, populated, and capable of answering more complex queries, we should utilize it to reduce the workload on the nova scheduler. The scheduler must filter large numbers of hosts down to very few during boot or migration actions, and is often the choke point for these operations.

Specifically, the introduction of CellsV2 allows/requires deployments to have a single scheduler (or set of schedulers) for all of their compute hosts. Especially given the default limit of 1000 results from placement, the scheduler may not even be able to provide good answers to scheduling queries due to it asking overly vague questions of placement.

We need a way to augment our queries to placement in order to receive smaller and more relevant sets of hosts from it, against which we apply our filters.

Comment 11 errata-xmlrpc 2019-01-11 11:48:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045

Comment 12 Red Hat Bugzilla 2023-09-14 04:16:52 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.