Force nova config drive to True in puppet data
Currently if you follow the advanced discovery/introspection flow you find that the dicovery data is not injected into the deployed nodes via the config-drive as expected. This change configures the undercloud nova to always include the configdrive data such that it's available for deploy-time scripts to consume, e.g to create the mappings for os-net-config or configure filesystems based on knowledge of disk performance/type. Bug ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1233199 Change-Id: I8dac26dab4eeccb3e8c878d51ce9d3944b4f7675
This commit is contained in:
parent
bf68406a20
commit
a96156a6b3
@ -150,6 +150,7 @@ nova::network::neutron::neutron_admin_password: {{UNDERCLOUD_NEUTRON_PASSWORD}}
|
||||
nova::notify_on_state_change: 'vm_and_task_state'
|
||||
nova::scheduler::enabled: true
|
||||
nova::network::neutron::dhcp_domain: ''
|
||||
nova::compute::force_config_drive: true
|
||||
|
||||
# Ironic
|
||||
ironic::api::admin_password: {{UNDERCLOUD_IRONIC_PASSWORD}}
|
||||
|
Loading…
Reference in New Issue
Block a user