Open Stack

I don't think these patches are conflicting.
I will continue to work on this patch.

https://review.openstack.org/#/c/34903/


Thanks!


Best Regards


-------------------------------------------------------------------------------------------------------

Hi Arnaud,

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.

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.

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.




Best Regards
Zarric(Zhu Zhu)

From: Arnaud Legendre
Date: 2013-12-18 01:58
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][VMware] Deploy from vCenter template
Hi Qui Xing,



We are planning to address the vCenter template issue by levering the
OVF/OVA capabilities.
Kiran's implementation is tied to a specific VC and requires to add Glance
properties that are not generic.
For existing templates, the workflow will be:
. generate an *.ova tarball (containing the *.ovf descriptor + *.vmdk
stream-optimized) out of the template,
. 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,
. 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).


[1]
https://blueprints.launchpad.net/glance/+spec/vmware-datastore-storage-backend

[2] https://blueprints.launchpad.net/nova/+spec/vmware-driver-ova-support


If you have questions about [1], please send me an email. For [2], please
reach vuil.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131220/df58b271/attachment.html>