Bug 1687543
Summary: | [RFE] - Need a way to add headings in Virtual Machine View | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Anand Jambhulkar <ajambhul> |
Component: | Compute Resources - VMWare | Assignee: | Chris Roberts <chrobert> |
Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.4 | CC: | bkearney, chrobert, dcarmich, mhulan, mmccune, oezr, oprazak, walden, zhunting |
Target Milestone: | 6.6.0 | Keywords: | FutureFeature |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | foreman-1.22.0-0.5.RC2.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-22 12:47:16 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: |
Description
Anand Jambhulkar
2019-03-11 17:03:29 UTC
Created redmine issue http://projects.theforeman.org/issues/26317 from this bug I suppose this is vmware VMs listing. Each compute resource have different capabilities what we can display. Ondrej, do you know if we could get this VM's OS from fog-vsphere today? The same for VM's host and cluster. If the library provides us the information, it may be an easy fix just in our UI. There's currently no easy way to customize the list, but adding this and makes sense. We may need to condense the information a bit, since the table can't contain many more columns, but that's doable. One thing that could help this table would be to add customizable columns to it by converting the table to react. There is not a big problem to add more information to a table, maybe even make it into React. What is actually the biggest concern here is a performance. As we have written own logic to get vmware VMs from the vsphere to gather only the necessary subset of information, I believe it was already a concern in the past. I can imagine to make this logic adjustable so we would pull only information user requested, but it could get harder to make the caching work. I would like to have some measurements of the performance impact and than decide what to do. I can prepare the logic, but I have only ~120 VMs datacenter at hand, I would rather see that one tested on bigger datacenter. I will prepare the patches with measurements for performance impact on the cluster available to me. OS and host are easy to add without major performance impact, tested on ~750 vms. The BZ also mentioned cluster, not sure what the impact of that would be. I'd prefer to keep selectable columns in this table out of the scope for this BZ. I think we could shrink all 3 new columns (OS and host fit well). We have managed to get done the hypervisor and the OS columns. Shall this tracker keep open for more features, or is that going to be enough for this one? Upstream ticket is kept open for more dynamic approach. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3172 |