<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 14, 2017 at 2:04 PM, Richard W.M. Jones <span dir="ltr"><<a href="mailto:rjones@redhat.com" target="_blank">rjones@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">As you may know virt-v2v can use the Export Storage Domain (ESD) to<br>
upload converted virtual machines to oVirt. It was brought to my<br>
attention yesterday that the ESD feature is being dropped, so this<br>
will no longer work at some point in the future. (BTW I would<br>
appreciate notice if you're going to drop major features that we rely on.)<br></blockquote><div><br></div><div>It caught me by surprise as well while discussing [1].</div><div>Allon, has it been shared publicly? if not, can we publicly discuss the high level design and goals of this effort?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Although virt-v2v can still work via the GUI, this isn't really<br>
suitable for bulk, scripted upload of hundreds or thousands of VMs.<br></blockquote><div><br></div><div>We now enable triggering that process also via REST-API (this is mostly intended for importing from VMware using ManageIQ, which is expected to be available soon).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
The ESD method was never very good. It was sort of an undocumented<br>
back door into oVirt, and it was slow, and still required manual<br>
intervention (after virt-v2v had done its job, you still needed to go<br>
through the GUI and import the guests into the Data Domain).<br>
<br>
What we really need is a fully scripted method to upload VMs --<br>
metadata and disk images -- to oVirt. Maybe one exists already? If<br>
not, what's the best way to do this?<br>
<br></blockquote><div><br></div><div>So besides using the REST-API mentioned above, we may be able to deliver some of the stuff described in [1] before dropping the export domain. With that, we can think of generating an oVirt-compatible OVA as an output of virt-v2v that can be consumed in a similar way to how VMs in the export domain used to be consumed.</div><div><br></div><div>Other than that, there is a rumor about introucing a backup-data-domain. Hopefully, that plan will also be shared publicly and we'll know more details about it. If it will be close in concept to the export domain, we may be able to replace the export domain with that domain in virt-v2v.</div><div><br></div><div>[1] <a href="http://www.ovirt.org/develop/release-management/features/virt/enhance-import-export-with-ova/">http://www.ovirt.org/develop/release-management/features/virt/enhance-import-export-with-ova/</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
Rich.<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
--<br>
Richard Jones, Virtualization Group, Red Hat <a href="http://people.redhat.com/~rjones" rel="noreferrer" target="_blank">http://people.redhat.com/~<wbr>rjones</a><br>
Read my programming and virtualization blog: <a href="http://rwmj.wordpress.com" rel="noreferrer" target="_blank">http://rwmj.wordpress.com</a><br>
libguestfs lets you edit virtual machines. Supports shell scripting,<br>
bindings from many languages. <a href="http://libguestfs.org" rel="noreferrer" target="_blank">http://libguestfs.org</a><br>
</font></span></blockquote></div><br></div></div>