Bug 1331544 - [RFE] Implement a storage backend policy to balance new disks
Summary: [RFE] Implement a storage backend policy to balance new disks
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 3.6.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Yaniv Lavi
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On: 1539837
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 18:30 UTC by nicolas
Modified: 2018-05-27 13:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-27 13:36:22 UTC
oVirt Team: Storage
Embargoed:
tnisan: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

Description nicolas 2016-04-28 18:30:53 UTC 
Description of problem:

It would be nice if a storage backend policy could be implemented at least in the User panel. We grant privileges to students so they can create their own VMs, and regarding to new disks (when not deploying from a template), they usually leave the storage backend as the default one that appears, resulting in the first backend full in a short time and the rest of them (3 in our case) almost empty.

A configurable policy could be implemented so admins could choose between:

* Let users choose the storage backend themselves
* Enforce balanced policy

This last option could then be based on: storage with most available space, storage with least response time, ...
Comment 2 Doron Fediuck 2018-05-27 13:36:22 UTC 
Closing old RFEs.
If relevant, please re-open and explain why.
As always- patches are welcomed!
Note You need to log in before you can comment on or make changes to this bug.