Add metadata_settings to Octavia and Glance APIs

Internal TLS works fine if one deploys the API services in the
controller. Once one moves the service away from the controller, the
appropriate service principals won't be created.

Closes-Bug: #1795923
Change-Id: I6e8555fbc90fa0369aae37a7ad19eafc7b4a198a
This commit is contained in:
Carlos Goncalves 2018-10-03 17:39:18 +02:00 committed by Juan Antonio Osorio Robles
parent cac9d17663
commit 66f9c304db
4 changed files with 12 additions and 0 deletions

View File

@ -242,3 +242,5 @@ outputs:
- octavia_api_httpd_enabled|bool
- httpd_running|bool
service: name=httpd state=stopped
metadata_settings:
get_attr: [OctaviaApiPuppetBase, role_data, metadata_settings]

View File

@ -413,3 +413,5 @@ outputs:
- step|int == 1
- glance_registry_enabled.rc == 0
service: name=openstack-glance-registry state=stopped enabled=no
metadata_settings:
get_attr: [TLSProxyBase, role_data, metadata_settings]

View File

@ -175,3 +175,5 @@ outputs:
octavia::db::mysql::allowed_hosts:
- '%'
- "%{hiera('mysql_bind_host')}"
metadata_settings:
get_attr: [TLSProxyBase, role_data, metadata_settings]

View File

@ -0,0 +1,6 @@
---
fixes:
- |
Fixed an issue where if Octavia API or Glance API were deployed away from
the controller node with internal TLS, the service principals wouldn't be
created.