a42f58de50
Now instance panel is sending API calls to Neutron to get the addresses info about network. It take some time until Nova network info cache is synced when IP address operation like floating IP association is made in Neutron. The API calls to Neutron exist from this reason. However, it retrieves a full list of port, so it can potentially leads to performance issues in large deployments. This commit adds a setting flag to control whether API calls to Neutron is used or skipped in the project instance table. This commits drops a call of servers_update_addresses() in the admin instance table. In the admin instance table there is no need to retrieve IP addresses from neutron because the main purpose of the admin panel is to see all instances and IP addresses in nova network info cache will be synced soon. Closes-Bug: #1722417 Co-Authored-By: Akihiro Motoki <amotoki@gmail.com> Change-Id: Ie16784eb6352f70ab644dc8b6ea03fc6a881d3f9
11 lines
496 B
YAML
11 lines
496 B
YAML
---
|
|
fixes:
|
|
- |
|
|
A new setting ``OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES`` was introduced
|
|
to control whether IP addresses of servers are retrieved from neutron in
|
|
the project instance table. This setting was introduces to mitigate a
|
|
performance issue in large deployments and setting this to ``False``
|
|
skips the query to neutron. Deployments without floating IP support can
|
|
set this setting to ``False`` for better performance.
|
|
For more detail, see [:bug:`1722417`].
|