summaryrefslogtreecommitdiff
path: root/releasenotes/notes/setting-retrieve-instance-ip-addresses-b9db6703d8b010c8.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes/notes/setting-retrieve-instance-ip-addresses-b9db6703d8b010c8.yaml')
-rw-r--r--releasenotes/notes/setting-retrieve-instance-ip-addresses-b9db6703d8b010c8.yaml10
1 files changed, 10 insertions, 0 deletions
diff --git a/releasenotes/notes/setting-retrieve-instance-ip-addresses-b9db6703d8b010c8.yaml b/releasenotes/notes/setting-retrieve-instance-ip-addresses-b9db6703d8b010c8.yaml
new file mode 100644
index 000000000..4a9e768ba
--- /dev/null
+++ b/releasenotes/notes/setting-retrieve-instance-ip-addresses-b9db6703d8b010c8.yaml
@@ -0,0 +1,10 @@
+---
+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`].