Comment 2 for bug 1449084

Eli,

Can you explain why this is marked as incomplete? In my view, it is a bit misleading to present a 'Boot from Volume' option to the user when Openstack does not actually boot from the volume. In the case where the user is encrypting the volume, this presents a security vulnerability since the user will assume that they are booting from an encrypted volume when, in fact, they are booting from an unencrypted image from Nova's image cache.

As you correctly pointed out, there IS a way for the user to actually boot from a volume. The steps are as follows:

1. Attach a volume to an instance.
2. scp a raw image to the instance.
3. ssh into the instance, dd the image into the attached volume.
4. Terminate the instance.
5. Manually modify cinder's mysql database so that the volume is listed as bootable.
6. Boot an instance from the volume.

From my perspective, this is an unnecessarily laborious process for the user to perform anytime they want OpenStack to correctly boot from a volume.