openstack/nova
Code Issues Proposed changes

Fix typos for update_available_resource reference

Browse Source 
Fixing a couple of typos that wrongly refers to
update_available_resources()
insted of update_available_resource()

Change-Id: Iaf7828e9cfb73ac87018d78180d16aae91d838f3
This commit is contained in:
Riccardo Pittau
2020-01-15 10:20:49 +01:00
parent 093e65c2ca
commit f0bc7874a8
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/contributor/testing/eventlet-profiling.rst
View File

@@ -266,7 +266,7 @@ The creation of this caveat section was inspired by issues experienced while
profiling ``nova-compute``. The ``nova-compute`` process is not allowed to
speak with a database server directly. Instead communication is mediated
through the conductor, communication happening via ``oslo.versionedobjects``
and remote calls. Profiling methods such as ``_update_available_resources`` in
and remote calls. Profiling methods such as ``update_available_resource`` in
the ResourceTracker, which needs information from the database, results in
profile data that can be analyzed but is incorrect and misleading.

2
nova/conf/compute.py
View File

@@ -1150,7 +1150,7 @@ Related options:
help="""
Interval for updating compute resources.
This option specifies how often the update_available_resources
This option specifies how often the update_available_resource
periodic task should run. A number less than 0 means to disable the
task completely. Leaving this at the default of 0 will cause this to
run at the default periodic interval. Setting it to any positive

2
nova/virt/ironic/driver.py
View File

@@ -586,7 +586,7 @@ class IronicDriver(virt_driver.ComputeDriver):
extra_specs. Since existing ironic instances will not have this in
their extra_specs, they will only have allocations against
VCPU/RAM/disk. By adding just the custom RC to the existing flavor
extra_specs, the periodic call to update_available_resources() will add
extra_specs, the periodic call to update_available_resource() will add
an allocation against the custom resource class, and prevent placement
from thinking that node is available. This code can be removed in
Queens, and will need to be updated to also alter extra_specs to