diskimage-builder/diskimage_builder/elements/cloud-init-nocloud/install.d/05-inject-local-source-data

#!/bin/bash

if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then
    set -x
fi
set -eu
set -o pipefail

# without these files, cloud-init will not perform stock operations such as
# generating sshd hostkeys.

mkdir -p /var/lib/cloud/seed/nocloud
touch /var/lib/cloud/seed/nocloud/user-data
touch /var/lib/cloud/seed/nocloud/meta-data
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			`#!/bin/bash`

Standarise tracing for scripts There is a wide variety of tracing options through the various shell scripts. Some use "set -eux", others explicity set xtrace and others do nothing. There is a "-x" option to bin/disk-image-create but it doesn't flow down to the many scripts it calls. This adds a global integer variable set by disk-image-create DIB_DEBUG_TRACE. All scripts have a stanza added to detect this and turn on tracing. Any other tracing methods are rolled into this. So the standard header is --- if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then set -x fi set -eu set -o pipefail --- Multiple -x options can be specified to dib-create-image, which increases the value of DIB_DEBUG_TRACE. If script authors feel their script should only trace at higher levels, they should modify the "-gt" value. If they feel it should trace by default, they can modify the default value also. Changes to pachset 16 : scripts which currently trace themselves by default have retained this behaviour with DIB_DEBUG_TRACE defaulting to "1". This was done by running [1] on patch set 15. See the thread beginning at [2] dib-lint is also updated to look for the variable being matched. [1] https://gist.github.com/ianw/71bbda9e6acc74ccd0fd [2] http://lists.openstack.org/pipermail/openstack-dev/2014-November/051575.html Change-Id: I6c5a962260741dcf6f89da9a33b96372a719b7b0 2014-09-04 04:56:29 +00:00			`if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then`
			`set -x`
			`fi`
set -e all the things Using set -e in all of our scripts will prevent some subtle bugs from slipping in, and will allow us to enforce use of set -e with tooling. This change also adds -u and set -o pipefail in the less complex scripts where it is unlikely to cause problems. A follow-up change will enable those options in the complex scripts so that if it breaks something it can be reverted easily. Change-Id: I0ad358ccb98da7277a0ee2e9ce8fda98438675eb 2014-03-29 03:28:22 +00:00			`set -eu`
			`set -o pipefail`

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			`# without these files, cloud-init will not perform stock operations such as`
			`# generating sshd hostkeys.`

			`mkdir -p /var/lib/cloud/seed/nocloud`
			`touch /var/lib/cloud/seed/nocloud/user-data`
			`touch /var/lib/cloud/seed/nocloud/meta-data`