diskimage-builder/diskimage_builder/elements/dracut-ramdisk/install.d/20-install-dracut-deps

#!/bin/bash

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

DRACUT_NETWORK="dracut-network"
if [ 'ubuntu' = "$DISTRO_NAME" ]; then
    DRACUT_NETWORK=
    # Install Dracut from source because the packaged version is
    # broken and old.  For Dracut builds we throw away the chroot
    # anyway so it won't matter if we've installed some build deps.
    install-packages build-essential arping
    pushd /tmp
    tar xJvf dracut.tar.xz
    pushd dracut-$DRACUT_VERSION
    ./configure
    make
    make install
    popd
    popd
fi

PACKAGES=$(pkg-map --element dracut-ramdisk ncat tftp)
install-packages $DRACUT_NETWORK wget $PACKAGES
Enable dracut deploy ramdisks The element builds dracut from source on Ubuntu because the Ubuntu dracut package is broken and very old, so it can't be installed properly and causes a number of other issues that are fixed by using a newer version of Dracut. This initial version should work in virtualized environments. Further validation of its suitability for real baremetal deployments will need to be done in the future, but this should be sufficient to enable that work. Regarding Dracut specifically, in order to limit the changes needed in the existing scripts this element continues to use a cut down version of the /init script that we were building for the existing ramdisk. However, instead of running it as pid 0 it is run as a Dracut pre-mount hook. This allows Dracut to set up all of the hardware and system bits, while falling early enough in the Dracut sequence to complete the deployment before Dracut would try to boot off the hard disk. bp tripleo-juno-dracut-ramdisks Change-Id: I144c8993fe040169f440bd4f7a428fdbe3d745cf 2014-09-26 05:12:32 +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:-1} -gt 0 ]; then`
			`set -x`
			`fi`
			`set -eu`
Enable dracut deploy ramdisks The element builds dracut from source on Ubuntu because the Ubuntu dracut package is broken and very old, so it can't be installed properly and causes a number of other issues that are fixed by using a newer version of Dracut. This initial version should work in virtualized environments. Further validation of its suitability for real baremetal deployments will need to be done in the future, but this should be sufficient to enable that work. Regarding Dracut specifically, in order to limit the changes needed in the existing scripts this element continues to use a cut down version of the /init script that we were building for the existing ramdisk. However, instead of running it as pid 0 it is run as a Dracut pre-mount hook. This allows Dracut to set up all of the hardware and system bits, while falling early enough in the Dracut sequence to complete the deployment before Dracut would try to boot off the hard disk. bp tripleo-juno-dracut-ramdisks Change-Id: I144c8993fe040169f440bd4f7a428fdbe3d745cf 2014-09-26 05:12:32 +00:00			`set -o pipefail`

			`DRACUT_NETWORK="dracut-network"`
			`if [ 'ubuntu' = "$DISTRO_NAME" ]; then`
			`DRACUT_NETWORK=`
			`# Install Dracut from source because the packaged version is`
			`# broken and old. For Dracut builds we throw away the chroot`
			`# anyway so it won't matter if we've installed some build deps.`
			`install-packages build-essential arping`
			`pushd /tmp`
			`tar xJvf dracut.tar.xz`
			`pushd dracut-$DRACUT_VERSION`
			`./configure`
			`make`
			`make install`
			`popd`
			`popd`
			`fi`

			`PACKAGES=$(pkg-map --element dracut-ramdisk ncat tftp)`
			`install-packages $DRACUT_NETWORK wget $PACKAGES`