Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1037280

Summary: meaning of "Hypervisor" field is not clear
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: web UIAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.14CC: aigao, asaha, atodorov, dcallagh, jzhao, qwan, rmancy, tools-bugs
Target Milestone: 19.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-25 07:18:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1014438    
Bug Blocks:    

Description Dan Callaghan 2013-12-03 04:24:04 UTC 
The "Hypervisor" field on the system page indicates the type of hypervisor that the system is running inside of. For a bare metal system it will be None, for a KVM guest it will be "KVM", etc.

However the meaning of the field is not clear in the web UI. In particular, "Hypervisor: None" suggests that the system does not support hardware virtualization but in fact it means that the system is not virtualized.

http://article.gmane.org/gmane.comp.systems.beaker.devel/916

Suggestions are to rename the field to "Virtualization", "Virtualized", or "Host hypervisor". Or the word "guest" could be used when displaying the field values, as in:

    Virtualization: Not virtualized
    Virtualization: KVM guest
    Virtualization: Xen guest
Comment 2 Alexander Todorov 2013-12-03 13:33:47 UTC 
(In reply to Dan Callaghan from comment #0)
> 
> Suggestions are to rename the field to "Virtualization", "Virtualized", or
> "Host hypervisor". Or the word "guest" could be used when displaying the
> field values, as in:
> 

Renaming will break all existing templates. Please add another field with more appropriate name but the same meaning (and possibly issue a deprecation warning if using the old field).
Comment 3 Dan Callaghan 2013-12-05 22:41:40 UTC 
(In reply to Alexander Todorov from comment #2)

When you say "break all existing templates" do you just mean that the new field will cause the HTML output on some pages to change, which will break any scraping scripts? I'm sorry but we don't consider the web UI to be a public API, it's not really practical for us to go through that kind of deprecation process every time we want to make a change to it.

However, I think in this case we would keep the db schema the same, it would only be a change to the wording used in the web UI. So it wouldn't affect bkr system-details.
Comment 4 Dan Callaghan 2014-09-18 06:03:20 UTC 
This is fixed as part of the system page improvements (bug 1014438). The wording is now:

Host hypervisor | (not virtualized)

for physical systems, and:

Host hypervisor | KVM

and so forth, for virtual systems.
Comment 7 Dan Callaghan 2014-11-25 07:18:37 UTC 
Beaker 19.0 has been released.