Bug 1304617

Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Contents of the dashboard (only passive):

Statistics
List VMs
Actual accumulated VM usage charts (cpu/mem/disk/net)
View SSH Host key
Network IP address information
HE Status

(In reply to Ryan Barry from comment #4)
> Contents of the dashboard (only passive):
> 
> Statistics
> List VMs
> Actual accumulated VM usage charts (cpu/mem/disk/net)
> View SSH Host key
> Network IP address information
> HE Status

Connected storage domains?
Package versions?

(In reply to Yaniv Kaul from comment #5)
> (In reply to Ryan Barry from comment #4)
> > Contents of the dashboard (only passive):
> > 
> > Statistics
> > List VMs
> > Actual accumulated VM usage charts (cpu/mem/disk/net)
> > View SSH Host key
> > Network IP address information
> > HE Status
> 
> Connected storage domains?
> Package versions?

Both of these are options. I worry that connected storage domains provides too much overlap with engine functionality (at least to start with), but it's definitely something we can look at adding.

(In reply to Ryan Barry from comment #6)
> (In reply to Yaniv Kaul from comment #5)
> > (In reply to Ryan Barry from comment #4)
> > > Contents of the dashboard (only passive):
> > > 
> > > Statistics
> > > List VMs
> > > Actual accumulated VM usage charts (cpu/mem/disk/net)
> > > View SSH Host key
> > > Network IP address information
> > > HE Status
> > 
> > Connected storage domains?
> > Package versions?
> 
> Both of these are options. I worry that connected storage domains provides
> too much overlap with engine functionality (at least to start with), but
> it's definitely something we can look at adding.

Multipathing status is a feature requested on engine (and isn't there) and is probably quite easy to do in Cockpit, btw.

(In reply to Yaniv Kaul from comment #7)
> (In reply to Ryan Barry from comment #6)
> > (In reply to Yaniv Kaul from comment #5)
> > > (In reply to Ryan Barry from comment #4)
> > > > Contents of the dashboard (only passive):
> > > > 
> > > > Statistics
> > > > List VMs
> > > > Actual accumulated VM usage charts (cpu/mem/disk/net)
> > > > View SSH Host key
> > > > Network IP address information
> > > > HE Status
> > > 
> > > Connected storage domains?
> > > Package versions?
> > 
> > Both of these are options. I worry that connected storage domains provides
> > too much overlap with engine functionality (at least to start with), but
> > it's definitely something we can look at adding.
> 
> Multipathing status is a feature requested on engine (and isn't there) and
> is probably quite easy to do in Cockpit, btw.

I haven't checked on the status in a couple of weeks, but there's ongoing work with storaged and cockpit which may end up implementing this. I'll investigate.

(In reply to Ryan Barry from comment #4)
> Contents of the dashboard (only passive):

> List VMs
> Actual accumulated VM usage charts (cpu/mem/disk/net)

this is an overlap as well. Not sure if worth investing in downstream in the first iteration. The calls to retrieve that might be too expensive, and we will have the same info in the "normal" 4.0 UI dashboard. I would propose to leave it open for now

(In reply to Michal Skrivanek from comment #9)
> (In reply to Ryan Barry from comment #4)
> > Contents of the dashboard (only passive):
> 
> > List VMs
> > Actual accumulated VM usage charts (cpu/mem/disk/net)
> 
> this is an overlap as well. Not sure if worth investing in downstream in the
> first iteration. The calls to retrieve that might be too expensive, and we
> will have the same info in the "normal" 4.0 UI dashboard. I would propose to
> leave it open for now

True, unless we can pick it from vdsm-collect daemon I'd like to see introduced in the near future (splitting the metrics collection from VDSM and sending it to an independent metrics collection).

(In reply to Michal Skrivanek from comment #9)
> (In reply to Ryan Barry from comment #4)
> > Contents of the dashboard (only passive):
> 
> > List VMs
> > Actual accumulated VM usage charts (cpu/mem/disk/net)
> 
> this is an overlap as well. Not sure if worth investing in downstream in the
> first iteration. The calls to retrieve that might be too expensive, and we
> will have the same info in the "normal" 4.0 UI dashboard. I would propose to
> leave it open for now

We also have the option of pulling this from libvirt just for a node-only summary (the current TUI shows how many VMs are running on the system as well), if vdsm is too expensive, though vdsm is obviously preferred.

[pushed it out to 4.1 - I'd be happy to see this in 4.0 / 4.0.z, but I want it off the radar for 4.0 GA. I do expect work on it during 4.0 timeframe).

Yaniv, this is actually part the Cockpit dashboard of Node for 4.0 and this is scheduled for 4.0 GA.

Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

*** Bug 1318379 has been marked as a duplicate of this bug. ***

Test version:
rhev-hypervisor7-ng-4.0-20160527.0
cockpit-ovirt-dashboard-0.10.1-0.0.1.el7ev.noarch

Test steps:
1. Install rhev-hypervisor7-ng-4.0-20160527.0
2. Enter cockpit
3. Check the oVirt page

Test result:
1. In oVirt page, it now has the follow items.
   - Dashboard
     | - VirtualMachines' status
     | - View Networking information
     | - View System Logs
     | - View Storage
     | - Show SSH Host Key
   - Hosted Engine setup
   - Virtual Machines page

Ryan,

Could you please help to review the above test result. Is those items enough for cockpit page now? Or we still need to add more items in oVirt page.

Thanks!

There will be one more page coming in the next couple of days (patch landing upstream today) --

"Hosted Engine Status"

Now that the necessary patches to ovirt-hosted-engine-setup have merged and are part of builds.

However, this page is simply presentation, so verification should be very easy.

"Hosted Engine Status" page is added in rhev-hypervisor7-ng-4.0-20160607.1.x86_64(cockpit-ovirt-dashboard-0.10.3-0.0.1.el7ev.noarch) now. So this issue can be verified. All the detail issues will be tracked by specific bugs.

oVirt 4.0.0 has been released, closing current release.