[Beaker-devel] Reorganising the system page

Dan Callaghan dcallagh at redhat.com
Tue Dec 3 04:27:44 UTC 2013


Excerpts from Jeffrey Burke's message of 2013-12-03 01:03:04 +1000:
>  Not sure this is the correct time to ask. But even on the current
> interface the Hypervisor field is a misnomer.  Looking at your current
> page. I get the impression that this system could not run virt jobs.
> Which is not the case, Virt jobs depend on a keyvalue pair HVM = 1.
> IMO I think we should change the name of that field to Virtualization
> or Virtualized.

The "Hypervisor" field is supposed to be short for "Type of hypervisor 
which this system is running inside of, if any". But I agree the name is 
ambiguous. I've filed a bug for it:

https://bugzilla.redhat.com/show_bug.cgi?id=1037280

>  I especially like the "Out of Service" and the "Loan to" information at
> the top. Is there an API talking to RT or is the information displayed at
> the top in the comments?

The screenshots were just a mock-up which I produced by editing the HTML 
by hand, there's no code behind them yet. Integration with RT has been 
talked about for a long time but I wasn't planning to tackle it. The 
"out of service" message would be the existing "Condition report" field, 
a message which the admin fills in when they mark the system as broken. 
Although I have been thinking it might make sense to get rid of 
"Condition report" and use system notes instead. For the "out of 
service" message it could just display the most recent system note.

-- 
Dan Callaghan <dcallagh at redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/beaker-devel/attachments/20131203/08f7bea7/attachment.sig>


More information about the Beaker-devel mailing list