sig_cloud/diskimage-builder
11
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
diskimage-builder/elements/ramdisk
History
Chris Jones f093d4d38d Fix troubleshooting override. 
We can now actually override the $TROUBLESHOOT environment variable in
ramdisks, by not declaring it as readonly. Yay for insufficient
end-to-end testing.

Change-Id: I026c9dbdd411bf3eb945d5b18188eb1eedf3850a
2013-11-19 11:25:58 +00:00
..
cleanup.d /bin/bash all the things. 2013-11-17 16:59:31 -06:00
extra-data.d Fix troubleshooting override. 2013-11-19 11:25:58 +00:00
init.d Split network bringup out of base ramdisk init. 2013-11-17 20:37:26 +00:00
post-install.d Remove BUSYBOX variable from ramdisk-defaults 2013-11-11 14:36:15 +01:00
README.md Document ramdisk troubleshooting. 2013-11-18 19:45:59 +00:00

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.md of the project, for more information about the mechanisms available to a ramdisk element.