Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1363692 - [RFE] virt-v2v: Indicate source template as a template in the import dialog.
Summary: [RFE] virt-v2v: Indicate source template as a template in the import dialog.
Keywords:
Status: NEW
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.0.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On: 1363796 1363800
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-03 11:28 UTC by Nisim Simsolo
Modified: 2019-04-14 12:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Virt
michal.skrivanek: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
screenshot of import dialog, template is highlighted (deleted)
2016-08-03 11:30 UTC, Nisim Simsolo
no flags Details

Description Nisim Simsolo 2016-08-03 11:28:01 UTC
Description of problem:
Currently, when "loading" external provider, available VMs to import using webadmin import dialog, there is no difference between VM and template representation (both of this types are listed with name and checkbox only).
It would be nice to have a different indication for template, so the webadmin  can know which one is VM and which one is template.

Version-Release number of selected component (if applicable):
ovirt-engine-4.0.2.2-0.1.el7ev


Additional info:
screenshot of import dialog with template attached.

Comment 1 Nisim Simsolo 2016-08-03 11:30:16 UTC
Created attachment 1187023 [details]
screenshot of import dialog, template is highlighted


Note You need to log in before you can comment on or make changes to this bug.