Configure cinder to use service user tokens
Long-running operations such as snapshot can sometimes overrun the
expiry of the user token. In such cases, post operations such as
cleaning up after a snapshot can fail when the cinder service needs
to cleanup resources.
This patch enables cinder to use service user tokens to supplement
the regular user token used to initiate the operation.
The identity service (keystone) will then authenticate a request
using the service user token if the user token has already expired.
Change-Id: I3c794ae27b543e1a5df60696bb4a351e9d11a387
Related-Prod: PROD-25985
diff --git a/tests/pillar/control_single.sls b/tests/pillar/control_single.sls
index cd1f7d9..9f6d66d 100644
--- a/tests/pillar/control_single.sls
+++ b/tests/pillar/control_single.sls
@@ -21,6 +21,14 @@
user: cinder
password: password
endpoint_type: internalURL
+ service_user:
+ enabled: True
+ auth_type: password
+ user_domain_id: default
+ project_domain_id: default
+ project_name: service
+ username: cinder
+ password: password
glance:
host: 127.0.0.1
port: 9292