Bug 1238287
| Summary: | [RFE] Monthly Billing - Report to provide watermark sockets of hypervisors | |||
|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | John Hardy <jhardy> | |
| Component: | Reporting | Assignee: | Gregg Tanzillo <gtanzill> | |
| Status: | CLOSED ERRATA | QA Contact: | Nandini Chandra <nachandr> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 5.4.0 | CC: | cpelland, dclarizi, gblomqui, gtanzill, jhardy, mfeifer, obarenbo, soconcar | |
| Target Milestone: | GA | Keywords: | FutureFeature, ZStream | |
| Target Release: | 5.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 5.5.0.8 | Doc Type: | Enhancement | |
| Doc Text: |
Previous CloudForms Management Engine versions did not report a high watermark for the number of virtual machine sockets on a provider's hypervisors over a one-month period. This functionality has been added to the current version of CloudForms Management Engine. A report can now be queued to collect watermark information for sockets on each hypervisor per provider.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1262016 (view as bug list) | Environment: | ||
| Last Closed: | 2015-12-08 13:20:40 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: | 1262016 | |||
|
Description
John Hardy
2015-07-01 14:14:47 UTC
ManageIQ/manageiq: Pull Request #5006 ManageIQ/manageiq: Pull Request #5090 Verified the following: 1)The report to provide watermark sockets of hypervisors per provider is now available as an OOTB report. 2)The report can be queued and that it reports the watermark sockets of hypervisors per provider. Verified in 5.5.0.9 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-2015:2551 |