sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1f38bfad41
diskimage-builder/elements/ironic-agent/cleanup.d/99-ramdisk-create

25 lines
533 B
Plaintext
Raw Normal View History

Add element for building ramdisk with ironic-python-agent This element creates kernel and ramdisk files based on Fedora, example: disk-image-create -a i386 -o test fedora ironic-agent disable-selinux Change-Id: Ifa133d1680b81cb87d32a405aa7d7b40fe91f835
2014-06-27 11:54:29 +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
Add element for building ramdisk with ironic-python-agent This element creates kernel and ramdisk files based on Fedora, example: disk-image-create -a i386 -o test fedora ironic-agent disable-selinux Change-Id: Ifa133d1680b81cb87d32a405aa7d7b40fe91f835
2014-06-27 11:54:29 +00:00
set -eu
set -o pipefail
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
Add element for building ramdisk with ironic-python-agent This element creates kernel and ramdisk files based on Fedora, example: disk-image-create -a i386 -o test fedora ironic-agent disable-selinux Change-Id: Ifa133d1680b81cb87d32a405aa7d7b40fe91f835
2014-06-27 11:54:29 +00:00
[ -n "$TARGET_ROOT" ]
source $_LIB/img-functions
Allow absolute path to image with ironic-agent The element was prepending the work directory forcibly, which will have problems when the image name has an absolute path, which is allowed. Change-Id: I0cb7b96e24daab8ee73611936af72074c70ac1aa Closes-Bug: #1400405
2014-12-13 17:14:06 +00:00
IMAGE_PATH=$(readlink -f $IMAGE_NAME)
Add element for building ramdisk with ironic-python-agent This element creates kernel and ramdisk files based on Fedora, example: disk-image-create -a i386 -o test fedora ironic-agent disable-selinux Change-Id: Ifa133d1680b81cb87d32a405aa7d7b40fe91f835
2014-06-27 11:54:29 +00:00
cd $TARGET_ROOT
echo "#disabled" > ./tmp/fstab.new
sudo mv ./tmp/fstab.new ./etc/fstab
sudo ln -s ./sbin/init ./
ironic-agent: exclude content of /tmp from initramfs /tmp does not contain anything useful anyway, and excluding its content makes the initramfs smaller too. Change-Id: Ia72867e0cdebacf668ac1a1f551a965da0d69694
2015-03-10 18:03:04 +00:00
sudo find . -path ./sys -prune -o -path ./proc -prune -o -path './tmp/*' -prune -o -print | sudo cpio -o -H newc | gzip > ${IMAGE_PATH}.initramfs
Add element for building ramdisk with ironic-python-agent This element creates kernel and ramdisk files based on Fedora, example: disk-image-create -a i386 -o test fedora ironic-agent disable-selinux Change-Id: Ifa133d1680b81cb87d32a405aa7d7b40fe91f835
2014-06-27 11:54:29 +00:00
select_boot_kernel_initrd $TARGET_ROOT
Allow absolute path to image with ironic-agent The element was prepending the work directory forcibly, which will have problems when the image name has an absolute path, which is allowed. Change-Id: I0cb7b96e24daab8ee73611936af72074c70ac1aa Closes-Bug: #1400405
2014-12-13 17:14:06 +00:00
sudo cp $BOOTDIR/$KERNEL ${IMAGE_PATH}.vmlinuz
Reference in New Issue Copy Permalink