Bug 974066 - PRD33 - externalize vm level configuration values to a property file
PRD33 - externalize vm level configuration values to a property file
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.3.0
Assigned To: Roy Golan
Jiri Belka
: CodeChange, FutureFeature
Depends On:
Blocks: 1019470
  Show dependency treegraph
Reported: 2013-06-13 07:20 EDT by Itamar Heim
Modified: 2015-09-22 09 EDT (History)
10 users (show)

See Also:
Fixed In Version: is4
Doc Type: Enhancement
Doc Text:
All virtual machine operating system properties (from vdc_options and VmOsType.java enum) are now merged in one file-based repository which is external to the code. This makes it easier for administrators to extend and configure operating system information.
Story Points: ---
Clone Of:
Last Closed: 2014-01-21 12:27:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 15078 None None None Never
oVirt gerrit 15080 None None None Never
oVirt gerrit 15538 None None None Never

  None (edit)
Description Itamar Heim 2013-06-13 07:20:58 EDT
should allow adding new OSs or override defaults of predefined OSs
Comment 1 Michal Skrivanek 2013-06-14 04:39:33 EDT
the goal is to indirectly use libosinfo and external config files for OS-related config values. 
As an evolution we should have a way how to generate new property files on libosinfo update yet we also want to have/keep customizations
Comment 2 Jiri Belka 2013-07-03 09:41:04 EDT
ok, is4. for related issues following BZs were created: BZ980879, BZ980886, BZ980813.
Comment 3 Charlie 2013-11-27 19:23:10 EST
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:


Thanks in advance.
Comment 4 errata-xmlrpc 2014-01-21 12:27:18 EST
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.


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