diskimage-builder/elements/ramdisk
Ralf Haferkamp 5fb556f44d Fix ramdisk element for openSUSE
The openSUSE base image does not contain /sbin/dhclient-script, install it.

Change-Id: Ib0db15139930d42bd60213437ef63d7915d8134a
2014-01-23 14:26:11 +01:00
..
cleanup.d Default name for ramdisks to image. 2013-12-04 15:31:46 -05:00
extra-data.d Wait for tgtd socket to be available 2014-01-14 12:53:03 -05:00
init.d Split network bringup out of base ramdisk init. 2013-11-17 20:37:26 +00:00
install.d Fix ramdisk element for openSUSE 2014-01-23 14:26:11 +01:00
post-install.d Remove BUSYBOX variable from ramdisk-defaults 2013-11-11 14:36:15 +01: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.