| Awesome.
Feel free to file a blueprint for it. I also discussed with some people the other day the idea of allowing some additions to the config drive api to allow you to specify an unattend.xml when booting an instance that would put it in the proper place on the config drive. We could create an extension for this or perhaps just accept it in user-data. Would that be enough for you?
Vish Hi Vish,
I will work on this block_device_mapping enhancement if there are no other guys working on this.
--------------------------------------------------
Best regard,
David Geng
--------------------------------------------------
<graycol.gif>Vishvananda Ishaya ---12/06/2012 02:37:23 AM---Vishvananda Ishaya <vishvana...@gmail.com>
|
|
<ecblank.gif>
To | <ecblank.gif>
Jian Hua Geng/China/IBM@IBMCN,
|
<ecblank.gif>
cc | <ecblank.gif>
|
<ecblank.gif>
Subject | <ecblank.gif>
Re: [Openstack] [openstack] config_drive <Image UUID> doesn't create disk.config
|
| <ecblank.gif> | <ecblank.gif> |
|
On Dec 4, 2012, at 3:48 AM, Jian Hua Geng <gen...@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
|
<<inline: pic15985.gif>>
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
