<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 2, 2012, at 6:15 PM, Jian Hua Geng <<a href="mailto:gengjh@cn.ibm.com">gengjh@cn.ibm.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><p><font size="3" face="sans-serif">I saw the comments in the </font><a href="https://bugs.launchpad.net/nova/+bug/1029647"><font size="3" color="#0000FF" face="serif"><u>https://bugs.launchpad.net/nova/+bug/1029647</u></font></a><font size="3" face="serif"> </font><font size="3" face="sans-serif">, can anyone give me more detail introduction of this decision about </font><font size="3" face="serif">why the functionality for using an image id for config drive was removed</font><font size="2" face="sans-serif">?</font><font size="3" face="sans-serif"> </font><br>
<br>
<font size="3" face="sans-serif">Just for example for our requirement: We want create a CDROM and write some information in it such as the sysprep info for windows when run vm.</font><br>
<font size="3" face="sans-serif">First we need extend the config drive to support both cdrom and file disk device, second we create an iso image in glance which is used to save the sysprep info and share with other user in cloud, then wen can use this config_drive_id to load the iso.</font><br>
<font size="3" face="sans-serif">Have any suggestion or solution for this requirement?</font><br></p></div></blockquote><div>Here is one option that you could use. Create a volume instead of an image (or create the volume from the image), snapshot the volume. If you pass the volume snapshot in as a secondary drive in block_device_mapping on boot, then you will get a volume copy of the image. If it is delete_on_terminate=True then the volume will be deleted when you terminate the vm.</div><div><br></div><div>Vish</div></div></body></html>