@@ -141,58 +141,41 @@ OpenStack Capacity
141
141
==================
142
142
143
143
OpenStack Capacity allows you to see how much space you have available
144
- in your cloud. StackHPC Kayobe Config includes a playbook for manual
145
- deployment, and it's necessary that some variables are set before
146
- running this playbook .
144
+ in your cloud. StackHPC Kayobe Config will deploy OpenStack Capacity
145
+ by default on a service deploy, this can be disabled by setting
146
+ `` stackhpc_enable_os_capacity `` to false .
147
147
148
- To successfully deploy OpenStack Capacity, you are required to specify
149
- the OpenStack application credentials in ``kayobe/secrets.yml `` as:
148
+ OpenStack Capacity is deployed automatically using a service deploy hook
149
+ with the generated kolla-ansible admin credentials, you can override these
150
+ by setting the authentication url, username, password, project name and
151
+ project domain name in ``stackhpc-monitoring.yml ``:
150
152
151
153
.. code-block :: yaml
152
154
153
- secrets_os_capacity_credential_id : <some_credential_id>
154
- secrets_os_capacity_credential_secret : <some_credential_secret>
155
+ stackhpc_os_capacity_auth_url : <keystone_auth_url>
156
+ stackhpc_os_capacity_username : <openstack_username>
157
+ stackhpc_os_capacity_password : <openstack_password_encrypted_with_vault>
158
+ stackhpc_os_capacity_project_name : <openstack_project_name>
159
+ stackhpc_os_capacity_domain_name : <openstack_project_domain_name>
160
+ stackhpc_os_capacity_openstack_region_name : <openstack_region_name>
155
161
156
- The Keystone authentication URL and OpenStack region can be changed
157
- from their defaults in ``stackhpc-monitoring.yml `` should you need to
158
- set a different OpenStack region for your cloud. The authentication
159
- URL is set to use ``kolla_internal_fqdn `` by default:
160
-
161
- .. code-block :: yaml
162
-
163
- stackhpc_os_capacity_auth_url : <some_authentication_url>
164
- stackhpc_os_capacity_openstack_region_name : <some_openstack_region>
165
-
166
- Additionally, you are required to enable a conditional flag to allow
167
- HAProxy and Prometheus configuration to be templated during deployment.
168
-
169
- .. code-block :: yaml
170
-
171
- stackhpc_enable_os_capacity : true
172
-
173
- If you are deploying in a cloud with internal TLS, you may be required
162
+ Additionally, you should ensure these credentials have the correct permissions
163
+ for the exporter. If you are deploying in a cloud with internal TLS, you may be required
174
164
to disable certificate verification for the OpenStack Capacity exporter
175
165
if your certificate is not signed by a trusted CA.
176
166
177
167
.. code-block :: yaml
178
168
179
169
stackhpc_os_capacity_openstack_verify : false
180
170
181
- After defining your credentials, you may deploy OpenStack Capacity
182
- using the ``ansible/ deploy-os-capacity-exporter.yml `` Ansible playbook
171
+ If you've modified your credentials, you will need to re- deploy OpenStack Capacity
172
+ using the ``deploy-os-capacity-exporter.yml `` Ansible playbook
183
173
via Kayobe.
184
174
185
175
.. code-block :: console
186
176
187
177
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/deploy-os-capacity-exporter.yml
188
178
189
- It is required that you re-configure the Prometheus, Grafana and HAProxy
190
- services following deployment, to do this run the following Kayobe command.
191
-
192
- .. code-block :: console
193
-
194
- kayobe overcloud service reconfigure -kt grafana,prometheus,loadbalancer
195
-
196
179
If you notice ``HaproxyServerDown `` or ``HaproxyBackendDown `` prometheus
197
180
alerts after deployment it's likely the os_exporter secrets have not been
198
181
set correctly, double check you have entered the correct authentication
0 commit comments