diskimage-builder/elements/ramdisk
Gregory Haynes c4bbb6f3bc Create docs site containing element READMEs
We currently do not have the ability to create a docs site which
outlines all the elements.

Change-Id: I77ccf61e0c4b1509b3e7ce9b8f15ea5ccfd50d9b
2015-02-10 11:45:35 -08:00
..
binary-deps.d Move busybox binary-dep to ramdisk element 2014-10-21 16:05:19 -05:00
init.d Refactor ramdisk element to allow alternate implementations 2014-09-26 00:13:55 -05:00
install.d Refactor ramdisk element to allow alternate implementations 2014-09-26 00:13:55 -05:00
post-install.d ramdisk-image-create: add support for vmlinux file 2015-01-22 02:10:39 +05:30
element-deps Refactor ramdisk element to allow alternate implementations 2014-09-26 00:13:55 -05:00
pkg-map Fix ramdisk pkg-map for openSUSE 2014-09-02 11:20:08 +02:00
README.rst Create docs site containing element READMEs 2015-02-10 11:45:35 -08:00

=======
ramdisk
=======
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.

NOTE: ramdisks require 1GB minimum memory on the machines they are booting.

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