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 1129251

Summary: [RFE] [RHEV] storage load balancing when creating VM from template
Product: Red Hat Enterprise Virtualization Manager Reporter: Evgheni Dereveanchin <ederevea>
Component: RFEsAssignee: Rob Young <royoung>
Status: NEW --- QA Contact: Shai Revivo <srevivo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: jspanko, lpeer, michal.skrivanek, moddi, mtessun, obockows, ppostler, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: sherold: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Evgheni Dereveanchin 2014-08-12 11:57:34 UTC
Description of problem:
At the moment it is possible to clone a VM template to multiple Storage Domains. When creating a VM from template using the API without specifying the storage domain, it will be implicitly stored on the original Storage Domain where the template was created. This RFE is to enable storage load balancing when creating VMs from templates, so that the least used SD (in free space percentage) is selected to provision the VM when no destination SD is selected explicitly and template is copied to multiple SDs

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

How reproducible:
Always

Steps to Reproduce:
1. create VM template on SD1
2. clone template to SD2
3. create VM using the API without specifying the destination SD

Actual results:
VM disks always placed on SD1

Expected results:
VM disks created on the SD with more free space at the moment