5aca301693
In preparation for enabling Dracut-based ramdisks, this change factors out functionality that is common to both busybox and Dracut ramdisks. Said functionality is moved to a ramdisk-base element which is added as a dependency of the ramdisk element. ramdisk now only contains the functionality specific to building busybox-based ramdisks. bp tripleo-juno-dracut-ramdisks Change-Id: Iad2907c8be491c88727d87ed5e5a720e5beb66c3 |
||
|---|---|---|
| .. | ||
| binary-deps.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.