diskimage-builder/elements/cloud-init-nocloud/README.rst

==================
cloud-init-nocloud
==================
Configures cloud-init to only use on-disk metadata/userdata sources. This
will avoid a boot delay of 2 minutes while polling for cloud data sources
such as the EC2 metadata service.

Empty on-disk sources are created in /var/lib/cloud/seed/nocloud/.
Create docs site containing element READMEs We currently do not have the ability to create a docs site which outlines all the elements. Change-Id: I77ccf61e0c4b1509b3e7ce9b8f15ea5ccfd50d9b 2015-02-07 10:30:02 +00:00			`==================`
			`cloud-init-nocloud`
			`==================`
cloud-init-nocloud element for non-cloud image Disables cloud-init from querying EC2 metadata, or any cloud metadata service. It keeps only the Nocloud and None data sources, which are both expected to be "baked in" to an image. This speeds up boot by 2 minutes on hosts where cloud-init cannot reach the EC2 metadata service. Change-Id: I43522c4a442c0f2fc2044d4898768ceb4f839099 2013-02-05 05:54:48 +00:00			`Configures cloud-init to only use on-disk metadata/userdata sources. This`
			`will avoid a boot delay of 2 minutes while polling for cloud data sources`
			`such as the EC2 metadata service.`
Fix cloud-init-nocloud to actually work. Bug 1124593 reported that ssh host keys were not being created, and the lack of seed metadata files was the cause. Add those files and remove the workaround. Change-Id: I6fb55be7f8c7efd1f75aeba9123f495e312ff695 2013-06-12 01:28:27 +00:00
			`Empty on-disk sources are created in /var/lib/cloud/seed/nocloud/.`