Bug 1530730

*** Bug 1093548 has been marked as a duplicate of this bug. ***

(Originally by Sean Cohen)

Created attachment 923963 [details]
mockup: Images sub-tab: action buttons

(Originally by ecohen)

Created attachment 923964 [details]
mockup: "Upload Image" dialog

(Originally by ecohen)

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.

(Originally by ecohen)

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.

(Originally by Sandro Bonazzola)

*** Bug 706873 has been marked as a duplicate of this bug. ***

(Originally by Allon Mureinik)

*** Bug 630655 has been marked as a duplicate of this bug. ***

(Originally by Allon Mureinik)

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.

(Originally by Allon Mureinik)

Created attachment 1005575 [details]
mock-up: Import Disk

(Originally by ecohen)

(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.

(Originally by ecohen)

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.

(Originally by tony)

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

(Originally by Waldirio Pinheiro)

Good morning

Would like to ask if are there roadmap for this feature.

Appreciate
Waldirio

(Originally by Waldirio Pinheiro)

(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.

(Originally by ylavi)

*** Bug 1091377 has been marked as a duplicate of this bug. ***

(Originally by Daniel Erez)

No qe_ack:

No feature page available for us to test this feature

(Originally by Raz Tamir)

Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

(Originally by pm-rhel)

(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.

(Originally by ylavi)

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.

(Originally by rule-engine)

Please provide doc text first.

(Originally by ylavi)

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

(Originally by Tal Nisan)

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

seems it's broken - see bug 1536826

No need to track for 4.3.
Closing.

BZ<2>Jira re-sync