Open Stack

Hello folks,

I was looking into the provisioning process in OpenStack. If
force_raw_images flag is set to False, the provisioning process looks like:

(1) Copy the image
(2) Create a copy of the copied image to an appropriate flavor name
(3) Start the VM

while if it is set to True, the provisioning process looks like:

(1) Copy the image
(2) Convert image to raw
(3) Create a copy of the converted raw image to an appropriate flavor name
(4) Start the VM

For the former, copying the image to a flavor name is a redundant process.
Can that be eliminated? Any thoughts?

Provisioning images from very large images (>20G) necessitate investigating
all aspects of provisioning process. The reason one can have very large
images is due to VM snapshotting or software bundling etc.

Thanks.

Best Regards,

Salman A. Baset
Research Staff Member, IBM T. J. Watson Research Center
Tel: +1-914-784-6248
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120507/257a4f47/attachment.html>