Red Hat Bugzilla – Bug 1021338
[RFE] webadmin: please add custom columns
Last modified: 2018-01-04 04:49:19 EST
Webadmin shoult have the possibility to add custom columns, like cpu count, allocated memory, number+size of attached disks and so on. Basically any VM parameter should be available as column.
Reason: Better overview.
I think we need the infrastructure support to be able to add/remove columns. Is it coming, Einav?
(In reply to Michal Skrivanek from comment #1)
> I think we need the infrastructure support to be able to add/remove columns.
> Is it coming, Einav?
indeed, that's why Itamar marked this bug as "depends on" bug 957600 (ux) which is exactly about that - adding the infrastructure.
[moving this one back to 'virt' - once the infrastructure is in place, it will be 'virt' responsibility to utilize it for the grids/columns in its responsibility]
setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
dependent on rhevm-future bug, pushing out
dependent infrastructure not yet in, resetting target until we have it
I would like this feature.
(In reply to Gianluca Cecchi from comment #6)
> I would like this feature.
I don't think it'll happen in the near term future - are there specific columns that are missing that are in a higher priority to be added?
I think we need these numbers: vcpu count, gb memory, disk gb total.
If there would be an aggregation whem multiple hosts are selected/filtered that would be awesome :)
I agree with Ernest and what said in his comment#8
+1. I'd like to be able to see VM memory size.
This is clearly something that would benefit the GUI.
One obvious example, sometimes while doing manual VM migrations, on the hosts screen (having the respectives VM screen right below), it should be clearly visible the VM RAM usage to be sure to migrate the right VM to the right host (and not migrate a VM that is using to much RAM on a overloaded host)
This is just one example, I can think of some more...
Is there anything more we can do to up the priority of this request?