| Summary: | Should move the oVirt tab to the sidebar which is belong to specific host | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-node | Reporter: | wanghui <huiwa> | ||||
| Component: | UI | Assignee: | Fabian Deutsch <fdeutsch> | ||||
| Status: | CLOSED DEFERRED | QA Contact: | Wei Wang <weiwang> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.0 | CC: | anilsson, bugs, cshao, huzhao, leiwang, rbarry, stefw, weiwang, yaniwang, ycui | ||||
| Target Milestone: | --- | Flags: | fdeutsch:
ovirt-4.1?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-09-02 10:14:08 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
IIUIC then dashboard still refers to the dashboard of a single server, not of multiple. Is this correct Ryan? If this is the case, then oVirt should stay in the top bar, but Cockpit should do a design change to make it more clear tha tthe top bar refers to one individual machine and not multiple. (In reply to wanghui from comment #0) > Expected results: > 1. It should be better to move the ovirt tab to sidebar which is belong to > specific host. > > The basic problem with this is that it would be very difficult to present a meaningful UX with a sidebar for different oVirt elements inside a cockpit tab. But it's worth noting that other Cockpit plugins (Kubernetes, for example) follow the same design pattern that the oVirt plugin is following right now. It's unusual that there's a "Dashboard" tab on top which manages multiple hosts and allow selection along with other tabs (Kubernetes, oVirt, etc) which are host-specific, but this is a pattern which is followed elsewhere in cockpit. (In reply to Fabian Deutsch from comment #1) > IIUIC then dashboard still refers to the dashboard of a single server, not > of multiple. Is this correct Ryan? > > If this is the case, then oVirt should stay in the top bar, but Cockpit > should do a design change to make it more clear tha tthe top bar refers to > one individual machine and not multiple. Also, yes, the dashboard shows at-a-glance statistics for localhost by default. It allows adding other servers for monitoring, though. The "Cluster" tab (kubernetes) and "Image Registry" (kubernetes) have host-specific views. Stef, do you have thoughts on this? If the dashboard does show multiple servers then it makes sense to show it along with the other dashboards. Andreas Nilsson is thinking about upgrading the navigation design further and hopefully there will be more UI symmetry between dashboards and per server tools in the future. Closing this, because it's a Cockpit design issue which should be tracked there. |
Created attachment 1150836 [details] Screenshot for ovirt tab Description of problem: Due to cockpit can add multiple servers in one cockpit services(serverA), it will change to machines as the label when move to ovirt tab. This will make misunderstanding which host we are configured in ovirt tab. And as I tested, for this time, the operation I does in ovirt tab will make changes only in serverA which is a host who host the cockpit services. But I think, if we can manage multiple server in one cockpit services, can we also move ovirt management for each host. If we can, we need to move the ovirt tab to sidebar which is belong to the specific host. Version-Release number of selected component (if applicable): ovirt-node-ng-installer-ovirt-3.6-2016042500.iso cockpit-0.103-1.el7.centos.x86_64 cockpit-ovirt-0.5.1-0.0.master.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Anaconda install NGN 4.0. 2. Start cockpit service. 3. In oVirt tab, Check the machine names. Actual results: 1. After step3, it's not point to one specific hostname. It just called Machines which will make a misunderstanding which host we are operated now. Expected results: 1. It should be better to move the ovirt tab to sidebar which is belong to specific host. Additional info: