3f76f9cfdb
The nova CDM builder code and notification handling code had some inefficiencies when it came to looking up a hypevisor to get details. The general pattern used before was: 1. get the minimal hypervisor information by hypervisor_hostname 2. make another query to get the hypervisor details by id In the notifications case, it was actually three calls because the first is listing hyprvisors to filter client-side by service host. This change collapses 1 and 2 above into a single API call to get the hypervisor by hypervisor_hostname with details which will include the service (compute) host information which is what get_compute_node_by_id() was being used for. Now that nothing is using get_compute_node_by_id it is removed. There is more work we could do in get_compute_node_by_hostname if the compute API allowed filtering hypervisors by service host so a TODO is left for that. One final thing: the TODO in get_compute_node_by_hostname about there being more than one hypervisor per compute service host for vmware vcenter is not accurate - nova's vcenter driver hasn't supported a host:node 1:M topology like that since the Liberty release [1]. The only in-tree driver in nova that supports 1:M is the ironic baremetal driver, so the comment is updated. [1] Ifc17c5049e3ed29c8dd130339207907b00433960 Depends-On: https://review.opendev.org/661785/ Change-Id: I5e0e88d7b2dd1a69117ab03e0e66851c687606da
53 lines
1.8 KiB
Plaintext
53 lines
1.8 KiB
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
apscheduler>=3.5.1 # MIT License
|
|
enum34>=1.1.6;python_version=='2.7' or python_version=='2.6' or python_version=='3.3' # BSD
|
|
jsonpatch>=1.21 # BSD
|
|
keystoneauth1>=3.4.0 # Apache-2.0
|
|
jsonschema>=2.6.0 # MIT
|
|
keystonemiddleware>=4.21.0 # Apache-2.0
|
|
lxml>=4.1.1 # BSD
|
|
croniter>=0.3.20 # MIT License
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.cache>=1.29.0 # Apache-2.0
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.context>=2.21.0 # Apache-2.0
|
|
oslo.db>=4.35.0 # Apache-2.0
|
|
oslo.i18n>=3.20.0 # Apache-2.0
|
|
oslo.log>=3.37.0 # Apache-2.0
|
|
oslo.messaging>=8.1.2 # Apache-2.0
|
|
oslo.policy>=1.34.0 # Apache-2.0
|
|
oslo.reports>=1.27.0 # Apache-2.0
|
|
oslo.serialization>=2.25.0 # Apache-2.0
|
|
oslo.service>=1.30.0 # Apache-2.0
|
|
oslo.upgradecheck>=0.1.0 # Apache-2.0
|
|
oslo.utils>=3.36.0 # Apache-2.0
|
|
oslo.versionedobjects>=1.32.0 # Apache-2.0
|
|
PasteDeploy>=1.5.2 # MIT
|
|
pbr>=3.1.1 # Apache-2.0
|
|
pecan>=1.3.2 # BSD
|
|
PrettyTable<0.8,>=0.7.2 # BSD
|
|
gnocchiclient>=7.0.1 # Apache-2.0
|
|
python-ceilometerclient>=2.9.0 # Apache-2.0
|
|
python-cinderclient>=3.5.0 # Apache-2.0
|
|
python-glanceclient>=2.9.1 # Apache-2.0
|
|
python-keystoneclient>=3.15.0 # Apache-2.0
|
|
python-monascaclient>=1.12.0 # Apache-2.0
|
|
python-neutronclient>=6.7.0 # Apache-2.0
|
|
python-novaclient>=14.1.0 # Apache-2.0
|
|
python-openstackclient>=3.14.0 # Apache-2.0
|
|
python-ironicclient>=2.3.0 # Apache-2.0
|
|
six>=1.11.0 # MIT
|
|
SQLAlchemy>=1.2.5 # MIT
|
|
stevedore>=1.28.0 # Apache-2.0
|
|
taskflow>=3.1.0 # Apache-2.0
|
|
WebOb>=1.8.5 # MIT
|
|
WSME>=0.9.2 # MIT
|
|
# NOTE(fdegir): NetworkX 2.3 dropped support for Python 2
|
|
networkx>=1.11,<2.3;python_version<'3.0' # BSD
|
|
networkx>=1.11;python_version>='3.4' # BSD
|
|
microversion_parse>=0.2.1 # Apache-2.0
|
|
futurist>=1.8.0 # Apache-2.0
|