disk-image-create doesn't export the kernel and ramdisk

[Robert Collins]

for non 'vm' images - partition images - we have to have the kernel and ramdisk to boot the machine, but we don't export them. As a result we end up qemu-nbd mounting the images and scrovening around inside it. This is a little slow and entirely unnecessary.

ramdisk-image-create exports multiple files (ramdisk and kernel), we can do something similar for partition images: output the partition image *and* the kernel and ramdisk to use, which will then let the image be loaded into glance with no further introspection.

Relatedly, the script disk-image-get-kernel is fragile and unnecessary - it can be removed with this bug fixed.

[Richard Jones (rjones-redhat)]

virt-builder --get-kernel disk.img

will get the latest kernel & initramfs from any Linux disk image.

[Chris Jones (cmsj)]

We shouldn't need to use any tools, we have the image mounted during the build phase, so we should just pull the kernel/ramdisk out then, like we do with ramdisk builds.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/68019
Committed: https://git.openstack.org/cgit/openstack/diskimage-builder/commit/?id=58c755cf4c3219393266c0f4e8494cd447c844c9
Submitter: Jenkins
Branch: master

commit 58c755cf4c3219393266c0f4e8494cd447c844c9
Author: Steve Kowalik <email address hidden>
Date: Mon Jan 20 23:00:21 2014 +1100

    Create a new baremetal element

    Rather than using a script to mount the image using nbd to extract the
    kernel and ramdisk, make a new element called baremetal, which contains
    a cleanup.d script that will copy them out to <image name>.{vmlinuz,initrd}.

    Closes-Bug: 1224669
    Change-Id: I8f3569aa12148d18b1c8242b6fbbd8857894b26f