Bug 1354029
| Summary: | [RFE] Reporting on OpenShift Custom Labels | |||
|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Mike Dahlgren <mdahlgre> | |
| Component: | Reporting | Assignee: | Federico Simoncelli <fsimonce> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Einat Pacifici <epacific> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 5.6.0 | CC: | azellner, cbudzilo, cpelland, fsimonce, jhardy, mbarrett, mdahlgre, obarenbo, simaishi | |
| Target Milestone: | GA | Keywords: | FutureFeature, TestOnly, ZStream | |
| Target Release: | 5.7.0 | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | container | |||
| Fixed In Version: | 5.7.0.1 | Doc Type: | If docs needed, set a value | |
| Doc Text: |
This release resolves an issue with the ability of CloudForms to generate a chargeback report using custom OpenShift tags.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1373709 1374377 (view as bug list) | Environment: | ||
| Last Closed: | 2017-01-11 20:24:12 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1373709, 1373712, 1373714, 1373715, 1373717, 1373718, 1374377 | |||
|
Comment 2
Mike Dahlgren
2016-07-08 18:36:39 UTC
Mike this is probably a duplicate of bug 1358257. Let me know so I can probably close this. Thanks. (In reply to Federico Simoncelli from comment #3) > Mike this is probably a duplicate of bug 1358257. Let me know so I can > probably close this. Thanks. Sorry, to clarify, that was actually a bug on a similar feature related to chargeback (which was already delivered in 5.6 GA). This REF seems actually something new. Federico, I agree the other bug is an error being thrown from a provider if blank labels are used. The primary use case of this bug is being able to add custom labels from OpenShift into a chargeback report. Mike, Im trying to figure out the exact intentions here: 1) Is the requirement to display tags as columns? meaning if we have a 'location=Minneapolis' custom tag then the user would be able to add 'location' as a column and each line in the report would show a different 'location' based on what the x defined in the 'location=x' tag. 2) Filter - Is there a requirement to filter by these tags? just one or many? meaning if 'location=Minneapolis' is set then the user could create a chargeback report in which only ContainerProjects with 'location=Minneapolis' would be considered in it. Right now i think we support filtering by one tag only. 1) You are correct the expectation is you would be able to add the tags as a column. See the example below. 2) Yes, that would be great, but just being able to get an output charge back report would be huge. Having multiple filters is just a nice to have. The hope is once this is finished a customer could create a chart similar to the following. *Charge back report for container usage for the last month* Project Name | Department | Location | Number of Containers(* hrs?) | Total cost Project X | Developers | Minneapolis | 212 | $350 Project Y | Developers | San Diego | 399 | $550 Project Z | Operations | Minneapolis | 55 | $80 Verified. It is now possible to generate a chargeback report with model tags as columns in the report. |