sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
83aee34534
diskimage-builder/elements/ramdisk
History
Ben Nemec 16be6d7ce0 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-05-06 15:51:07 -05:00
..
cleanup.d set -u and -o pipefail everywhere 2014-05-06 15:51:07 -05:00
extra-data.d set -u and -o pipefail everywhere 2014-05-06 15:51:07 -05:00
init.d indent: replace tab by 4 spaces 2014-04-18 10:32:43 +02:00
install.d set -u and -o pipefail everywhere 2014-05-06 15:51:07 -05:00
post-install.d set -u and -o pipefail everywhere 2014-05-06 15:51:07 -05:00
README.md Document ramdisk troubleshooting. 2013-11-18 19:45:59 +00:00

README.md

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.