1d476dd994
When the kernel gets installed on Fedora, the rpm post scripts call "/bin/kernel-install" [1] to install it. This is a script provided by systemd. However, in [2], Fedora ships a patch to kernel-install that makes a call-out to /sbin/new-kernel-pkg -- the install script provided by grubby [3] Without grubby installed, systemd's kernel-install script goes off and runs dracut plugins directly [4], which eventually creates the initrd. For reasons that are not clearly explained, the initrd will end up in a a "machine-id" sub-directory of /boot (possibly, so you can symlink it?). It is also called "initrd", even though it's an initramfs, for historical reasons in dracut I think. It is at this point that I think 99-ramdisk has been written to move the generated initrd file back into /boot. Later on, when we build the image, we run grub-install and it picks up the kernel and the initrd and installs everything. grubby's new-kernel-pkg [6] it's very similar -- it uses dracut to make the initramfs ... but in this case it is put in /boot and is actually called initramfs. The subtle change that led me down this path is that dracut has been modified to have a "Recommends" for grubby for >F22 [7]. After discussing this change with the author, it turns out it was *always* intended to use the grubby-based kernel install scripts for Fedora -- our builds have been incorrect in not including the package. The author got sick of people removing the package and making unbootable systems, hence the change. Thus this removes the workarounds in 99-ramdisk and replace it with an install of the grubby package. grubby's kernel install script will put the kernel & generated initramfs in /boot, and it will be installed correctly via the usual grub install later when we build the disk image. I have built F22 & F23 fedora-minimal images with this and they boot. [1] http://pkgs.fedoraproject.org/cgit/kernel.git/tree/kernel.spec#n1832 [2] http://pkgs.fedoraproject.org/cgit/systemd.git/tree/kernel-install-grubby.patch [3] http://linux.die.net/man/8/new-kernel-pkg [4] https://github.com/haraldh/dracut/blob/master/50-dracut.install [5] |
||
|---|---|---|
| bin | ||
| diskimage_builder | ||
| doc/source | ||
| elements | ||
| lib | ||
| tests | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| babel.cfg | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Image building tools for OpenStack
diskimage-builder is a flexible suite of components for
building a wide-range of disk images, filesystem images and ramdisk
images for use with OpenStack.
This repository has the core functionality for building such images, both virtual and bare metal. Images are composed using elements; while fundamental elements are provided here, individual projects have the flexibility to customise the image build with their own elements.
For example:
$ DIB_RELEASE=trusty disk-image-create -o ubuntu-trusty.qcow2 vm ubuntuwill create a bootable Ubuntu Trusty based qcow2
image.
diskimage-builder is useful to anyone looking to produce
customised images for deployment into clouds. These tools are the
components of TripleO that are
responsible for building disk images. They are also used extensively to
build images for testing OpenStack itself, particularly with nodepool.
Platforms supported include Ubuntu, CentOS, RHEL and Fedora.
Full documentation, the source of which is in
doc/source/, is published at:
Copyright
Copyright 2012 Hewlett-Packard Development Company, L.P. Copyright (c) 2012 NTT DOCOMO, INC.
All Rights Reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.