diskimage-builder/elements/ramdisk
Ben Nemec 79ab95b16e Make sure all scripts are set -e
If scripts are not set -e then errors can be ignored, causing more
confusing failures later.

Also adds an exclusion comment to the ramdisk init script since we
don't want that to exit on failure.

Change-Id: Idf43993bd10b1ef16c1d3b0d9df8d0ad94c46458
2014-05-02 17:18:54 -05:00
..
cleanup.d Default name for ramdisks to image. 2013-12-04 15:31:46 -05:00
extra-data.d Make sure all scripts are set -e 2014-05-02 17:18:54 -05:00
init.d indent: replace tab by 4 spaces 2014-04-18 10:32:43 +02:00
install.d Fix ramdisk element for openSUSE 2014-01-23 14:26:11 +01:00
post-install.d Fix set -eu and pipefail failures 2014-04-15 20:53:15 -05:00
README.md Document ramdisk troubleshooting. 2013-11-18 19:45:59 +00:00

This is the ramdisk element.

Almost any user building a ramdisk will want to include this in their build, as it triggers many of the vital functionality from the basic diskimage-builder libraries (such as init script aggregation, busybox population, etc).

An example of when one might want to use this toolchain to build a ramdisk would be the initial deployment of baremetal nodes in a TripleO setup. Various tools and scripts need to be injected into a ramdisk that will fetch and apply a machine image to local disks. That tooling/scripting customisation can be easily applied in a repeatable and automatable way, using this element.

See the top-level README.md of the project, for more information about the mechanisms available to a ramdisk element.