+++ This bug was initially created as a clone of Bug #1091377 +++ Description of problem: It would be helpful to be able to upload iso images through the gui. Being able to add them through the hosted engine and through nfs is fine in many cases of course, but a more integrated solution into the webgui would be great. Letting users choose their own iso seems a better solution in many cases, especially if it can go under their own resource pool. First time poster, so please tell me if I'm doing anything incorrectly. With my best regards Klas --- Additional comment from Sean Cohen on 2014-07-24 09:37:32 EDT ---
*** Bug 1093548 has been marked as a duplicate of this bug. ***
Created attachment 923963 [details] mockup: Images sub-tab: action buttons
Created attachment 923964 [details] mockup: "Upload Image" dialog
graphic design is pretty straight forward IMO: - add "Upload", "Edit" (? maybe not needed) and "Remove" buttons to the "Images" sub-tab (displayed when an ISO domain is selected in the Storage main tab). [see attachment 923963 [details]] - Once "Upload" is clicked, the "Upload Image" dialog is opened. [see attachment 923964 [details]] - "Edit" opens an "Edit Image", which should be identical to the "Upload Image" dialog, with the information filled and potentially some of the fields disabled (again, probably doesn't make sense, hence not needed). - "Remove" should open a standard "are you sure" confirmation dialog.
Moving to storage: it's a change needed in the engine webadmin for importing an image in an iso domain. Doesn't look like an integration task.
*** Bug 706873 has been marked as a duplicate of this bug. ***
*** Bug 630655 has been marked as a duplicate of this bug. ***
Note to the UXD team: We want to handle bug 706873 (uploading a VM's DISK, not an ISO) as part of this effort too. This will probably require slightly different screens.
Created attachment 1005575 [details] mock-up: Import Disk
(In reply to Allon Mureinik from comment #8) > Note to the UXD team: > We want to handle bug 706873 (uploading a VM's DISK, not an ISO) as part of > this effort too. > > This will probably require slightly different screens. Thanks for the update, Allon. After discussing with Liz: It may make sense to utilize the 'Import' terminology that we are using throughout the application to represent the action of adding a pre-defined item to the system, rather than creating a 'New' one from scratch. It would probably make sense to make this action available from the Disks sub-tab of the VMs main tab as well as from the Disks main-tab [see attachment 1005575 [details]]. I am not sure if we will have (or already have) capabilities of importing a Disk from e.g. an Export domain - if we do / will, it would make sense to enable this capability from the same button/dialog, and let the user the option to choose whether he wants to Import the Disk from his local file system, from an Export domain, etc. If makes completely no sense to use the 'Import' terminology here, I guess that we can use 'Upload' instead (similarly to the action-name for the ISOs - see attachment 923963 [details]). We can also change the terminology for ISOs to 'Import' (though in ISOs, we are never creating new ones from scratch anyway, so a bit of a different case here). If you need any further UXD assistance, please feel free to further 'needinfo' us. thanks.
From the mockup images it appears as though the graphical image/iso uploader will only support NFS paths. Will http and/or smb also be an option so users can specify a path like http://$host/$file.iso or smb://$user@$host/$file.iso? It would be nice for users to be able to upload images/isos from their local machines. Supporting smb and nfs may provide a way to allow this by allowing users to create a share or export on their local machine.
Morning I was today in a customer and we was testing and comparing environments (RHEV and VMWare) and this point was very important. In VMWare the client can upload/download image, all from webui, without necessity to copy .iso file between machines for example. This will be a great feature in RHEV, the idea is just upload to ISO data store, defining the correct permission, or download if necessary, without necessity to access the server via cli. Appreciate and let me know if I can help you about it. B'Regards Waldirio
Good morning Would like to ask if are there roadmap for this feature. Appreciate Waldirio
(In reply to Waldirio M Pinheiro from comment #13) > Good morning > > Would like to ask if are there roadmap for this feature. > > Appreciate > Waldirio We are planning to add image uploader in the GUI on RHEV 4.0. ISO uploader is planned later on and requires some infra work which has already started.
*** Bug 1091377 has been marked as a duplicate of this bug. ***
No qe_ack: No feature page available for us to test this feature
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.
(In reply to Raz Tamir from comment #21) > No qe_ack: > > No feature page available for us to test this feature Please use QE Conditional NAK. Nacking means you are not willing to test and it closes the ticket.
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Please provide doc text first.
In order to create an ISO disk container via the REST-API the following should be specified within the request: <disk> .... <content_type>iso</content_type> .... </disk> When the disk exists on an active storage domain in the data center it can be attached to the VM as a CDROM device via the REST-API by sending a POST request to: ....ovirt-engine/api/vms/{vm-id}/cdroms With the content: <cdrom> <file id="{disk-id}"/> </cdrom> Where {disk-id} is the ID of the ISO disk created
Verified with the following code: -------------------------------------- ovirt-engine-4.2.2.1-0.1.el7.noarch vdsm-4.20.19-1.el7ev.x86_64 Verified with the following scenario: --------------------------------------- Verified with Tier1 for the upload iso part and by verification of https://bugzilla.redhat.com/show_bug.cgi?id=1536826 Moving to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1488
BZ<2>Jira Resync
Hi This does not solve the problem for 'Boot Options' where I can specify a kernel and initrd using iso:// style path This will become more of an issue when booting up RH coreos using ignite config. To automate this we would need to be able to pass kernel params pointing at bios or uefi image and .ign config At the moment I cannot upload a kernel image and initrd to the ISO Domain via rest or the web UI. Thanks Phil
To add on to what Phil said, if the kernel/initrd were uploaded to a "data" domain, the VMs can't boot from them.