Bug 1242856 - [RFE] Allow default order of allocation policy for new disks
Summary: [RFE] Allow default order of allocation policy for new disks
Keywords:
Status: CLOSED DUPLICATE of bug 1188651
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-config
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.6.0
Assignee: Tal Nisan
QA Contact: Pavel Stehlik
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-14 09:30 UTC by Jiri Belka
Modified: 2016-02-10 19:44 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-07-21 22:29:58 UTC
oVirt Team: Storage
Embargoed:


Attachments (Terms of Use)

Description Jiri Belka 2015-07-14 09:30:45 UTC
Description of problem:

New disk dialog has allocation policy sorted alphabetically, thus it causes 'preallocated' to be used by default. this could be annoying as each disk would use "full" size and there are also snapshots involved...

It would be nice to redefine order of policies.

Version-Release number of selected component (if applicable):
3.6

How reproducible:


Steps to Reproduce:
1. allow to redefine order of allocation policy for new disks
2.
3.

Actual results:
not possible, it seems to be hardcoded

Expected results:
should be possible

Additional info:
getVolumeType().setSelectedItem(storageType.isBlockDomain() ? VolumeType.Preallocated : VolumeType.Sparse);

Comment 1 Allon Mureinik 2015-07-16 09:12:27 UTC
I think a whole mechanism to configure the order of options is a tad overkill, but I agree the the default should be sparse/thin. 

Yaniv - your two cents?

Comment 2 Yaniv Lavi 2015-07-21 22:29:58 UTC
(In reply to Allon Mureinik from comment #1)
> I think a whole mechanism to configure the order of options is a tad
> overkill, but I agree the the default should be sparse/thin. 
> 
> Yaniv - your two cents?

It is and is a dup of BZ 1188651

*** This bug has been marked as a duplicate of bug 1188651 ***


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