womax/nova
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Block servers with vGPU and device profile in heal_allocations

Browse Source 
Nested allocations are only partially supported in nova-manage placement
heal_allocations CLI. This patch documents the missing support and
blocks healing instances with VGPU or Cyborg device profile request in
the embedded flavor. Blocking is needed as if --forced is used with such
instances then the tool could recreate an allocation ignoring some of
these resources.

Change-Id: I89ac90d2ea8bc268940869dbbc90352bfad5c0de
Related-Bug: bug/1939020
This commit is contained in:
Balazs Gibizer
2021-08-05 15:20:02 +02:00
parent 2ffd973860
commit 59c2262ca5
6 changed files with 110 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/source/cli/nova-manage.rst
+9
View File
@@ -1144,6 +1144,15 @@ state transition. For each instance found, allocations are created against
the compute node resource provider for that instance based on the flavor
associated with the instance.
.. note::
Nested allocations are only partially supported. Nested allocations due to
Neutron ports having QoS policies are supported since 20.0.0 (Train)
release. But nested allocations due to vGPU or Cyborg device profile
requests in the flavor are not supported. Also if you are using
provider.yaml files on compute hosts to define additional resources, if
those resources are defined on child resource providers then instances
using such resources are not supported.
Also if the instance has any port attached that has resource request
(e.g. :neutron-doc:`Quality of Service (QoS): Guaranteed Bandwidth
<admin/config-qos-min-bw.html>`) but the corresponding