Bug 1331544

Summary:	[RFE] Implement a storage backend policy to balance new disks
Product:	[oVirt] ovirt-engine	Reporter:	nicolas
Component:	BLL.Storage	Assignee:	Yaniv Lavi <ylavi>
Status:	CLOSED WONTFIX	QA Contact:	Raz Tamir <ratamir>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.5	CC:	bperkins, bugs, dfediuck, tnisan, ylavi
Target Milestone:	---	Keywords:	FutureFeature, Improvement
Target Release:	---	Flags:	tnisan: ovirt-future? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-27 13:36:22 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:
Bug Depends On:	1539837
Bug Blocks:

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!