sig_cloud/diskimage-builder
11
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
072fee1a74
diskimage-builder/elements/ramdisk
History
Robert Collins 072fee1a74 Ensure we can read the kernel out. 
If the kernel is restricted read (as a security measure) we may not be
able to read it without chmodding it.

Change-Id: Ib577705c27d8c351288334de03a7848cf49f2de9
2014-05-14 04:25:05 +12:00
..
cleanup.d Ensure we can read the kernel out. 2014-05-14 04:25:05 +12: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.