-
-
Save evrardjp/9ee8038c67d1eee1452a3bba2529ec2c to your computer and use it in GitHub Desktop.
multi-region OSA POC
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
service_region: regionTwo | |
master_region_keystone_address: "10.53.3.2" | |
keystone_service_region: regionOne | |
keystone_service_adminuri: "{{ keystone_service_adminuri_proto }}://{{ master_region_keystone_address }}:{{ keystone_admin_port }}" | |
keystone_service_internaluri: "{{ keystone_service_internaluri_proto }}://{{ master_region_keystone_address }}:{{ keystone_service_port }}" | |
# Make sure your keystone_auth_admin_password in user_secrets for the second region matches the password from regionOne | |
# These settings avoid username collisions when using the same keystone | |
# deployment across multiple regions. | |
glance_service_user_name: "glance-{{ service_region }}" | |
cinder_service_user_name: "cinder-{{ service_region }}" | |
nova_service_user_name: "nova-{{ service_region }}" | |
nova_placement_service_username: "placement-{{ service_region }}" | |
neutron_service_user_name: "neutron-{{ service_region }}" | |
heat_service_user_name: "heat-{{ service_region }}" | |
# typically in the second region you would not define any identity_hosts or dashboard_hosts in your openstack_user_config.yml | |
# that means only regionOne has keystone and horizon, and the dashboard and identity service for all regions is accessed thru regionOne |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment