diskimage-builder/elements/ramdisk
Derek Higgins 5671a38e8e Fix dhclient in Fedora ramdisks
Copy all of the necessary parts for a Fedora based dhclient to work. This
includes a number of network scripts. Also grab the ip command supplied by
the iproute package, the busybox "ip addr" command was missing the valid_lft
and preferred_lft options.

This will allow the dhcp to work in the ramdisk instead of getting passed the
PXE net config.

Related-Bug: #1417026
Change-Id: I8feee9a740855dab7b47162c5727bf91db77fcc6
2015-03-31 12:27:40 +01:00
..
binary-deps.d Fix dhclient in Fedora ramdisks 2015-03-31 12:27:40 +01: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.