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
This commit is contained in:
parent
35ea92178d
commit
3778e6121b
@ -121,7 +121,7 @@ outputs:
|
||||
nova::metadata::novajoin::auth::tenant: 'service'
|
||||
nova::metadata::novajoin::auth::password: {get_param: NovajoinPassword}
|
||||
nova::metadata::novajoin::auth::region: {get_param: KeystoneRegion}
|
||||
nova_metadata:
|
||||
nova_metadata: &nova_vendordata
|
||||
novajoin_address:
|
||||
str_replace:
|
||||
template:
|
||||
@ -152,6 +152,9 @@ outputs:
|
||||
nova::vendordata::vendordata_dynamic_read_timeout: {get_param: NovajoinVendordataTimeout}
|
||||
nova::notification_topics: ['notifications', 'novajoin_notifications']
|
||||
nova::notify_on_state_change: 'vm_state'
|
||||
nova_api: *nova_vendordata
|
||||
nova_compute: *nova_vendordata
|
||||
nova_ironic: *nova_vendordata
|
||||
# BEGIN DOCKER SETTINGS
|
||||
puppet_config:
|
||||
config_volume: novajoin
|
||||
|
Loading…
x
Reference in New Issue
Block a user