As one of the original authors of dracut, I would love to see it being used to build initramfs images for TripleO. dracut is flexible, works across a wide variety of distros, and removes the need to have special-purpose toolchains and packages for use by the initramfs.
On Thu, Jul 3, 2014 at 10:12 PM, Ben Nemec <[email protected]> wrote: > I've recently been looking into using dracut to build the > deploy-ramdisks that we use for TripleO. There are a few reasons for > this: 1) dracut is a fairly standard way to generate a ramdisk, so users > are more likely to know how to debug problems with it. 2) If we build > with dracut, we get a lot of the udev/net/etc stuff that we're currently > doing manually for free. 3) (aka the self-serving one ;-) RHEL 7 > doesn't include busybox, so we can't currently build ramdisks on that > distribution using the existing ramdisk element. > > For the RHEL issue, this could just be an alternate way to build > ramdisks, but given some of the other benefits I mentioned above I > wonder if it would make sense to look at completely replacing the > existing element. From my investigation thus far, I think dracut can > accommodate all of the functionality in the existing ramdisk element, > and it looks to be available on all of our supported distros. > > So that's my pitch in favor of using dracut for ramdisks. Any thoughts? > Thanks. > > https://dracut.wiki.kernel.org/index.php/Main_Page > > -Ben > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
