openstack/puppet-zaqar
Code Issues Proposed changes

Ensure keystone resources are created during service startup

Browse Source 
This change ensures keystone resources like the mistral service user
are created before completing service setup, so that we can use
the service::end anchor to ensure Zaqar service is fully available.

Change-Id: I5989b330cd55328510cc1bb20b6c00eeac18353b
This commit is contained in:
Takashi Kajinami 2022-02-07 00:25:15 +09:00
parent bfd3346540
commit f92eb34785
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
manifests/keystone/auth.pp
View File

@ -100,6 +100,8 @@ class zaqar::keystone::auth(
validate_legacy(String, 'validate_string', $password)
Keystone::Resource::Service_identity['zaqar'] -> Anchor['zaqar::service::end']
keystone::resource::service_identity { 'zaqar':
configure_user => $configure_user,
configure_user_role => $configure_user_role,

2
manifests/keystone/auth_websocket.pp
View File

@ -97,6 +97,8 @@ class zaqar::keystone::auth_websocket(
}
}
Keystone::Resource::Service_identity['zaqar-websocket'] -> Anchor['zaqar::service::end']
keystone::resource::service_identity { 'zaqar-websocket':
configure_user => false,
configure_user_role => false,