<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 6, 2012, at 11:48 PM, Salman A Baset wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><p><font size="2" face="sans-serif">Hello folks,</font><br>
<br>
<font size="2" face="sans-serif">I was looking into the provisioning process in OpenStack. If force_raw_images flag is set to False, the provisioning process looks like:</font><br>
<br>
<font size="2" face="sans-serif">(1) Copy the image </font><br>
<font size="2" face="sans-serif">(2) Create a copy of the copied image to an appropriate flavor name</font><br>
<font size="2" face="sans-serif">(3) Start the VM</font><br>
<br>
<font size="2" face="sans-serif">while if it is set to True, the provisioning process looks like:</font><br>
<br>
<font size="2" face="sans-serif">(1) Copy the image</font><br>
<font size="2" face="sans-serif">(2) Convert image to raw</font><br>
<font size="2" face="sans-serif">(3) Create a copy of the converted raw image to an appropriate flavor name</font><br>
<font size="2" face="sans-serif">(4) Start the VM</font><br>
<br>
<font size="2" face="sans-serif">For the former, copying the image to a flavor name is a redundant process. Can that be eliminated? Any thoughts?</font></p><div><br></div></div></blockquote><br></div><div>The copy is to resize the image to the size requested by the user. Are you suggesting that it could be streamed from glance and resized to the proper size on the fly? It seems like that would be possible although it would probably make future launches of the same instances of a different size a bit slower.</div><div><br></div><div>Vish</div><br></body></html>