Red Hat Bugzilla – Bug 1476293
[RFE] Configure BMaaS to boot instances from cinder volumes
Last modified: 2018-02-13 10:45:38 EST
Boot from volume has recently been added to Ironic upstream. Now that it has
ironic if deployed in the overcloud should be capable of booting baremetal instances from images on cinder volumes.
The ironic part is done, and the THT part might be done already too. Needs testing from dev before handing to qe.
Upstream testing done, boot from cinder volume in the tripleo overcloud is working over iscsi. One bug found and fixed
The image being used must be setup to use BFV, for the CentOS cloud image this means two things
The kernel must be booted with rd.iscsi.firmware=1 so that iscsi target details are read from the firmware (passed to it by ipxe), this needs to be added to the grub config
The ramdisk in the image needs to have the iscsi dracut module in it, this is achieved by installing “iscsi-initiator-utils” in the image then adding the network and iscsi modules to the ramdisk
$ dracut --force --add "network iscsi" $RAMDISK $KERNEL_VERSION
Both of these can be achieved by using guestmount (or similar) and making the required changes in a chroot.
Many thanks Derek! We'd need to make sure that the RHEL KVM Guest Image , which is a whole-disk image. Would this be possible to test with? Mainly because we should have it documented downstream for the RHEL KVM Guest Image (ideally upstream with RHEL and CentOS and other flavours).
Derek, is this ready to QA? It looks like it can go to POST if all the patches are finished, right?
(In reply to Ramon Acedo from comment #6)
> Many thanks Derek! We'd need to make sure that the RHEL KVM Guest Image ,
> which is a whole-disk image. Would this be possible to test with? Mainly
> because we should have it documented downstream for the RHEL KVM Guest Image
> (ideally upstream with RHEL and CentOS and other flavours).
> Derek, is this ready to QA? It looks like it can go to POST if all the
> patches are finished, right?
Also note that adding rd.iscsi.firmware=1 to the kernel params currently means that the image can't be used for localboot, so as is we would need an iscsi image and a separate localboot image. I have submitted a fix to dracut so they can be common https://github.com/dracutdevs/dracut/pull/298
we should then be able to create a image that can do both bfv and localboot.
images problems aside, we also need to figure out a solution for the metadata service which doesn't seem to be working for ironic in the overcloud. This wasn't needed up to now as config drive was used but config drive isn't a thing in BFV. I'm looking into this now.
bug for dracut reported here, it shouldn't stall this bugs as its not about support in tripleo
the metadata service works once a router is created and the provisioning subnet is attache to it. All is working upstream.