c9f432d45b
We now run the network bringup portion of the ramdisk init from an init.d script, thus allowing image builders to inject code into the init script before that point (e.g. configure network hardware). The environment variables used by the network bringup code are retained in the base init script so they can be overridden by init.d fragments. Change-Id: I1ef0bb21e7f26c0ff3f02266f853ce5402bcb94d Closes-Bug: #1252023 |
||
|---|---|---|
| .. | ||
| cleanup.d | ||
| extra-data.d | ||
| init.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.