<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/nova.git/nova/scheduler, branch master</title>
<subtitle>opendev.org: openstack/nova.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/'/>
<entry>
<title>add hypervisor version weigher</title>
<updated>2023-04-20T18:33:55+00:00</updated>
<author>
<name>Sean Mooney</name>
<email>work@seanmooney.info</email>
</author>
<published>2023-04-12T19:24:35+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=e38d6a356b8238038f11565662eaacff2ec2c2df'/>
<id>e38d6a356b8238038f11565662eaacff2ec2c2df</id>
<content type='text'>
implements: blueprint weigh-host-by-hypervisor-version
Change-Id: I36b16a388383c26bdf432030bc9e28b2fd75d120
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
implements: blueprint weigh-host-by-hypervisor-version
Change-Id: I36b16a388383c26bdf432030bc9e28b2fd75d120
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge "Make scheduler lazy-load the placement client"</title>
<updated>2023-04-10T21:10:46+00:00</updated>
<author>
<name>Zuul</name>
<email>zuul@review.opendev.org</email>
</author>
<published>2023-04-10T21:10:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=ae42400b7663bc58d5562de99e976c95131b77a9'/>
<id>ae42400b7663bc58d5562de99e976c95131b77a9</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>mypy: Fix implicit optional usage</title>
<updated>2023-03-27T14:43:58+00:00</updated>
<author>
<name>Eric Harney</name>
<email>eharney@redhat.com</email>
</author>
<published>2023-03-27T14:43:58+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=29de62bf3b3bf5eda8986bc94babf1c94d67bd4e'/>
<id>29de62bf3b3bf5eda8986bc94babf1c94d67bd4e</id>
<content type='text'>
Current versions of mypy run with no-implicit-optional
by default.  This change gets Nova's mypy test environment
to pass again.

Change-Id: Ie50c8d364ad9c339355cc138b560ec4df14fe307
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Current versions of mypy run with no-implicit-optional
by default.  This change gets Nova's mypy test environment
to pass again.

Change-Id: Ie50c8d364ad9c339355cc138b560ec4df14fe307
</pre>
</div>
</content>
</entry>
<entry>
<title>Make scheduler lazy-load the placement client</title>
<updated>2023-03-22T15:59:25+00:00</updated>
<author>
<name>Dan Smith</name>
<email>dansmith@redhat.com</email>
</author>
<published>2023-03-22T15:20:58+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=d37cca361a4d575311318cb870da40079eb1617c'/>
<id>d37cca361a4d575311318cb870da40079eb1617c</id>
<content type='text'>
Like we did for conductor, this makes the scheduler lazy-load the
placement client instead of only doing it during __init__. This avoids
a startup crash if keystone or placement are not available, but
retains startup failures for other problems and errors likely to be
a result of misconfigurations.

Closes-Bug: #2012530
Change-Id: I42ed876b84d80536e83d9ae01696b0a64299c9f7
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Like we did for conductor, this makes the scheduler lazy-load the
placement client instead of only doing it during __init__. This avoids
a startup crash if keystone or placement are not available, but
retains startup failures for other problems and errors likely to be
a result of misconfigurations.

Closes-Bug: #2012530
Change-Id: I42ed876b84d80536e83d9ae01696b0a64299c9f7
</pre>
</div>
</content>
</entry>
<entry>
<title>testing: Reset affinity support global variables</title>
<updated>2023-03-02T18:14:46+00:00</updated>
<author>
<name>melanie witt</name>
<email>melwittt@gmail.com</email>
</author>
<published>2023-03-01T23:57:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=d53372790435a003723a29cb15ac044b014a0e89'/>
<id>d53372790435a003723a29cb15ac044b014a0e89</id>
<content type='text'>
Ran into this randomly today, if a test sets
CONF.scheduler.enabled_filters to a non-default value, the affinity
support global variables will be set to False which can affect
subsequent test runs that expect the default configuration (affinity
filter support enabled).

Example error:

  WARNING [nova.scheduler.utils] Failed to
    compute_task_build_instances: ServerGroup policy is not supported:
      ServerGroupAffinityFilter not configured

This resets the global variables during base test setup, similar to how
other globals are reset.

Change-Id: Icbc75b1001c0a609280241f99a780313b244aa9d
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Ran into this randomly today, if a test sets
CONF.scheduler.enabled_filters to a non-default value, the affinity
support global variables will be set to False which can affect
subsequent test runs that expect the default configuration (affinity
filter support enabled).

Example error:

  WARNING [nova.scheduler.utils] Failed to
    compute_task_build_instances: ServerGroup policy is not supported:
      ServerGroupAffinityFilter not configured

This resets the global variables during base test setup, similar to how
other globals are reset.

Change-Id: Icbc75b1001c0a609280241f99a780313b244aa9d
</pre>
</div>
</content>
</entry>
<entry>
<title>Factor out a mixin class for candidate aware filters</title>
<updated>2023-01-20T16:17:48+00:00</updated>
<author>
<name>Balazs Gibizer</name>
<email>gibi@redhat.com</email>
</author>
<published>2023-01-05T18:32:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=87c0602537688c3da2291792a98caf9d9faf9d6c'/>
<id>87c0602537688c3da2291792a98caf9d9faf9d6c</id>
<content type='text'>
blueprint: pci-device-tracking-in-placement
Change-Id: Id044131162e582cef41e424aa751e3cd3618ed0c
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
blueprint: pci-device-tracking-in-placement
Change-Id: Id044131162e582cef41e424aa751e3cd3618ed0c
</pre>
</div>
</content>
</entry>
<entry>
<title>Filter PCI pools based on Placement allocation</title>
<updated>2022-10-17T11:56:18+00:00</updated>
<author>
<name>Balazs Gibizer</name>
<email>gibi@redhat.com</email>
</author>
<published>2022-08-19T10:24:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=f1d82c0d0a0ef5932bb1e25120015c1099f03d18'/>
<id>f1d82c0d0a0ef5932bb1e25120015c1099f03d18</id>
<content type='text'>
The stats module is used to decide if the InstancePCIRequests of a boot
request can fit to a given compute host and to decide which PCI device
pool can fulfill the requests. It is used both during scheduling and also
during the PCI claim code.

PCI devices now modelled in placement and the allocation_candidate query
now requests PCI resources therefore each allocation candidate returned
from placement already restricts which PCI devices can be used during
the PciPassthroughFilter, the NumaTopologyFilter, and PCI claim code
paths. This patch adapts the stats module to consider the PCI
allocation candidate or the already made placement PCI allocation when
filtering the PCI device pools.

blueprint: pci-device-tracking-in-placement
Change-Id: If363981c4aeeb09a96ee94b140070d3d0f6af48f
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The stats module is used to decide if the InstancePCIRequests of a boot
request can fit to a given compute host and to decide which PCI device
pool can fulfill the requests. It is used both during scheduling and also
during the PCI claim code.

PCI devices now modelled in placement and the allocation_candidate query
now requests PCI resources therefore each allocation candidate returned
from placement already restricts which PCI devices can be used during
the PciPassthroughFilter, the NumaTopologyFilter, and PCI claim code
paths. This patch adapts the stats module to consider the PCI
allocation candidate or the already made placement PCI allocation when
filtering the PCI device pools.

blueprint: pci-device-tracking-in-placement
Change-Id: If363981c4aeeb09a96ee94b140070d3d0f6af48f
</pre>
</div>
</content>
</entry>
<entry>
<title>Make allocation candidates available for scheduler filters</title>
<updated>2022-10-17T11:56:18+00:00</updated>
<author>
<name>Balazs Gibizer</name>
<email>gibi@redhat.com</email>
</author>
<published>2022-08-17T14:12:24+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=3d818c3473cdd94cac846309b555b771243f82b8'/>
<id>3d818c3473cdd94cac846309b555b771243f82b8</id>
<content type='text'>
This patch extends the HostState object with an allocation_candidates
list populated by the scheduler manager. Also this changes the generic
scheduler logic to allocate the candidate of the selected host based on
the candidates in the host state.

So after this patch scheduler filters can be extended to filter the
allocation_candidates list of the HostState object while processing a
host and restrict which candidate can be allocated if the host passes
the all the filters. Potentially all candidates can be removed by
multiple consecutive filters making the host as a non viable scheduling
target.

blueprint: pci-device-tracking-in-placement
Change-Id: Id0afff271d345a94aa83fc886e9c3231c3ff2570
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch extends the HostState object with an allocation_candidates
list populated by the scheduler manager. Also this changes the generic
scheduler logic to allocate the candidate of the selected host based on
the candidates in the host state.

So after this patch scheduler filters can be extended to filter the
allocation_candidates list of the HostState object while processing a
host and restrict which candidate can be allocated if the host passes
the all the filters. Potentially all candidates can be removed by
multiple consecutive filters making the host as a non viable scheduling
target.

blueprint: pci-device-tracking-in-placement
Change-Id: Id0afff271d345a94aa83fc886e9c3231c3ff2570
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge "Follow up for the PCI in placement series"</title>
<updated>2022-09-06T16:30:11+00:00</updated>
<author>
<name>Zuul</name>
<email>zuul@review.opendev.org</email>
</author>
<published>2022-09-06T16:30:11+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=36091a7ed7ad553d5cbb5dcfde0090e1e762bc34'/>
<id>36091a7ed7ad553d5cbb5dcfde0090e1e762bc34</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Follow up for the PCI in placement series</title>
<updated>2022-09-02T12:07:32+00:00</updated>
<author>
<name>Balazs Gibizer</name>
<email>gibi@redhat.com</email>
</author>
<published>2022-08-30T10:21:12+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=11bcf2676c326451772a7280b45180882d5dc9a7'/>
<id>11bcf2676c326451772a7280b45180882d5dc9a7</id>
<content type='text'>
Fixed various small issues from the already merged (or being merged)
patches.

The logic behind the dropped FIXME and empty condition are handled in
the update_allocations() calls of the translator already.

The removal of  excutils.save_and_reraise_exception from the report
client is safe as self._clear_provider_cache_for_tree does not raise.

blueprint: pci-device-tracking-in-placement
Change-Id: If87dedc6a14f7b116c4238e7534b67574428c01c
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fixed various small issues from the already merged (or being merged)
patches.

The logic behind the dropped FIXME and empty condition are handled in
the update_allocations() calls of the translator already.

The removal of  excutils.save_and_reraise_exception from the report
client is safe as self._clear_provider_cache_for_tree does not raise.

blueprint: pci-device-tracking-in-placement
Change-Id: If87dedc6a14f7b116c4238e7534b67574428c01c
</pre>
</div>
</content>
</entry>
</feed>
