<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE>
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
DIV.FoxDiv20131219143908185538 {
COLOR: #000000
}
P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
LINE-HEIGHT: 1.5; FONT-FAMILY: 微软雅黑; COLOR: #000000; FONT-SIZE: 10.5pt
}
</STYLE>
<META name=GENERATOR content="MSHTML 8.00.7601.18305"></HEAD>
<BODY style="MARGIN: 10px">
<DIV>
<DIV>Hi Arnaud, </DIV>
<DIV> </DIV>
<DIV>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. <SPAN lang=en class=short_text><SPAN
class=hps>OVA would be a good choice which will benefit users by
avoiding only use flat image limited from current driver. </SPAN></SPAN></DIV>
<DIV><SPAN lang=en class=short_text><SPAN class=hps></SPAN></SPAN> </DIV>
<DIV><SPAN lang=en class=short_text><SPAN class=hps></SPAN></SPAN>But in my
opinion, it may not conflict <SPAN id=result_box lang=en class=short_text><SPAN
class=hps>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. </SPAN></SPAN></DIV>
<DIV><SPAN lang=en class=short_text><SPAN class=hps></SPAN></SPAN><SPAN lang=en
class=short_text><SPAN class=hps></SPAN></SPAN> </DIV>
<DIV><SPAN lang=en class=short_text><SPAN class=hps>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. </SPAN></SPAN></DIV></DIV>
<DIV> </DIV>
<HR style="WIDTH: 210px; HEIGHT: 1px" align=left color=#b5c4df SIZE=1>
<DIV><SPAN>
<DIV style="FONT-FAMILY: verdana; FONT-SIZE: 10pt">
<DIV>Best Regards<BR>Zarric(Zhu Zhu)</DIV></DIV></SPAN></DIV>
<DIV> </DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV
style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; FONT-FAMILY: tahoma; BACKGROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B> <A href="mailto:alegendre@vmware.com">Arnaud
Legendre</A></DIV>
<DIV><B>Date:</B> 2013-12-18 01:58</DIV>
<DIV><B>To:</B> <A
href="mailto:openstack-dev@lists.openstack.org">OpenStack Development Mailing
List (not for usage questions)</A></DIV>
<DIV><B>Subject:</B> Re: [openstack-dev] [Nova][VMware] Deploy from vCenter
template</DIV></DIV></DIV>
<DIV>
<DIV style="BACKGROUND-COLOR: white" class=FoxDiv20131219143908185538>
<DIV
style="FONT-FAMILY: times new roman, new york, times, serif; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>Hi Qui Xing,<BR></DIV>
<DIV><BR></DIV>
<DIV>We are planning to address the vCenter template issue by levering the
OVF/OVA capabilities.</DIV>
<DIV>Kiran's implementation is tied to a specific VC and requires to add Glance
properties that are not generic.</DIV>
<DIV>For existing templates, the workflow will be:</DIV>
<DIV>. generate an *.ova tarball (containing the *.ovf descriptor + *.vmdk
stream-optimized) out of the template,</DIV>
<DIV>. 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,</DIV>
<DIV>. 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).</DIV>
<DIV><BR></DIV>
<DIV>[1] <A
href="https://blueprints.launchpad.net/glance/+spec/vmware-datastore-storage-backend"
data-mce-href="https://blueprints.launchpad.net/glance/+spec/vmware-datastore-storage-backend">https://blueprints.launchpad.net/glance/+spec/vmware-datastore-storage-backend</A></DIV>
<DIV>[2] <A
href="https://blueprints.launchpad.net/nova/+spec/vmware-driver-ova-support"
data-mce-href="https://blueprints.launchpad.net/nova/+spec/vmware-driver-ova-support">https://blueprints.launchpad.net/nova/+spec/vmware-driver-ova-support</A> </DIV>
<DIV><BR></DIV>
<DIV>If you have questions about [1], please send me an email. For [2], please
reach vuil.</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>Thanks,</DIV>
<DIV>Arnaud</DIV>
<DIV><BR></DIV>
<HR id=zwchr>
<DIV
style="FONT-STYLE: normal; FONT-FAMILY: Helvetica,Arial,sans-serif; COLOR: #000; FONT-SIZE: 12pt; FONT-WEIGHT: normal; TEXT-DECORATION: none"><B>From:
</B>"Shawn Hartsock" <hartsock@acm.org><BR><B>To: </B>"OpenStack
Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org><BR><B>Sent: </B>Monday, December 16,
2013 9:37:34 AM<BR><B>Subject: </B>Re: [openstack-dev] [Nova][VMware] Deploy
from vCenter template<BR>
<DIV><BR></DIV>
<DIV dir=ltr>IIRC someone who shows up at <A
href="https://urldefense.proofpoint.com/v1/url?u=https://wiki.openstack.org/wiki/Meetings/VMwareAPI%23Meetings&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=5wWaXo2oVaivfKLCMyU6Z9UTO8HOfeGCzbGHAT4gZpo%3D%0A&m=KCBtvBVSZCslDQrTvSEqBcTEcx%2FSKxtF0ZRIjtTFmSw%3D%0A&s=b7e206823086d30592a77473b7f3b587d73ad46a8ee1f6ecc18d68207af55180"
target=_blank>https://wiki.openstack.org/wiki/Meetings/VMwareAPI#Meetings</A> is
planning on working on that again for Icehouse-3 but there's some new debate on
the best way to implement the desired effect. The goal of that change would be
to avoid streaming the disk image out of vCenter for the purpose of then
streaming the same image back into the same vCenter. That's really inefficient.
<DIV><BR></DIV>
<DIV>So there's a Nova level change that could happen (that's the patch you saw)
and there's a Glance level change that could happen, and there's a combination
of both approaches that could happen.</DIV>
<DIV><BR></DIV>
<DIV>If you want to discuss it informally with the group that's looking into the
problem I could probably make sure you end up talking to the right people on
#openstack-vmware or if you pop into the weekly team meeting on IRC you could
mention it during open discussion time.</DIV></DIV>
<DIV class=gmail_extra><BR>
<DIV><BR></DIV>
<DIV class=gmail_quote>On Mon, Dec 16, 2013 at 3:27 AM, Qing Xin Meng <SPAN
dir=ltr><<A href="mailto:mengqxqx@cn.ibm.com"
target=_blank>mengqxqx@cn.ibm.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<P><SPAN style="FONT-FAMILY: sans-serif"
data-mce-style="font-family: sans-serif;" face="sans-serif">I saw a commit for
Deploying from VMware vCenter template and found it's abandoned.</SPAN><BR><A
href="https://urldefense.proofpoint.com/v1/url?u=https://review.openstack.org/%23/c/34903&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=5wWaXo2oVaivfKLCMyU6Z9UTO8HOfeGCzbGHAT4gZpo%3D%0A&m=KCBtvBVSZCslDQrTvSEqBcTEcx%2FSKxtF0ZRIjtTFmSw%3D%0A&s=950e963bf15d7e752c98f67e9706262a1ae4756c7218d7ac7741db4367ba456b"
target=_blank><SPAN
style="FONT-FAMILY: serif; COLOR: #0000ff; FONT-SIZE: medium"
data-mce-style="color: #0000ff; font-family: serif; font-size: medium;"
face="serif" color="#0000FF" size="3"><SPAN style="TEXT-DECORATION: underline"
data-mce-style="text-decoration: underline;">https://review.openstack.org/#/c/34903</SPAN></SPAN></A><SPAN
style="FONT-FAMILY: serif; FONT-SIZE: medium"
data-mce-style="font-family: serif; font-size: medium;" face="serif"
size="3"> </SPAN><BR><BR><SPAN style="FONT-FAMILY: sans-serif"
data-mce-style="font-family: sans-serif;" face="sans-serif">Anyone knows the
plan to support the deployment from VMware vCenter
template?</SPAN><BR><BR><BR><SPAN style="FONT-FAMILY: sans-serif"
data-mce-style="font-family: sans-serif;"
face="sans-serif">Thanks!</SPAN><BR><SPAN style="FONT-FAMILY: sans-serif"
data-mce-style="font-family: sans-serif;" face="sans-serif"><BR><BR><BR>Best
Regards</SPAN></P></DIV><BR>_______________________________________________<BR>OpenStack-dev
mailing list<BR><A href="mailto:OpenStack-dev@lists.openstack.org"
target=_blank>OpenStack-dev@lists.openstack.org</A><BR><A
href="https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=5wWaXo2oVaivfKLCMyU6Z9UTO8HOfeGCzbGHAT4gZpo%3D%0A&m=KCBtvBVSZCslDQrTvSEqBcTEcx%2FSKxtF0ZRIjtTFmSw%3D%0A&s=f45fbe293564be6a16c90b0125534e5e62f7505fea9f92708b72aa60e5e1dc5f"
target=_blank>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</A><BR><BR></BLOCKQUOTE></DIV><BR><BR
clear=all>
<DIV><BR></DIV>-- <BR>
<DIV dir=ltr># Shawn.Hartsock - twitter: @hartsock - <A
href="https://urldefense.proofpoint.com/v1/url?u=http://plus.google.com/%2BShawnHartsock&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=5wWaXo2oVaivfKLCMyU6Z9UTO8HOfeGCzbGHAT4gZpo%3D%0A&m=KCBtvBVSZCslDQrTvSEqBcTEcx%2FSKxtF0ZRIjtTFmSw%3D%0A&s=4fecd32ebc04b37ea93dc11177b2b8cffa24fe09368d825faf8abca0594d8e7a"
target=_blank>plus.google.com/+ShawnHartsock</A> <BR></DIV></DIV><BR>_______________________________________________<BR>OpenStack-dev
mailing
list<BR>OpenStack-dev@lists.openstack.org<BR>https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=5wWaXo2oVaivfKLCMyU6Z9UTO8HOfeGCzbGHAT4gZpo%3D%0A&m=KCBtvBVSZCslDQrTvSEqBcTEcx%2FSKxtF0ZRIjtTFmSw%3D%0A&s=f45fbe293564be6a16c90b0125534e5e62f7505fea9f92708b72aa60e5e1dc5f<BR></DIV>
<DIV><BR></DIV></DIV></DIV></DIV></BODY></HTML>