Bug 1573413

Summary:	[RFE] Allow selecting disk allocation policy when creating a template from a VM
Product:	[oVirt] ovirt-engine	Reporter:	Eyal Shenitzky <eshenitz>
Component:	BLL.Storage	Assignee:	Eyal Shenitzky <eshenitz>
Status:	CLOSED DEFERRED	QA Contact:	Avihai <aefrat>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	bugs, lwright
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-01 14:47:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eyal Shenitzky 2018-05-01 07:01:19 UTC

Description of problem:

When creating a VM template in the UI there is no way select the template disks allocation policy.
Currently, the template disks will be created with the following rules:

QCow -> SPARSE
RAW + File -> SPARSE
RAW + Block -> PREALLOCATED

If the UI will supply this behavior the user will be able to select the specific template disks configuration.

Version-Release number of selected component (if applicable):
master-4.3.0 from commit 56af10f17ad1ed06611c99abec486fe03e91dd3e

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with disks
2. Create a template from the VM using the UI

Actual results:
There is no way to select the disks allocation policy

Expected results:
The engine should supply a way to select the disk allocation policy

Additional info:

Comment 2 Laura Wright 2019-05-30 12:57:59 UTC

Do you guys need any UX help with this issue?

Comment 3 Michal Skrivanek 2020-03-18 15:46:06 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 4 Michal Skrivanek 2020-03-18 15:50:58 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 5 Michal Skrivanek 2020-04-01 14:47:07 UTC

ok, closing. Please reopen if still relevant/you want to work on it.

Comment 6 Michal Skrivanek 2020-04-01 14:50:49 UTC

ok, closing. Please reopen if still relevant/you want to work on it.