2:54 a.m.
Hi,
I noticed that if I create a directory in root of ISO domain and put an
image in it, you can see it in admin portal image list (listed as
"foo/bar.iso"), but mounting that iso in a VM ("change CD") fails
"Error while executing action Change CD: Drive image file could not be
found"
I can easily reproduce this behaviour in ovirt 4.2.8 and rhv 4.2.7.
Is it a bug?
Cheers,
gc
11:14 a.m.
Il giorno mer 30 gen 2019 alle ore 10:02 Giulio Casella <giulio(a)di.unimi.it>
ha scritto:
Hi,
I noticed that if I create a directory in root of ISO domain and put an
image in it, you can see it in admin portal image list (listed as
"foo/bar.iso"), but mounting that iso in a VM ("change CD") fails
"Error while executing action Change CD: Drive image file could not be
found"
I can easily reproduce this behaviour in ovirt 4.2.8 and rhv 4.2.7.
Is it a bug?
As far as I can tell, there are no tools that creates subdirectories within
storage domains.
Did you manually upload the iso into the nfs mount creating a subdirectory
there?
I think this layout is not supported at all.
Cheers,
gc
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WRVLT542RUQ...
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
2:20 a.m.
Il 31/01/2019 18:14, Sandro Bonazzola ha scritto:
As far as I can tell, there are no tools that creates subdirectories
within storage domains.
Did you manually upload the iso into the nfs mount creating a
subdirectory there?
I think this layout is not supported at all.
Yes, I did (sorry :-)). My ISOs are growing, and I'd like to have a
hierarchical structure.
To say the truth it was only a test, I wasn't sure to see ISOs in
subdir. But when I've seen them (correctly listed in admin portal as
"foo/bar.iso"), I'd expect to be able mount them.
I also filed a bug
(https://bugzilla.redhat.com/show_bug.cgi?id=1671046), if the answer
will be NOTABUG, I'll try with a RFE.
Thanks,
gc
TL;DR
The scenario I'm trying to implement is a DVD video store, provided by
images in ISO domain, automatically mounted on VM on demand, via a
backend python script. That's why in this case a hyerarchical structure
would be much better than a flat one.
5:12 a.m.
On Fri, Feb 1, 2019 at 3:22 AM Giulio Casella <giulio(a)di.unimi.it> wrote:
Il 31/01/2019 18:14, Sandro Bonazzola ha scritto:
> As far as I can tell, there are no tools that creates subdirectories
> within storage domains.
> Did you manually upload the iso into the nfs mount creating a
> subdirectory there?
> I think this layout is not supported at all.
Yes, I did (sorry :-)). My ISOs are growing, and I'd like to have a
hierarchical structure.
To say the truth it was only a test, I wasn't sure to see ISOs in
subdir. But when I've seen them (correctly listed in admin portal as
"foo/bar.iso"), I'd expect to be able mount them.
Fair point. But I think editing ISOs directly like this was never really
supported.
I also filed a bug
(https://bugzilla.redhat.com/show_bug.cgi?id=1671046), if the answer
will be NOTABUG, I'll try with a RFE.
ISO domains are deprecated, so my guess is it will be closed.
And storage domains aren't intended for the user to edit manually.
Perhaps the best way for you to organize is to make a few separate storage
domains for your subsets of ISOs.
windows_domain - win7.iso
windows_domain - win81.iso
el_domain - centos7.iso
el_domain - rhel7.iso
etc
Best wishes,
Greg
Thanks,
gc
TL;DR
The scenario I'm trying to implement is a DVD video store, provided by
images in ISO domain, automatically mounted on VM on demand, via a
backend python script. That's why in this case a hyerarchical structure
would be much better than a flat one.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HRTTZSKLMNI...
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>
5:46 a.m.
Il 01/02/2019 12:12, Greg Sheremeta ha scritto:
ISO domains are deprecated, so my guess is it will be closed.
And storage domains aren't intended for the user to edit manually.
Perhaps the best way for you to organize is to make a few separate
storage domains for your subsets of ISOs.
windows_domain - win7.iso
windows_domain - win81.iso
el_domain - centos7.iso
el_domain - rhel7.iso
This could be a (partially satisfying solution), but I can have only one
storage domain for ISOs, right?
AFAIK you can have one ISO domain, one export domain and many data
domains; "engine-iso-uploader list" reports only ISO domain.
6:19 a.m.
On Fri, Feb 1, 2019 at 12:47 PM Giulio Casella <giulio(a)di.unimi.it> wrote:
This could be a (partially satisfying solution), but I can have only one
storage domain for ISOs, right?
AFAIK you can have one ISO domain, one export domain and many data
domains; "engine-iso-uploader list" reports only ISO domain.
You can have only one iso domain attached (and so active) at a time. But
you can have many iso domains defined.
And the same domain can be defined across different domains
The same applies to export domains. When you select "Attach Export" button
in Computers -> Datacenters -> MyDc you get a list of defined export domain
among which to select the one to attach, in case you have more than one
defined.
Gianluca
6:20 a.m.
On Fri, Feb 1, 2019 at 1:19 PM Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Fri, Feb 1, 2019 at 12:47 PM Giulio Casella
<giulio(a)di.unimi.it> wrote:
>
> This could be a (partially satisfying solution), but I can have only one
> storage domain for ISOs, right?
> AFAIK you can have one ISO domain, one export domain and many data
> domains; "engine-iso-uploader list" reports only ISO domain.
>
>
You can have only one iso domain attached (and so active) at a time. But
you can have many iso domains defined.
And the same domain can be defined across different domains
Meant to be: the same iso domain can be defined across different DCs.
The same applies to export domains. When you select "Attach
Export" button
in Computers -> Datacenters -> MyDc you get a list of defined export domain
among which to select the one to attach, in case you have more than one
defined.
Gianluca
6:25 a.m.
Il 01/02/2019 13:19, Gianluca Cecchi ha scritto:
On Fri, Feb 1, 2019 at 12:47 PM Giulio Casella
<giulio(a)di.unimi.it
<mailto:giulio@di.unimi.it>> wrote:
This could be a (partially satisfying solution), but I can have only one
storage domain for ISOs, right?
AFAIK you can have one ISO domain, one export domain and many data
domains; "engine-iso-uploader list" reports only ISO domain.
You can have only one iso domain attached (and so active) at a time. But
you can have many iso domains defined.
And the same domain can be defined across different domains
The same applies to export domains. When you select "Attach Export"
button in Computers -> Datacenters -> MyDc you get a list of defined
export domain among which to select the one to attach, in case you have
more than one defined.
Correct. So the solution to use more than one ISO domain to logically
organize groups of ISOs cannot be accomplished, I'd like to see all my
ISOs at the same time.
That's why I think subfolders could be a nice enhancement for ISO
storage domains.
Cheers,
gc
9:10 a.m.
On Fri, Feb 1, 2019 at 7:25 AM Giulio Casella <giulio(a)di.unimi.it> wrote:
Il 01/02/2019 13:19, Gianluca Cecchi ha scritto:
> On Fri, Feb 1, 2019 at 12:47 PM Giulio Casella <giulio(a)di.unimi.it
> <mailto:giulio@di.unimi.it>> wrote:
>
>
> This could be a (partially satisfying solution), but I can have only
one
> storage domain for ISOs, right?
> AFAIK you can have one ISO domain, one export domain and many data
> domains; "engine-iso-uploader list" reports only ISO domain.
>
>
> You can have only one iso domain attached (and so active) at a time. But
> you can have many iso domains defined.
> And the same domain can be defined across different domains
> The same applies to export domains. When you select "Attach Export"
> button in Computers -> Datacenters -> MyDc you get a list of defined
> export domain among which to select the one to attach, in case you have
> more than one defined.
Correct. So the solution to use more than one ISO domain to logically
organize groups of ISOs cannot be accomplished, I'd like to see all my
ISOs at the same time.
That's why I think subfolders could be a nice enhancement for ISO
storage domains.
The confusion is that ISO Storage Domains are now deprecated. Use Data
Domains (upload ISOs *and* disks to the same Data Domain in the UI) and
make as many of them as you want :) )
"""
Uploading Images to a Data Storage Domain
You can upload virtual disk images and ISO images to your data storage
domain in the Administration Portal
"""
https://ovirt.org/documentation/admin-guide/chap-Storage.html#uploading-i...
Greg
Cheers,
gc
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>
4:21 p.m.
On Fri, Feb 1, 2019 at 10:21 AM Giulio Casella <giulio(a)di.unimi.it> wrote:
Il 31/01/2019 18:14, Sandro Bonazzola ha scritto:
> As far as I can tell, there are no tools that creates subdirectories
> within storage domains.
> Did you manually upload the iso into the nfs mount creating a
> subdirectory there?
> I think this layout is not supported at all.
Yes, I did (sorry :-)). My ISOs are growing, and I'd like to have a
hierarchical structure.
To say the truth it was only a test, I wasn't sure to see ISOs in
subdir. But when I've seen them (correctly listed in admin portal as
"foo/bar.iso"), I'd expect to be able mount them.
I also filed a bug
(https://bugzilla.redhat.com/show_bug.cgi?id=1671046), if the answer
will be NOTABUG, I'll try with a RFE.
Vdsm list iso files in subdirectories, and should be able to use them when
starting vms. I don't know about engine side, but this may be a regression
in 4.2, which made major changes in the way vm are started.
You can try to create a 4.1 cluster and see if this works there. If you
don't
need any of the features added in 4.2 cluster version, using 4.1 cluster
version may be good enough.
But note that ISO domains are deprecated and will be removed in future
versions. Mostly likely 4.4 will not have them.
Thanks,
gc
TL;DR
The scenario I'm trying to implement is a DVD video store, provided by
images in ISO domain, automatically mounted on VM on demand, via a
backend python script. That's why in this case a hyerarchical structure
would be much better than a flat one.
I would like to hear more about this use case.
Why do you need to start a vm connected to iso file in a DVD store?
Nir
1909
days inactive
1911
days old
9 comments
5 participants
participants (5)
-
Gianluca Cecchi -
Giulio Casella -
Greg Sheremeta -
Nir Soffer -
Sandro Bonazzola