Bug 1037654 - Factors comprising host score should be configurable
Summary: Factors comprising host score should be configurable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-ha
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.0
Assignee: Greg Padgett
QA Contact: Lukas Svaty
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-03 14:45 UTC by Greg Padgett
Modified: 2016-06-12 23:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 16:51:54 UTC
oVirt Team: SLA
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0080 0 normal SHIPPED_LIVE new package: ovirt-hosted-engine-ha 2014-01-21 21:00:07 UTC
oVirt gerrit 22056 0 None None None Never

Description Greg Padgett 2013-12-03 14:45:32 UTC
Description of problem:
The factors making up the host score are currently in a constants.py file, which while it can be hacked/changed, is not clean and will get overwritten on upgrade.

It would be better for these to either live in a proper configuration file, or to at least allow overriding via a config file.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Changing the scores in constants.py (/usr/lib/python2.6/site-packages/ovirt_hosted_engine_ha/agent/) will influence the agent scores; however, it will be overwritten on upgrade.  It's also not very intuitive.

Expected results:
Score changes should survive upgrades and be done in a file under /etc.

Additional info:

Comment 1 Greg Padgett 2013-12-09 15:53:35 UTC
Merged Change-Id: If485283c133eb517c9a3036ff42d1cd962a1697d

Comment 4 errata-xmlrpc 2014-01-21 16:51:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0080.html


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