Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1195167 - vmpool collection lacks most vm properties
vmpool collection lacks most vm properties
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.5.0
Unspecified Unspecified
high Severity medium
: ovirt-3.6.0-rc
: 3.6.0
Assigned To: Shmuel Melamud
sefi litmanovich
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-02-23 05:01 EST by sefi litmanovich
Modified: 2016-04-19 21:36 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Previously, the REST API for virtual machine pools creation was limited. Now, the REST API for virtual machine pools creation has been extended to enable configuration of all virtual machine properties on pool level.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-19 21:36:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 38755 master MERGED restapi: Add VM parameters to VmPool collection Never

  None (edit)
Description sefi litmanovich 2015-02-23 05:01:59 EST
Description of problem:

Currently in api vmpool collection doesn't support the majority of vm parameters.
currently parameters available for vmpool are:

<name>vmpool.cluster.id|name</name>
<name>vmpool.template.id|name</name>
<name>vmpool.name</name>
<name>vmpool.comment</name>
<name>vmpool.size</name>
<name>vmpool.max_user_vms</name>
<name>vmpool.display.proxy</name>
<name>vmpool.description</name>

In contrary, in the webadmin-ui when adding a pool one does have all the properties that a vm has available to define already on pool level.
This means creating a preconfigured vm pool automatically is basically impossible.

I would suggest to add the same properties of a vm/template to enable further changes of the template used for the pool on the pool level.


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

rhevm 3.5 =<

How reproducible:

always
Comment 1 sefi litmanovich 2015-05-11 04:49:31 EDT
verified with ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764.el6.noarch

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