openstack
/
diskimage-builder
Code Issues Proposed changes
diskimage-builder/elements/dracut-ramdisk
History
Ben Nemec ffe825113e Make troubleshoot work with dracut ramdisks 
Currently, calling the troubleshoot function in a ramdisk script
doesn't work as expected on dracut ramdisks.  This adds an alternate
troubleshoot implementation that will behave as intended.

I did not make it conditional on a kernel param as was done in the
original because dracut can behave strangely if you allow it to
continue after an error.  Always dropping to a shell immediately
should be less confusing.

Change-Id: I98000f4ac6d7890b1f44fe4d10394ac0ea332fcb
 		2015-04-08 12:54:32 -05:00
..
binary-deps.d Remove duplicate binary-deps from dracut-ramdisk 2014-11-14 12:43:49 -06:00
dracut-drivers.d Allow elements to add drivers to dracut 2015-03-18 11:40:20 -05:00
environment.d Enable dracut deploy ramdisks 2014-10-17 21:44:09 -05:00
extra-data.d/scripts/module Make troubleshoot work with dracut ramdisks 2015-04-08 12:54:32 -05:00
init.d Make troubleshoot work with dracut ramdisks 2015-04-08 12:54:32 -05:00
install.d Standarise tracing for scripts 2015-02-12 10:41:32 +11:00
post-install.d Allow elements to add drivers to dracut 2015-03-18 11:40:20 -05:00
README.rst Allow elements to add drivers to dracut 2015-03-18 11:40:20 -05:00
element-deps Refactor deploy ramdisk to allow use of targetcli 2015-03-18 11:42:00 -05:00
pkg-map Enable dracut deploy ramdisks 2014-10-17 21:44:09 -05:00
source-repository-dracut Enable dracut deploy ramdisks 2014-10-17 21:44:09 -05:00

README.rst

dracut-ramdisk

Build Dracut-based ramdisks

This is an alternative to the ramdisk element that uses Dracut to provide the base system functionality instead of Busybox.

For elements that need additional drivers in the ramdisk image, a dracut-drivers.d feature is included that works in a similar fashion to the binary-deps.d feature. The element needing to add drivers should create a dracut-drivers.d directory and populate it with a single file listing all of the kernel modules it needs added to the ramdisk. Comments are not supported in this file. Note that these modules must be installed in the chroot first.

By default, the virtio, virtio_net, and virtio_blk modules are included so that ramdisks are able to function properly in a virtualized environment.