5e18777691
This change adds support in ramdisk element for recognising boot from virtual media cdrom and read the parameters from the configuration file in virtual media floppy. Change-Id: I28ca888b4ead4905f7141b38ed4b9a3614d00d26 Closes-Bug: #1321564 |
||
|---|---|---|
| .. | ||
| binary-deps.d | ||
| cleanup.d | ||
| extra-data.d | ||
| init.d | ||
| install.d | ||
| post-install.d | ||
| element-deps | ||
| pkg-map | ||
| 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.
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.