Description of problem: [RFE][UX] provide an indication in Admin Portal that ISO domains are deprecated and Data Domains can and should now store ISOs I have had conversations with several users on the users list and Twitter that had no idea ISO domains were deprecated, or that they could / should upload ISOs to their Data Domains. We should: 1. on creation of an ISO domain, warn the user that they probably don't need an ISO domain and should use a Data domain 2. on the disks upload page, point out that ISOs work too Version-Release number of selected component (if applicable): 4.3
Sounds reasonable. I guess when creating a VM, in the CDROM images dropdown menu, there will be VM disks also ? Can't we just recreate the iso domain as data domain and somehow mark the isos , so they can be filtered during VM deployment ?
(In reply to Strahil Nikolov from comment #1) > Sounds reasonable. > I guess when creating a VM, in the CDROM images dropdown menu, there will be > VM disks also ? In VM Portal, you only see the ISOs. Should be the same in Admin Portal but I haven't tried it. Please do and let me know if it doesn't work as expected. > Can't we just recreate the iso domain as data domain and somehow mark the > isos , so they can be filtered during VM deployment ? Yes, you can create a Data Domain, and use either the UI or this tool: https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py and like I said, the filtering in the UI should just work.
(In reply to Greg Sheremeta from comment #2) > In VM Portal, you only see the ISOs. > Should be the same in Admin Portal but I haven't tried it. Please do and let > me know if it doesn't work as expected. Indeed, Admin Portal also properly filters the list of ISOs.
(In reply to Strahil Nikolov from comment #1) > Sounds reasonable. > I guess when creating a VM, in the CDROM images dropdown menu, there will be > VM disks also ? When you upload ISO file, it is stored in the data domain with ISO content type so the system will list this image in the same way ISO files on ISO storage domain are listed. The main advantage is being able to use iSCSI of FC storage for ISO domain, instead of NFS. > Can't we just recreate the iso domain as data domain and somehow mark the > isos , so they can be filtered during VM deployment ? ISO domain have some limits that data domains do not have, and special code for handling it. Creating a data domain as ISO domain will not help to avoid this unneeded complexity. I agree with Greg that we should change the UI to warn about using ISO domain and suggest to use disk upload instead.
Also, We should consider a deprecation message is printed out during usage of engine-iso-uploader.
This request is not currently committed to 4.4.z, moving it to 4.5
An info message was added when the ISO domain is created about the domain being deprecated. Steps to check: 1. from the domain window -> new domain -> content type ISO 2. after pressing OK a confirmation window should pop up with the info messege. 3. should work for all supported storage types under ISO.
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.