e09bec2c83
This patch makes the bifrost-keystone-client-config role a bit more generic to allow creating more that a single cloud configuration setting. The role is changed to accept a dict with possibly many clouds configurations, and the template for clouds.yaml is changed accordingly. This new functionality is used right away to add the keystone admin user to the created clouds.yaml file to make the installed keystone usable for admin-level operations (listing and editig users, projects, roles and role assignments) - the name of the 'cloud' created is 'bifrost-admin'. Change-Id: Icb274de989966645cd0f3874f8dff9d9f37d871b
22 lines
974 B
YAML
22 lines
974 B
YAML
---
|
|
features:
|
|
- |
|
|
'bifrost-keystone-client-config' role can now write 'clouds.yaml' file
|
|
with several clouds settings. It starts to accept a single compound
|
|
variable 'clouds' that should contain a dict of
|
|
'<cloud-name>:<dict-of-cloud-settings>'.
|
|
Previous way of passing 'config_*' vars to the role is supported for
|
|
backward compatibility but is deprecated.
|
|
|
|
In addition to previous 'bifrost' cloud, the default 'install.yaml'
|
|
playbook now also writes 'bifrost-admin' cloud settings that contain
|
|
Keystone admin credentials so that when installed, the Keystone service
|
|
is fully usable right away (users/projects etc can be managed).
|
|
|
|
deprecations:
|
|
- |
|
|
Passing 'config_*' variables defining credentials for 'bifrost'
|
|
cloud to 'bifrost-keystone-client-config' role is deprecated.
|
|
Instead a single compound variable named 'clouds' defining sets of
|
|
settings to be written to 'clouds.yaml' should be passed to that role.
|