Decouple ceilometer user create from API
Ceilometer user is needed for other ceilometer services to authenticate with keystone even when API is not present. So the data can be dispatched to gnocchi. Lets keep these separate so user always exists even when api is not. Depends-On: Iffebd40752eafb1d30b5962da8b5624fb9df7d48 Closes-bug: #1677354 Change-Id: I8f4e543a7cef5e50a35a191fe20e276d518daf20
This commit is contained in:
parent
f36a4ac6bb
commit
38e4976b7b
@ -246,7 +246,10 @@ class tripleo::profile::base::keystone (
|
||||
if hiera('barbican_api_enabled', false) {
|
||||
include ::barbican::keystone::auth
|
||||
}
|
||||
if hiera('ceilometer_api_enabled', false) {
|
||||
# ceilometer user is needed even when ceilometer api
|
||||
# not running, so it can authenticate with keystone
|
||||
# and dispatch data.
|
||||
if hiera('ceilometer_auth_enabled', false) {
|
||||
include ::ceilometer::keystone::auth
|
||||
}
|
||||
if hiera('ceph_rgw_enabled', false) {
|
||||
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- We need ceilometer user in cases where ceilometer API is disabled.
|
||||
This is to ensure other ceilometer services can still authenticate
|
||||
with keystone.
|
Loading…
x
Reference in New Issue
Block a user