openstack
/
diskimage-builder
Code Issues Proposed changes
diskimage-builder/elements/ramdisk
History
Chris Jones 8d1ce9c0c3 Build ramdisks in an image chroot. 
Ramdisks are now built inside a chroot which is built by the normal
image build process. Doing so improves our independence of the
precise state of the build host.

This fixes bug 1194055.

Change-Id: Ibc254fbb9e7b404b5f38c1b35bcde8a4136e8e28
 		2013-07-12 11:09:35 +01:00
..
cleanup.d Build ramdisks in an image chroot. 2013-07-12 11:09:35 +01:00
extra-data.d Build ramdisks in an image chroot. 2013-07-12 11:09:35 +01:00
post-install.d Build ramdisks in an image chroot. 2013-07-12 11:09:35 +01:00
README.md Build ramdisks in an image chroot. 2013-07-12 11:09:35 +01: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.me of the project, for more information about the mechanisms available to a ramdisk element.