<html><body>
<p><font size="2" face="sans-serif">I don't think these patches are conflicting.</font><br>
<font size="2" face="sans-serif">I will continue to work on this patch.</font><br>
<br>
<a href="https://review.openstack.org/#/c/34903/"><font size="3" color="#0000FF" face="serif"><u>https://review.openstack.org/#/c/34903/</u></font></a><font size="3" face="serif"> </font><br>
<br>
<br>
<font size="2" face="sans-serif">Thanks!</font><br>
<br>
<br>
<font size="2" face="sans-serif">Best Regards<br>
</font><br>
<br>
<font size="2" face="sans-serif">-------------------------------------------------------------------------------------------------------</font><br>
<br>
<font size="1" color="#535353" face="Lucida Console">Hi Arnaud, <br>
<br>
It's really good to know that your team are proposing the vcenter driver with OVA+glance datastore backend support. Thanks for sharing the information. OVA would be a good choice which will benefit users by avoiding only use flat image limited from current driver. <br>
<br>
But in my opinion, it may not conflict with deploying from template. From an end user perpective, if there are already a set of templates within vcenter, it's good for him to have openstack to deploy VM from it directly. He can touch an empty image in glance only with the metadata pointing to the template name. And boot vm from it. Also he can freely choose to generate a *ova with vmdk stream file and placed in certain datastore and deploy from VM from image location pointing to the datastore. These are two different usage scenarios per my understanding. <br>
<br>
And to go further, if there are some mechnism, that openstack can sync exsiting VM templates into Glance images. It can make this function more useful. <br>
<br>
<br>
<br>
<br>
Best Regards<br>
Zarric(Zhu Zhu)<br>
<br>
From: Arnaud Legendre<br>
Date: 2013-12-18 01:58<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [Nova][VMware] Deploy from vCenter template<br>
Hi Qui Xing,<br>
<br>
<br>
<br>
We are planning to address the vCenter template issue by levering the OVF/OVA capabilities.<br>
Kiran's implementation is tied to a specific VC and requires to add Glance properties that are not generic.<br>
For existing templates, the workflow will be:<br>
. generate an *.ova tarball (containing the *.ovf descriptor + *.vmdk stream-optimized) out of the template,<br>
. register the *.ova as a Glance image location (using the VMware Glance driver see bp [1]) or simply upload the *.ova to another Glance store,<br>
. The VMware driver in Nova will be able to consume the *.ova (either through the location or by downloading the content to the cache): see bp [2]. However, for Icehouse, we are not planning to actually consume the *.ovf descriptor (work scheduled for the J/K release).<br>
<br>
<br>
[1] </font><a href="https://blueprints.launchpad.net/glance/+spec/vmware-datastore-storage-backend"><font size="1" color="#BC1518" face="serif">https://blueprints.launchpad.net/glance/+spec/vmware-datastore-storage-backend</font></a><font size="1" color="#535353" face="Lucida Console"><br>
[2] </font><a href="https://blueprints.launchpad.net/nova/+spec/vmware-driver-ova-support"><font size="1" color="#BC1518" face="serif">https://blueprints.launchpad.net/nova/+spec/vmware-driver-ova-support</font></a><font size="1" color="#535353" face="Lucida Console"> <br>
<br>
<br>
If you have questions about [1], please send me an email. For [2], please reach vuil.<br>
</font><br>
<font size="2" face="sans-serif"><br>
<br>
<br>
</font></body></html>