f645287ec4
This moves cloud-init data source configuration to a general purpose cloud-init-datasources element that can be used to explicitly configure the list of cloud-init sources that will be queried on first boot. cloud-init-nocloud now depends on this new element to configure the datasource_list while continuing to prep the image for a nocloud first boot. Change-Id: Ibcc3b86d6ca567a23f89b7a1a36bc713e444ef68 Closes-bug: #1316475
22 lines
770 B
Markdown
22 lines
770 B
Markdown
Configures cloud-init to only use an explicit list of data sources.
|
|
|
|
Cloud-init contains a growing collection of data source modules and most
|
|
are enabled by default. This causes cloud-init to query each data source
|
|
on first boot. This can cause delays or even boot problems depending on your
|
|
environment.
|
|
|
|
You must define `DIB_CLOUD_INIT_DATASOURCES` as a comma-separated list of valid
|
|
data sources to limit the data sources that will be queried for metadata on
|
|
first boot.
|
|
|
|
For instance, to enable only the Ec2 datasource:
|
|
|
|
export `DIB_CLOUD_INIT_DATASOURCES`="Ec2"
|
|
|
|
Or to enable multiple:
|
|
|
|
export `DIB_CLOUD_INIT_DATASOURCES`="Ec2, ConfigDrive, OpenStack"
|
|
|
|
Including this element without setting `DIB_CLOUD_INIT_DATASOURCES` will cause
|
|
image builds to fail.
|