Re: [openstack-dev] [TripleO] Building deploy ramdisks with dracut

2014-07-08 Thread 韦远科
I once used update-initramfs under ubuntu, building ramdisk to boot from remote iscsi disk. - 韦远科 3479 中国科学院 计算机网络信息中心 On Tue, Jul 8, 2014 at 12:15 PM, Adam Young ayo...@redhat.com wrote: On 07/07/2014 01:16 PM, Victor Lowther

Re: [openstack-dev] [TripleO] Building deploy ramdisks with dracut

2014-07-08 Thread Robert Collins
We got to the current place thusly: - The initial ramdisk code in Nova-baremetal needed a home other than a wikipage. - And then there was a need/desire to build ramdisks from a given distro != current host OS. - Various bits of minor polish to make it more or less in-line with the emerging

Re: [openstack-dev] [TripleO] Building deploy ramdisks with dracut

2014-07-08 Thread Ben Nemec
On 07/08/2014 03:28 AM, Robert Collins wrote: We got to the current place thusly: - The initial ramdisk code in Nova-baremetal needed a home other than a wikipage. - And then there was a need/desire to build ramdisks from a given distro != current host OS. - Various bits of minor polish

Re: [openstack-dev] [TripleO] Building deploy ramdisks with dracut

2014-07-07 Thread Victor Lowther
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

Re: [openstack-dev] [TripleO] Building deploy ramdisks with dracut

2014-07-07 Thread Adam Young
On 07/07/2014 01:16 PM, Victor Lowther wrote: 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

[openstack-dev] [TripleO] Building deploy ramdisks with dracut

2014-07-03 Thread Ben Nemec
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