domain types for export and iso: no fcp and no iscsi
Hello, I didn't notice before, but it seems that in 4.0.6 when I select "export" or "ISO" in Domain Function, then for Storage Type I can only select NFS, GlusterFS or POSIX compliant FS. If this is true, why this limitation? Any chance to change it, allowing FCP and iSCSI also for these kinds of domains? Thanks, Gianluca
On Sun, Jan 22, 2017 at 2:28 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, I didn't notice before, but it seems that in 4.0.6 when I select "export" or "ISO" in Domain Function, then for Storage Type I can only select NFS, GlusterFS or POSIX compliant FS. If this is true, why this limitation? Any chance to change it, allowing FCP and iSCSI also for these kinds of domains?
Hi Gianluca, That is indeed the behavior. ISO and export are only supported through mount options. I think that the goal is to replace those types of storage domains. For example the backup that the export storage domain is used for can be used with a regular data storage domain since oVirt 3.6. Yaniv, do we have any open RFEs on our future plans?
Thanks, Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Il 22/Gen/2017 13:23, "Maor Lipchuk" <mlipchuk@redhat.com> ha scritto: That is indeed the behavior. ISO and export are only supported through mount options. Ok I think that the goal is to replace those types of storage domains. In which sense/way? For example the backup that the export storage domain is used for can be used with a regular data storage domain since oVirt 3.6. I have not understood ... can you detail this? I have available a test environment with several San LUNs and no easy way to connect to nfs or similar external resources... how could I provide export and iso in this case? Creating a specialized vm and exporting from there, even if it would be a circular dependency then..? Suggestions?
On Sun, Jan 22, 2017 at 3:08 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Il 22/Gen/2017 13:23, "Maor Lipchuk" <mlipchuk@redhat.com> ha scritto:
That is indeed the behavior. ISO and export are only supported through mount options.
Ok
I think that the goal is to replace those types of storage domains.
In which sense/way?
For example the backup that the export storage domain is used for can be used with a regular data storage domain since oVirt 3.6.
I have not understood ... can you detail this?
In some future version, we can replace iso and export domain with a regular data domain. For example, iso file will be uploaded to regular volume (on file or block). When you want to attach an iso to a vm, we can activate the volume and have the vm use the path to the volume. For export domain, we would could copy the disks to regular volumes. The vm metadata will be kept in the OVF_STORE of the domain. Or, instead of export, you can download the vm to ova file, and instead of import, upload the vm from ova file.
I have available a test environment with several San LUNs and no easy way to connect to nfs or similar external resources... how could I provide export and iso in this case? Creating a specialized vm and exporting from there, even if it would be a circular dependency then..? Suggestions?
Maybe upload image via the ui/REST? Nir
On Sun, Jan 22, 2017 at 3:26 PM, Nir Soffer <nsoffer@redhat.com> wrote:
On Sun, Jan 22, 2017 at 3:08 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Il 22/Gen/2017 13:23, "Maor Lipchuk" <mlipchuk@redhat.com> ha scritto:
That is indeed the behavior. ISO and export are only supported through mount options.
Ok
I think that the goal is to replace those types of storage domains.
In which sense/way?
For example the backup that the export storage domain is used for can be used with a regular data storage domain since oVirt 3.6.
I have not understood ... can you detail this?
In some future version, we can replace iso and export domain with a regular
data domain.
For example, iso file will be uploaded to regular volume (on file or block). When you want to attach an iso to a vm, we can activate the volume and have the vm use the path to the volume.
For export domain, we would could copy the disks to regular volumes. The vm metadata will be kept in the OVF_STORE of the domain.
Or, instead of export, you can download the vm to ova file, and instead of import, upload the vm from ova file.
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. https://www.youtube.com/watch?v=DLcxDB0MY38&list=PL2NsEhIoqsJFsDWYKZ0jzJba11L_-xSds&index=4 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. 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.
I have available a test environment with several San LUNs and no easy way to connect to nfs or similar external resources... how could I provide export and iso in this case? Creating a specialized vm and exporting from there, even if it would be a circular dependency then..? Suggestions?
Maybe upload image via the ui/REST?
Nir
participants (3)
-
Gianluca Cecchi -
Maor Lipchuk -
Nir Soffer