openstack/bifrost
Code Issues Proposed changes
d10abd26f1
bifrost/playbooks/roles/bifrost-keystone-client-config
History
Pavlo Shchelokovskyy e09bec2c83 Allow to create cloud.yaml with many clouds 
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
2017-02-01 21:55:54 +02:00
..
defaults Add ability to write clouds.yaml 2016-11-22 14:24:08 +00:00
meta Add ability to write clouds.yaml 2016-11-22 14:24:08 +00:00
tasks Allow to create cloud.yaml with many clouds 2017-02-01 21:55:54 +02:00
templates Allow to create cloud.yaml with many clouds 2017-02-01 21:55:54 +02:00
README.md Allow to create cloud.yaml with many clouds 2017-02-01 21:55:54 +02:00

README.md

bifrost-keystone-client-config

This is a simple role intended for writing out a clouds.yaml file for Bifrost with the cloud name "bifrost".

Requirements

None

Role Variables

This role expects to be invoked with two variables:

  • user: Username of the user who will own the configuration file.
  • clouds: a dictionary with keys being names of the clouds to create in clouds.yaml, and values are dictionaries of authentication parameters for each cloud:
    • config_username
    • config_password
    • config_project_name
    • config_region_name
    • config_auth_url
    • config_project_domain_id (optional, defaults to 'default')
    • config_user_domain_id (optional, defaults to 'default')

Alternatively, for backward compatibility, the role can accept the above config_* variables directly, but this is deprecated. In this case, a single cloud named 'bifrost' will be written.

The resulting clouds.yaml file will be created at ~{{user}}/.config/openstack/clouds.yaml. If several sets of cloud settings are written, they will be sorted by cloud name, in case-insensitive order.

Notes

None

Dependencies

None at this time.

Example Playbook

  • hosts: localhost connection: local name: "Create clouds.yaml file"" become: no gather_facts: no roles:
    • role: bifrost-keystone-client-config user: joe clouds: local-cloud-user: config_username: username config_password: password config_project_name: baremetal config_region_name: RegionOne config_auth_url: http://localhost:5000 local-cloud-admin: config_username: admin config_password: verysecretpassword config_project_name: admin config_region_name: RegionOne config_auth_url: http://localhost:5000

License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Author Information

Ironic Developers