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
(cherry picked from commit 66f9c304db)

docker/services/octavia-api.yaml

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

puppet/services/glance-api.yaml

@@ -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]

puppet/services/octavia-api.yaml

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

releasenotes/notes/add-metadata-settings-to-octavia-and-glance-tls-internal-5d8e46650b174626.yaml

@@ -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.