[2.3rc2, UI] Information is missing from the CPU and Memory cards in controller summary

[Maria Vrachni]

* Current result:

Given I am in the controller details in the summary section
When I see the CPU and memory cards
Then the cards are empty

* Expected/ correct result:

Given I am in the controller details in the summary section
When I see the CPU and memory cards
Then I should be able to see metric data and more information for CPU and memory
Or not see the cards at all

[OS X Sierra]

Chrome, Version 61.0.3163.79 (64-bit)

[Björn Tillenius (bjornt)]

I don't think there's a problem with having the cards empty. If the controller isn't a machine, we can't run any hardware tests on it, so we will never have any metrics. However, currently the CPU and memory information is only available in the cards.

So, if we remove the cards, we'd have to display the CPU and memory information elsewhere.

[Maria Vrachni (m-vrachnis)]

@Bjorn

I agree, however, there is a requirement to avoid white space, so if we can't provide metrics we need to rethink the design of the summary pages. I will assign this one to me.

[Lee Trager (ltrager)]

Controllers may have metrics so we can't completely remove these cards. For example if a machine was converted to a controller or if power information was added to a controller so it could be tested.

[Maria Vrachni (m-vrachnis)]

@Lee

Could we add the metrics in the cards as designed both for machines and controllers? The cards are never supposed to be empty.

The way the cards were designed was to show the metric name even if there is no value for them. for example:
                        ___________________________________
                       | |
Metric 1: (No data) ¡ < Run <testname> to get this metric |
                       |___________________________________|
Metric 2: (No data) ¡

Metric 3: (No data) ¡

In this way the cards will never be empty and they will help the users discover what additional data they can get. The empty cards are just creating a lot of white space.

Also, if we could provide some basic values for each component, we would have an even better result.

For example for CPU:
cpu model
frequency
VMX

For memory:
#DIMS
bandwidth
cache size

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team