Bug 1541110 - [RFE] Chargeback reports for OpenStack tenants
Summary: [RFE] Chargeback reports for OpenStack tenants
Keywords:
Status: CLOSED CURRENTRELEASE
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.10.0
Assignee: Libor Pichler
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks: 1552796
TreeView+ depends on / blocked
 
Reported: 2018-02-01 17:46 UTC by David La Motta
Modified: 2021-06-10 14:26 UTC (History)
7 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1552796 (view as bug list)
Environment:
Last Closed: 2019-12-13 15:21:23 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David La Motta 2018-02-01 17:46:42 UTC
Description of problem:
Our chargeback reports need an overhaul in order to become more user friendly. Users can apply chargeback rates to OpenStack tenants; however, there is no way in the chargeback reports to get a single report grouped by OpenStack tenants. That's it. As simple as that sounds, one has to rely on tags and different contortions just to get the grouping--and then the data doesn't show up.

PLEASE IMPROVE THIS CRITICAL FEATURE IN CLOUDFORMS.


Version-Release number of selected component (if applicable):
All

How reproducible:
100% 

Steps to Reproduce:
1. Assign rates to OpenStack tenants
2. Create a chargeback report and try to group by OpenStack tenant
3. ...and realize it's not possible

Actual results:
Currently the chargeback report allows users to create a single report for one tenant. Well, if I have hundred of tenants that means I have to create a hundred reports, then aggregate, and the story just crumbles from there


Expected results:


Additional info:
We have multiple customers requesting this feature.

Comment 10 Tasos Papaioannou 2019-12-09 15:36:25 UTC
Verified on 5.10.0.33.


Note You need to log in before you can comment on or make changes to this bug.