1f328087d9
We now allow operators to drop into a troubleshooting shell while booting a deploy ramdisk, without having to have pre-configured their desire to do so ahead of time, by means of a 10 second pause for them to press a key. Change-Id: I05ffa1ebaa95c83dee7bd2a2f52ba4c08928bb10 |
||
|---|---|---|
| .. | ||
| cleanup.d | ||
| extra-data.d | ||
| post-install.d | ||
| 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.
See the top-level README.me of the project, for more information about the mechanisms available to a ramdisk element.