[Openstack] [openstack] config_drive <Image UUID> doesn't create disk.config

Jian Hua Geng gengjh at cn.ibm.com
Mon Dec 10 01:47:59 UTC 2012


Hi Vish,

I will work on this block_device_mapping enhancement if there are no other
guys working on this.

--------------------------------------------------
Best regard,
David Geng
--------------------------------------------------


                                                                           
             Vishvananda                                                   
             Ishaya                                                        
             <vishvananda at gmai                                          To 
             l.com>                    Jian Hua Geng/China/IBM at IBMCN,      
                                                                        cc 
             12/06/2012 02:37          openstack at lists.launchpad.net       
             AM                                                    Subject 
                                       Re: [Openstack] [openstack]         
                                       config_drive <Image UUID> doesn't   
                                       create disk.config                  
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           





On Dec 4, 2012, at 3:48 AM, Jian Hua Geng <gengjh at cn.ibm.com> wrote:



      Vish,

      Many thanks for u comments, but as you know to support windows
      sysprep image, we need save the unattend.xml in the CDROM or C:\
      device. So, we want to extend the config drive to attach a CDROM
      device when launch VM.

      Anyway, I think attach a CDROM when launch new VM is a common
      requirement, right?



Sounds like we need some modifications to allow for an attached cd-rom to
be specified in block_device_mapping.

Vish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121210/11a330a9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121210/11a330a9/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic15985.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121210/11a330a9/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121210/11a330a9/attachment-0002.gif>


More information about the Openstack mailing list