openstack
/
diskimage-builder
Code Issues Proposed changes
diskimage-builder/elements/cloud-init-datasources
History
Nikhil Manchanda d550087214 Do not use DatasourceNone for precise cloud-init 
The 'None' Datasource does not exist in precise 12.04 (which uses
cloud-init 0.6.3), so conditionally ensure that we are not including
this in the datasource_list in case we're building a precise image.

Partial-bug: 1329068
Change-Id: I6efb91e17bf896bbf7d67c31c4eb5098d5d61a71
 		2014-06-16 10:58:39 -07:00
..
install.d Do not use DatasourceNone for precise cloud-init 2014-06-16 10:58:39 -07:00
README.md Add new cloud-init-datasources element 2014-05-29 21:54:59 -07:00

README.md

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.