Steve Lewis 3d1b45ea4c Configure DB addresses for each service

To enable partitioning of DB traffic by-service, each service needs to
use a custom connection string. Defaulting the service address to a
common galera_address makes things continue to work by default.

While the galera_address could be overridden on a container or host
basis this requires repeating that behavior across each infra node in
the inventory. Providing service-specific connection address variables
simplifies the management somewhat for large deployments and may reduce
error rates.

The service install playbooks now default the service-specific variables
instead of galera_address to the internal lb vip from inventory to
maintain the ease-of-use currently available.

Any value for a service-specific variable set in user_variables.yml will
override the value in the playbook's vars to provide selective
customization as needed.

Change-Id: I4c98bf906a0c1cb11ddd41277a855dce22ff646a
Closes-Bug: 1462529

2015-06-10 02:07:38 +00:00

587 B

Raw Blame History

OpenStack keystone

tags: openstack, keystone, cloud, ansible
category: *nix

Role to install keystone. This will install keystone using apache.

This role will install the following:

keystone
apache2

- name: Installation and setup of Keystone
  hosts: keystone_all
  user: root
  roles:
    - { role: "os_keystone", tags: [ "os-keystone" ] }
  vars:
    external_lb_vip_address: 172.16.24.1
    internal_lb_vip_address: 192.168.0.1
    keystone_galera_address: "{{ internal_lb_vip_address }}"

587 B Raw Blame History

OpenStack keystone

587 B

Raw Blame History