@@ -145,38 +145,34 @@ in your cloud. StackHPC Kayobe Config includes a playbook for manual
145
145
deployment, and it's necessary that some variables are set before
146
146
running this playbook.
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 ``kayobe/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>
155
160
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.
161
+ Additionally, you should ensure these credentials have the correct permissions
162
+ for the exporter. If you are deploying in a cloud with internal TLS, you may be required
163
+ to disable certificate verification for the OpenStack Capacity exporter
164
+ if your certificate is not signed by a trusted CA.
168
165
169
166
.. code-block :: yaml
170
167
171
- stackhpc_enable_os_capacity : true
168
+ stackhpc_os_capacity_openstack_verify : false
172
169
173
- If you are deploying in a cloud with internal TLS, you may be required
174
- to disable certificate verification for the OpenStack Capacity exporter
175
- if your certificate is not signed by a trusted CA.
170
+ The OpenStack region can be changed from it's default in ``stackhpc-monitoring.yml ``
171
+ should you need to set a different OpenStack region for your cloud:
176
172
177
173
.. code-block :: yaml
178
174
179
- stackhpc_os_capacity_openstack_verify : false
175
+ stackhpc_os_capacity_openstack_region_name : <some_openstack_region>
180
176
181
177
After defining your credentials, you may deploy OpenStack Capacity
182
178
using the ``ansible/deploy-os-capacity-exporter.yml `` Ansible playbook
0 commit comments