diskimage-builder/elements/ramdisk
yogananth subramanian 57705694e7 ramdisk-image-create: add support for vmlinux file
ramdisk-image-create assumes the presence of vmlinuz file in OS image.
But ubuntu PPC LE images have only vmlinux file. This patch adds
support for using vmlinux file.

Change-Id: I5dd0b8ceb46b73be57d4c15b39b96f99b524fa3f
Closes-Bug: 1413362
2015-01-22 02:10:39 +05:30
..
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.md Reinstate Trusty as default for Ubuntu 2014-06-03 16:28:25 -07: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.

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.