Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1425493

Summary:	Vm pool auto storage domain target selection option doesn't exist in REST API
Product:	[oVirt] ovirt-engine	Reporter:	sefi litmanovich <slitmano>
Component:	RestAPI	Assignee:	Shahar Havivi <shavivi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.1.2	CC:	bugs, lveyde, tjelinek
Target Milestone:	ovirt-4.1.2	Flags:	tjelinek: ovirt-4.1? tjelinek: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+
Target Release:	4.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	With this release, when creating virtual machine pools using a template that is present in more than one storage domain, virtual machine disks can be distributed to multiple storage domains add the tag: <auto_storage_select>true</auto_storage_select> to the pool creation	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-23 08:22:43 UTC	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:
Embargoed:

Description sefi litmanovich 2017-02-21 15:00:46 UTC

Description of problem:

https://bugzilla.redhat.com/show_bug.cgi?id=1081536 adds the option, upon create vm pool from a template with disk on several SDs, to let the system automatically choose which disk to write on which SD.
The option appears in resource allocation tab of create vm pool menu.
This option doesn't exist via REST API.
I would add this as an extra variable to the vm pool POST call body, maybe <auto_storage_allocation>true<auto_storage_allocation/>.

Version-Release number of selected component (if applicable):
rhevm-4.1.1.2-0.1.el7.noarch

Comment 1 Israel Pinto 2017-05-03 10:10:01 UTC

Verify with: RHVM Version: 4.1.2-0.1.el7
Steps:
Create VM with 'auto_storage_select' flag 'ture'
<vm_pool>
    <name>vm_pool_test</name>
    <max_user_vms>1</max_user_vms>
    <prestarted_vms>0</prestarted_vms>
    <size>2</size>
    <type>automatic</type>
    <cluster id="52c5898a-0f95-471f-9790-37c697986c92"> </cluster>
    <template id="188645bd-ba75-4654-9135-ac0265f3df8e"/>
    <auto_storage_select>true</auto_storage_select>
</vm_pool>

Results:
VM pool created.

Comment 2 Israel Pinto 2017-05-03 10:10:48 UTC

(In reply to Israel Pinto from comment #1)
> Verify with: RHVM Version: 4.1.2-0.1.el7
> Steps:
> Create VM with 'auto_storage_select' flag 'true' (my mistake)
> <vm_pool>
>     <name>vm_pool_test</name>
>     <max_user_vms>1</max_user_vms>
>     <prestarted_vms>0</prestarted_vms>
>     <size>2</size>
>     <type>automatic</type>
>     <cluster id="52c5898a-0f95-471f-9790-37c697986c92"> </cluster>
>     <template id="188645bd-ba75-4654-9135-ac0265f3df8e"/>
>     <auto_storage_select>true</auto_storage_select>
> </vm_pool>
> 
> Results:
> VM pool created.