Browse Source

Configure nova_compute for vendordata

The next change in this series turns off the nova_metadata service,
which means nova_compute needs to have the same vendordata
configuration so that it can populate the config-drive data with the
same vendordata served by nova_metadata.

Change-Id: I2dc1d120d0bd7cc91bde767097945598148d3e9b
Blueprint: nova-less-deploy
(cherry picked from commit 3778e6121b)
Closes-Bug: #1840980
tags/9.4.1
Steve Baker 4 months ago
parent
commit
b6c73b7530
1 changed files with 4 additions and 1 deletions
  1. 4
    1
      docker/services/novajoin.yaml

+ 4
- 1
docker/services/novajoin.yaml View File

@@ -123,7 +123,7 @@ outputs:
123 123
           nova::metadata::novajoin::auth::tenant: 'service'
124 124
           nova::metadata::novajoin::auth::password: {get_param: NovajoinPassword}
125 125
           nova::metadata::novajoin::auth::region: {get_param: KeystoneRegion}
126
-        nova_metadata:
126
+        nova_metadata: &nova_vendordata
127 127
           novajoin_address:
128 128
             str_replace:
129 129
                template:
@@ -154,6 +154,9 @@ outputs:
154 154
           nova::vendordata::vendordata_dynamic_read_timeout: {get_param: NovajoinVendordataTimeout}
155 155
           nova::notification_topics: ['notifications', 'novajoin_notifications']
156 156
           nova::notify_on_state_change: 'vm_state'
157
+        nova_api: *nova_vendordata
158
+        nova_compute: *nova_vendordata
159
+        nova_ironic: *nova_vendordata
157 160
       # BEGIN DOCKER SETTINGS
158 161
       puppet_config:
159 162
         config_volume: novajoin

Loading…
Cancel
Save