diskimage-builder/elements/ramdisk
Ben Nemec c98a17222f Refactor deploy ramdisk to allow use of targetcli
RHEL 7 does not ship tgtadm or tgtd so they cannot be used in the
deploy ramdisk.  This change separates the tgt-specific parts of
the ramdisk into their own element, and adds a new one that supports
targetcli instead.

For now, the tgt implementation can only be used with traditional
busybox ramdisks and the targetcli one can only be used with dracut.
This is because dracut is primarily used for RHEL right now so it
makes sense to keep the dependencies simple.  If there is a future
desire to mix and match the implementations that could be done, but
it would require users to explicitly select between tgt and
targetcli.

Change-Id: I4f99c91016287e08d836095c2f2261de8b45abdc
Co-Authored-By: James Slagle <jslagle@redhat.com>
2015-03-18 11:42:00 -05: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 Standarise tracing for scripts 2015-02-12 10:41:32 +11:00
post-install.d Standarise tracing for scripts 2015-02-12 10:41:32 +11:00
element-deps Refactor deploy ramdisk to allow use of targetcli 2015-03-18 11:42:00 -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.