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/10.6.1
Steve Baker 4 months ago
parent
commit
b72c5e4bc5
1 changed files with 4 additions and 1 deletions
  1. 4
    1
      deployment/nova/novajoin-container-puppet.yaml

+ 4
- 1
deployment/nova/novajoin-container-puppet.yaml View File

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

Loading…
Cancel
Save