
Due to poor planning on our variable names we have a situation where we have "internal_address" which must be a VIP, but "external_address" which should be a DNS name. Now with two vips "external_vip_address" is a new variable. This corrects that issue by deprecating kolla_internal_address and replacing it with 4 nicely named variables. kolla_internal_vip_address kolla_internal_fqdn kolla_external_vip_address kolla_external_fqdn The default behaviour will remain the same, and the way the variable inheritance is setup the kolla_internal_address variable can still be set in globals.yml and propogate out to these 4 new variables like it normally would, but all reference to kolla_internal_address has been completely removed. Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5 Partially-Implements: blueprint ssl-kolla
12 lines
475 B
Django/Jinja
12 lines
475 B
Django/Jinja
[discoverd]
|
|
database = inspector.sqlite3
|
|
os_auth_url = {{ internal_protocol }}://{{ kolla_internal_fqdn }}:{{ keystone_public_port }}/v2.0
|
|
os_username = {{ openstack_auth.username }}
|
|
os_password = {{ openstack_auth.password }}
|
|
os_tenant_name = {{ openstack_auth.project_name }}
|
|
identity_uri = {{ openstack_auth.auth_url }}
|
|
|
|
# Note: this will be in the firewall section once upgraded to inspector
|
|
# unsure of the correct interface here
|
|
dnsmasq_interface = {{ api_interface }}
|