diskimage-builder/elements/base/install.d/10-cloud-init

#!/bin/bash
# Tweak the stock ubuntu cloud-init config

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

# cloud-init May not actually be installed
mkdir -p /etc/cloud/cloud.cfg.d
dd of=/etc/cloud/cloud.cfg.d/10_etc_hosts.cfg << EOF
manage_etc_hosts: localhost
EOF
Add a flavour for doing generic this-node-is-in-a-cloud stuff, like cloud-init tweaks. 2012-11-13 02:34:29 +00:00			`#!/bin/bash`
			`# Tweak the stock ubuntu cloud-init config`

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 -u and -o pipefail everywhere As with the previous similar changes, this is intended to catch problems as they happen instead of ignoring them and continuing on to potentially fail later. Setting this on all existing scripts will allow us to enforce use via Jenkins. Change-Id: Iad2d490c86dceab148ea9ab08f457c49a5d5352e 2014-04-03 02:24:15 +00:00			`set -eu`
			`set -o pipefail`
Add a flavour for doing generic this-node-is-in-a-cloud stuff, like cloud-init tweaks. 2012-11-13 02:34:29 +00:00
Handle non-cloud-init installs Not all operating-system elements install cloud-init, but the base element assumes its existence. Create the directory if it does not exist. Change-Id: I4bda8dc5d200825ea0c8163a4e5c44050a45083f 2015-03-23 20:14:07 +00:00			`# cloud-init May not actually be installed`
			`mkdir -p /etc/cloud/cloud.cfg.d`
Don't use sudo in base. Install.d hooks are already root, we don't need plain sudo there. Change-Id: I69747049b2f5f649eb503a24487bbb3a4151ae21 2013-02-27 02:51:10 +00:00			`dd of=/etc/cloud/cloud.cfg.d/10_etc_hosts.cfg << EOF`
Switch manage_etc_hosts from True to localhost When set to true this cloud-init setting overwrites the /etc/hosts file at reboot, breaking stuff in TripleO where controllers rely on resolving each other by name. We still want cloud-init to add in there a mapping for the local fqdn, so we switched to 'localhost' [1] 1. http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt#L470 Change-Id: I85468dece3b67f39841aa826f9b7ca4bf113027a Closes-Bug: 1411594 2015-01-21 12:21:53 +00:00			`manage_etc_hosts: localhost`
Add a flavour for doing generic this-node-is-in-a-cloud stuff, like cloud-init tweaks. 2012-11-13 02:34:29 +00:00			`EOF`