YANIV LAVI
SENIOR TECHNICAL PRODUCT MANAGER
Red Hat Israel Ltd.
34 Jerusalem Road, Building A, 1st floor
Ra'anana, Israel 4350109
ylavi@redhat.com    T: +972-9-7692306/8272306     F: +972-9-7692223    IM: ylavi
TRIED. TESTED. TRUSTED.


On Tue, Jul 31, 2018 at 5:14 PM Moran Goldboim <mgoldboi@redhat.com> wrote:


On Tue, Jul 31, 2018 at 4:43 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
On Tue, Jul 31, 2018 at 5:47 AM Liz Blanchard <lsurette@redhat.com> wrote:


On Sun, Jul 29, 2018 at 11:36 AM, Nir Soffer <nsoffer@redhat.com> wrote:
On Fri, Jul 27, 2018 at 6:13 PM Vojtech Szocs <vszocs@redhat.com> wrote:
> * Cluster cube shows "1 cluster" but also "N/A" even when my cluster is up with 2 machines (with DNS names).

The "N/A" text shown in Cluster status card simply means that we aren't tracking status (up/down/etc.) for the Cluster object within the Dashboard.

This looks bad, we need a better way.

Agreed. This came from not having anything to "roll up" about Clusters, but we can do a better job making this clear rather than making it seem broken with "N/A". Does anyone have any suggestions on something that would be helpful to see about the clusters at this level?

Nothing comes to mind for me :) @Tomas Jelinek @Michal Skrivanek any thoughts?

from the top of my head, it could be a joint query:
status up:
-The Data Center of the cluster is up (storage/SPM are ok) and there is at least one host in the cluster in an up state (cluster can run VMs)

status down:
-everything else
 
or we can break it a bit more if needed:
status maintenance:
-DC is up, all hosts are in maintenance or no hosts configured on the cluster

status contending:
-SPM election is in progress

I would just not show anything.
We should not add a status if one doesn't exists.
If we want to add cluster status it should first happen in the manager.
 
 
 

Thanks,
Liz
 

Nir

_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/J4KSJHJSVIZ76B54UVYR3SDPZUTNK57G/


_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
 List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/U6QTGXKC5R6C5RTSH34BO6LN5B6BADGU/


--

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA

gshereme@redhat.com    IRC: gshereme


_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/24H655OSCAHC5F2DBLWFZZ5GJR2MEMKU/


_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/MMDKTJRWF5JKOGC52DCS6P5FE4BOJ2VU/