Skip to content

Commit 197d09d

Browse files
MoteHueMaxBed4d
authored andcommitted
Deploy OS capacity after overcloud service upgrade
We only started enabling this by default in Caracal, so this needs to get deployed as part of an Antelope->Caracal upgrade. Otherwise, the haproxy and grafana config gets put in place without the exporter being present.
1 parent a02c89e commit 197d09d

File tree

2 files changed

+16
-0
lines changed

2 files changed

+16
-0
lines changed

doc/source/operations/upgrading-openstack.rst

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -176,6 +176,21 @@ authentication will fail if this configuration is absent. See `upstream
176176
Keystone change <https://review.opendev.org/c/openstack/keystone/+/833876>`__
177177
for more details.
178178

179+
OS Capacity exporter and dashboard enabled by default
180+
-----------------------------------------------------
181+
182+
The OS Capacity exporter will automatically be deployed after the upgrade.
183+
During the upgrade, HAProxy config, Prometheus config and Grafana dashboards
184+
will also be updated to use the exporter. If you want to disable this, change
185+
the following in ``kayobe-config/etc/kayobe/stackhpc-monitoring.yml``:
186+
187+
.. code-block:: yaml
188+
189+
# Whether the OpenStack Capacity exporter is enabled.
190+
# Enabling this flag will result in HAProxy configuration and Prometheus scrape
191+
# targets being templated during deployment.
192+
stackhpc_enable_os_capacity: false
193+
179194
Known issues
180195
============
181196

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../../ansible/deploy-os-capacity-exporter.yml

0 commit comments

Comments
 (0)