Bug 1506816 - [RFE] Add Metering Used Hours to chargeback report for containers
Summary: [RFE] Add Metering Used Hours to chargeback report for containers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.9.0
Assignee: Gregg Tanzillo
QA Contact: Gilad Shefer
URL:
Whiteboard: chargeback:container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-26 20:39 UTC by Nandini Chandra
Modified: 2018-03-01 13:20 UTC (History)
8 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 13:20:20 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:
gshefer: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1497947 0 unspecified CLOSED [RFE] Metrics: Number of hours should be available in Reporting including Chargeback 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Internal Links: 1497947

Description Nandini Chandra 2017-10-26 20:39:14 UTC 
Description of problem:
-----------------------
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.


Additional info:
----------------
Comment 2 Nandini Chandra 2017-10-26 20:39:42 UTC 
https://github.com/ManageIQ/manageiq/pull/15908
Comment 6 Gilad Shefer 2018-01-31 13:06:33 UTC 
Could you please describe how/what should I test?, should I see a new column? also, AFAIK the calculation is already done with hours.
Comment 9 errata-xmlrpc 2018-03-01 13:20:20 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
Note You need to log in before you can comment on or make changes to this bug.