diskimage-builder/diskimage_builder/elements/ironic-agent/cleanup.d/99-ramdisk-create

57 lines
1.8 KiB
Plaintext
Raw Normal View History

#!/bin/bash
# dib-lint: disable=safe_sudo
if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then
set -x
fi
set -eu
set -o pipefail
[ -n "$TARGET_ROOT" ]
USER=${USER:-$(whoami)}
source $_LIB/img-functions
IMAGE_PATH=$(readlink -f $IMAGE_NAME)
cd $TARGET_ROOT
echo "#disabled" > ./tmp/fstab.new
sudo mv ./tmp/fstab.new ./etc/fstab
sudo ln -s ./sbin/init ./
# Note: The pci.ids, which is used by lshw, locate on Ubuntu
# in /usr/share/misc. Therefore we are removing only the
# ./usr/share/misc/m* (will remove the magic and magic.mgc files).
# on RHEL pci.ids is locate on /usr/share/hwdata/pci.ids.
sudo find . -xdev \
-path './sys/*' -prune -o \
-path './tmp/*' -prune -o \
-path './boot/*' -prune -o \
-path './root/.cache' -prune -o \
Clean more from ironic-agent ramdisk image While we already clean a number of things off the ironic-agent ramdisk, there are a few more significant ones that we should add to the list. First is the kernel source. If you're rebuilding your kernel on the agent ramdisk after the initial image build, then you need to re-examine your life choices. ;-) Second is /var/cache. On yum-based distros, this contains a large number of yum cache files that take up significant space. We don't really want to be copying around caches when booting a ramdisk anyway, so cleaning this is the right thing to do regardless. Third is all *.pyc or *.pyo files. There are a lot of these, so they eat up significant space and bloat the number of files in the ramdisk, which makes it take longer to build. the only purpose for the files is to slightly speed up Python app startup, and we probably lose more time transferring the files over the network than we would gain in quicker start times. Note that we were already trying to remove these, but for some reason I was still seeing them show up in my final images. It makes more sense to put them in the same pruning command as all the others anyway. Fourth is /usr/include. These are files only needed for compilation. See above for my thoughts on compiling in a ramdisk. These changes have reduced the agent ramdisk from 391 MB to 333 MB in my local centos 7 builds, and have reduced the number of files in the ramdisk by over 18000. Change-Id: I550f9904b9afd12d48da9ba24559acb23133d076
2016-06-24 16:28:24 +00:00
-path './usr/include/*' -prune -o \
-path './usr/lib/locale/*' -prune -o \
-path './usr/share/doc/*' -prune -o \
-path './usr/share/man/*' -prune -o \
-path './usr/share/info/*' -prune -o \
-path './usr/share/licenses/*' -prune -o \
-path './usr/share/misc/m*' -prune -o \
Clean more from ironic-agent ramdisk image While we already clean a number of things off the ironic-agent ramdisk, there are a few more significant ones that we should add to the list. First is the kernel source. If you're rebuilding your kernel on the agent ramdisk after the initial image build, then you need to re-examine your life choices. ;-) Second is /var/cache. On yum-based distros, this contains a large number of yum cache files that take up significant space. We don't really want to be copying around caches when booting a ramdisk anyway, so cleaning this is the right thing to do regardless. Third is all *.pyc or *.pyo files. There are a lot of these, so they eat up significant space and bloat the number of files in the ramdisk, which makes it take longer to build. the only purpose for the files is to slightly speed up Python app startup, and we probably lose more time transferring the files over the network than we would gain in quicker start times. Note that we were already trying to remove these, but for some reason I was still seeing them show up in my final images. It makes more sense to put them in the same pruning command as all the others anyway. Fourth is /usr/include. These are files only needed for compilation. See above for my thoughts on compiling in a ramdisk. These changes have reduced the agent ramdisk from 391 MB to 333 MB in my local centos 7 builds, and have reduced the number of files in the ramdisk by over 18000. Change-Id: I550f9904b9afd12d48da9ba24559acb23133d076
2016-06-24 16:28:24 +00:00
-path './usr/src/kernels/*' -prune -o \
-path './var/cache/*' -prune -o \
-name '*.pyc' -prune -o \
-name '*.pyo' -prune -o \
-print | sudo cpio -o -H newc | gzip > ${IMAGE_PATH}.initramfs
select_boot_kernel_initrd $TARGET_ROOT
sudo cp $BOOTDIR/$KERNEL ${IMAGE_PATH}.kernel
sudo chown $USER: ${IMAGE_PATH}.kernel
# TODO(lucasagomes): Create a hard link for the .vmlinuz file to keep
# it backward compatible. Remove it after it has been consistent and
# documented in both places for at least one full OpenStack release cycle
echo "WARNING: The kernel extension .vmlinuz has been deprecated. Please rely on the file with the extension .kernel instead."
sudo rm -f ${IMAGE_PATH}.vmlinuz
ln ${IMAGE_PATH}.kernel ${IMAGE_PATH}.vmlinuz