<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 22, 2017 at 3:26 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On Sun, Jan 22, 2017 at 3:08 PM, Gianluca Cecchi<br>
<<a href="mailto:gianluca.cecchi@gmail.com">gianluca.cecchi@gmail.com</a>> wrote:<br>
> Il 22/Gen/2017 13:23, "Maor Lipchuk" <<a href="mailto:mlipchuk@redhat.com">mlipchuk@redhat.com</a>> ha scritto:<br>
><br>
><br>
> That is indeed the behavior.<br>
> ISO and export are only supported through mount options.<br>
><br>
><br>
> Ok<br>
><br>
><br>
> I think that the goal is to replace those types of storage domains.<br>
><br>
><br>
> In which sense/way?<br>
><br>
> For example the backup that the export storage domain is used for can be<br>
> used with a regular data storage domain since oVirt 3.6.<br>
><br>
><br>
> I have not understood ... can you detail this?</span> </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">In some future version, we can replace iso and export domain with a regular<br>
data domain.<br>
<br>
For example, iso file will be uploaded to regular volume (on file or<br>
block). When<br>
you want to attach an iso to a vm, we can activate the volume and have the vm<br>
use the path to the volume.<br>
<br>
For export domain, we would could copy the disks to regular volumes. The vm<br>
metadata will be kept in the OVF_STORE of the domain.<br>
<br>
Or, instead of export, you can download the vm to ova file, and<br>
instead of import,<br>
upload the vm from ova file.<br></blockquote><div><br></div><div><br></div><div>Here is an example how the user can migrate VMs/Templates between different Data Centers with the "import storage domain" instead of using export domain.</div><div><br></div><div><a href="https://www.youtube.com/watch?v=DLcxDB0MY38&list=PL2NsEhIoqsJFsDWYKZ0jzJba11L_-xSds&index=4">https://www.youtube.com/watch?v=DLcxDB0MY38&list=PL2NsEhIoqsJFsDWYKZ0jzJba11L_-xSds&index=4</a><br></div><div> </div><div>so this is only one feature the export storage domain is used for today that as of oVirt 3.5 can be done with any storage domain.</div><div>In the future we plan to enhance it to pre-define a certain storage domain as a backup storage domain which will have features similar to the export storage domain and more.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="gmail-"><br>
> I have available a test environment with several San LUNs and no easy way to<br>
> connect to nfs or similar external resources... how could I provide export<br>
> and iso in this case? Creating a specialized vm and exporting from there,<br>
> even if it would be a circular dependency then..? Suggestions?<br>
<br>
</span>Maybe upload image via the ui/REST?<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
Nir<br>
</font></span></blockquote></div><br></div></div>