<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 15, 2017 at 10:43 AM, Eduardo Mayoral <span dir="ltr"><<a href="mailto:emayoral@arsys.es" target="_blank">emayoral@arsys.es</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>As a user I must say this is a very welcome feature. I appreciate
a lot that oVirt already makes it very easy to import VMs from
VMWare .</p>
<p>Allowing to export oVirt machines in OVA format, which as of
today is the "lingua franca" of VM migrations offers a nice and
clear path out of oVirt. Having an easy way to migrate out of
oVirt makes me MORE likely to keep on using oVirt, not less.<br></p></div></blockquote><div><br></div><div>There is some confusion around the OVA format that I'd like to clarify. OVA is a very flexible format, in the sense that it's essentially an XML to describe the VM, but the content within may be (and practically is) whatever one feels like. A concrete example is a NIC - it can be (in VMware's case) a vmxnet3 and in our case virtio-net driver. So the fact there's a single XML that describes a VM has absolutely no assurance of an interchangeability. </div><div>oVirt, via virt-v2v integration, took the additional step to actually perform a conversion from VMware format and drivers and specs to KVM and oVirt.</div><div><br></div><div>The other way is left as an exercise for the reader, I'm afraid.</div><div><br></div><div>The goal of this feature, among others, is to more easily share VMs and templates between setups for example.</div><div>Y.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><p>
</p>
<pre class="m_-3579097611157925313moz-signature" cols="72">Eduardo Mayoral Jimeno (<a class="m_-3579097611157925313moz-txt-link-abbreviated" href="mailto:emayoral@arsys.es" target="_blank">emayoral@arsys.es</a>)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
<a href="tel:+34%20941%2062%2001%2045" value="+34941620145" target="_blank">+34 941 620 145 ext. 5153</a></pre><div><div class="h5">
<div class="m_-3579097611157925313moz-cite-prefix">On 14/05/17 15:56, Arik Hadas wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">Hi everyone,
<div><br>
</div>
<div>We would like to share our plan for extending the currently
provided support for OVA files with:</div>
<div>1. Support for uploading OVA.<br>
</div>
<div>2. Support for exporting a VM/template as OVA.</div>
<div>3. Support for importing OVA that was generated by oVirt
(today, we only support those that are VMware-compatible).</div>
<div>4. Support for downloading OVA.</div>
<div><br>
</div>
<div>This can be found on the <a href="http://www.ovirt.org/develop/release-management/features/virt/enhance-import-export-with-ova/" target="_blank">feature
page</a>.</div>
<div><br>
</div>
<div>Your feedback and cooperation will be highly appreciated.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Arik</div>
<div><br>
</div>
</div>
<br>
<fieldset class="m_-3579097611157925313mimeAttachmentHeader"></fieldset>
<br>
</div></div><pre>______________________________<wbr>_________________
Users mailing list
<a class="m_-3579097611157925313moz-txt-link-abbreviated" href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>
<a class="m_-3579097611157925313moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>