Bug 1073764 - No new parameters like 'HostsInReserve' for power saving cluster policy in REST
Summary: No new parameters like 'HostsInReserve' for power saving cluster policy in REST
Keywords:
Status: CLOSED DUPLICATE of bug 1071872
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-restapi
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-07 06:26 UTC by Artyom
Modified: 2014-03-07 08:31 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-07 08:31:23 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Artyom 2014-03-07 06:26:25 UTC
Description of problem:
No new parameters like 'HostsInReserve' for power saving cluster policy in REST

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

How reproducible:
Always

Steps to Reproduce:
1. Change cluster policy to power saving and add new parameter(for example 'EnableAutomaticHostPowerManagement')
2.
3.

Actual results:
No new parameter appear in REST under cluster policy

Expected results:
Parameter appear with correct value, for example:
<scheduling_policy>
<policy>power_saving</policy>
<thresholds low="20" high="80" duration="120"/>
<hosts_in_reserve>3</hosts_in_reserve>
<enable_automatic_host_power_management>true</enable_automatic_host_power_management>
</scheduling_policy>

Additional info:
Effected parameter 'HostsInReserve', 'EnableAutomaticHostPowerManagement' and 'ScaleDown'.
Also I can't add 'ScaleDown' parameter, when I create new cluster policy, no matter what balance function I choose, so how I understand this parameter not connect to any balance functions, so why I can add it, under PowerSaving or EvenDistribution when I choose cluster policy?

Comment 1 Juan Hernández 2014-03-07 08:31:23 UTC
None of the new properties of the scheduling policies is currently available in the API. Not exactly the same consequence, but the root cause is the same that in bug 1071872, so I'm closing this one as duplicate.

*** This bug has been marked as a duplicate of bug 1071872 ***


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