Bug 1497947

Summary: [RFE] Metrics: Number of hours should be available in Reporting including Chargeback
Product: Red Hat CloudForms Management Engine Reporter: Loic Avenel <lavenel>
Component: ReportingAssignee: Libor Pichler <lpichler>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.8.0CC: dajohnso, jhardy, lpichler, nachandr, obarenbo, simaishi
Target Milestone: MVPKeywords: FutureFeature
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: chargeback
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:19:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Feature
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screen shot of Default Chargeback rate without Metering group none

Description Loic Avenel 2017-10-03 08:07:27 UTC
Description of problem: In Performance and Chargeback Reporting, we should report the number of hours an entity (VM, Instance, Container, Project, Pod) are running over the interval. 
In this requirement we should count every hour started not the total of minutes on the interval and translate in hours.

Comment 2 Loic Avenel 2017-10-03 08:12:27 UTC
https://github.com/ManageIQ/manageiq/pull/15908

Comment 4 Nandini Chandra 2017-10-26 20:42:16 UTC
I'll be verifying this for infra and cloud VMs.

I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1506816 so that the Container team can verify it for Containers.

Comment 6 Nandini Chandra 2017-11-10 18:41:01 UTC
Created attachment 1350618 [details]
screen shot of Default Chargeback rate without Metering group

Comment 8 Nandini Chandra 2017-11-15 22:29:47 UTC
Verified in 5.9.0.8

Comment 11 errata-xmlrpc 2018-03-01 13:19:00 UTC
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-2018:0380