Description of problem: in 3.3 we adding the ability to add user-defined OSs to the engine. Reports on vm os type will end with up with new entries without the actual name of the OS, as kept in the engine. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: DWH keeps its own translation based on the VmOsType enum and won't have any info on new OSs Expected results: DWH will be able to read the mapping from the engine db. The data will relay in a dedicated dwh_osinfo table. Additional info:
This is a documentation bug. We need to add a guide to adding new OSs to the history database. Zac, which component to move this to? Yaniv
resetting this bug to the engine Yaniv I cloned one for the DWH
what happens if user adds an OS, then removes it? or adds an OS, then removes it, then adds another OS with same ID? how will localization be handled? do we even support using OsInfo by customers in 3.3 before we used it ourselves for a version and are sure we thought through all the upgrade issues on customer changes?
A short explanation about this issue: Since in 3.3 a customer can add a guest OS on his own, And the list is currently is hardcoded in the history DB, than we need a mechanism to collect the other guest OSs. It needs to be dynamic. So there are 2 bugs: - this virt bug - that is on the backend that should create a table (dwh_osinfo) that needs to be refreshed every engine restart. - Bug 985346 (on dwh) - to collect data from the dwh_osinfo (only on refresh) Hence moving this bug back to virt.
Please provide status update. Yaniv
Yaniv its pending long ago your review in gerrit, after the comment to add an entry in dwh_history_timekeeping
(In reply to Yaniv Dary from comment #1) > This is a documentation bug. We need to add a guide to adding new OSs to the > history database. Zac, which component to move this to? > > > > Yaniv I am sorry about the extreme lateness of this reply; it bypassed my inbox entirely. This bug impacts http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Enterprise_Virtualization/3.2/html/Administration_Guide/chap-Reports_History_Database_Reports_and_Dashboards.html, to begin with. If we want to add a section detailing how to add a new OS to the history database, I'll need more information about the feature before I can determine which book it should be added to.
Verified on is15. Added this entry in a new .properties file under /etc/ovirt-engine/osinfo.conf.d: os.ilanit.id.value = 2000 os.ilanit.name.value = Ilanit os.ilanit.derivedFrom.value = other os.ilanit.description.value = General user defined OS os.ilanit.family.value = user defined os.ilanit.devices.audio.value = ac97
Closing - RHEV 3.3 Released