commit f08d0ccf844e127f693cfc5498a205b13c873833
Author: Sean Mooney <email address hidden>
Date: Mon Oct 21 16:17:17 2019 +0000
Disable NUMATopologyFilter on rebuild
This change leverages the new NUMA constraint checking added in
in I0322d872bdff68936033a6f5a54e8296a6fb3434 to allow the
NUMATopologyFilter to be skipped on rebuild.
As the new behavior of rebuild enfroces that no changes
to the numa constraints are allowed on rebuild we no longer
need to execute the NUMATopologyFilter. Previously
the NUMATopologyFilter would process the rebuild request
as if it was a request to spawn a new instnace as the
numa_fit_instance_to_host function is not rebuild aware.
As such prior to this change a rebuild would only succeed
if a host had enough additional capacity for a second instance
on the same host meeting the requirement of the new image and
existing flavor. This behavior was incorrect on two counts as
a rebuild uses a noop claim. First the resouce usage cannot
change so it was incorrect to require the addtional capacity
to rebuild an instance. Secondly it was incorrect not to assert
the resouce usage remained the same.
I0322d872bdff68936033a6f5a54e8296a6fb3434 adressed guarding the
rebuild against altering the resouce usage and this change
allows in place rebuild.
This change found a latent bug that will be adressed in a follow
up change and updated the functional tests to note the incorrect
behavior.
Reviewed: https:/ /review. opendev. org/703117 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=f08d0ccf844 e127f693cfc5498 a205b13c873833
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit f08d0ccf844e127 f693cfc5498a205 b13c873833
Author: Sean Mooney <email address hidden>
Date: Mon Oct 21 16:17:17 2019 +0000
Disable NUMATopologyFilter on rebuild
This change leverages the new NUMA constraint checking added in 936033a6f5a54e8 296a6fb3434 to allow the yFilter to be skipped on rebuild.
in I0322d872bdff68
NUMATopolog
As the new behavior of rebuild enfroces that no changes fit_instance_ to_host function is not rebuild aware.
to the numa constraints are allowed on rebuild we no longer
need to execute the NUMATopologyFilter. Previously
the NUMATopologyFilter would process the rebuild request
as if it was a request to spawn a new instnace as the
numa_
As such prior to this change a rebuild would only succeed
if a host had enough additional capacity for a second instance
on the same host meeting the requirement of the new image and
existing flavor. This behavior was incorrect on two counts as
a rebuild uses a noop claim. First the resouce usage cannot
change so it was incorrect to require the addtional capacity
to rebuild an instance. Secondly it was incorrect not to assert
the resouce usage remained the same.
I0322d872bd ff68936033a6f5a 54e8296a6fb3434 adressed guarding the
rebuild against altering the resouce usage and this change
allows in place rebuild.
This change found a latent bug that will be adressed in a follow
up change and updated the functional tests to note the incorrect
behavior.
Conflicts:
nova/tests/ functional/ libvirt/ test_numa_ servers. py
NOTE( sean-k- mooney) : Trivial import conflicts
Change-Id: I48bccc4b9adcac 3c7a3e42769c11f deb8f6fd132 rebuild- of-numa- instances 4ab0b68fd635597 bf6959c0ca) fa06aa6cf5a483e 9285d7b91f) 14135b9390cb53d e726fc901d)
Closes-Bug: #1804502
Implements: blueprint inplace-
(cherry picked from commit 3f9411071d4c1a0
(cherry picked from commit 94c0362918169a1
(cherry picked from commit 4a691c33d136117