| Summary: | CPU Used and CPU Used cost reported zero for OSP instances in Chargeback Reports | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Nandini Chandra <nachandr> |
| Component: | Reporting | Assignee: | Marek Aufart <maufart> |
| Status: | CLOSED WONTFIX | QA Contact: | Omri Hochman <ohochman> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.6.0 | CC: | cpelland, dajohnso, dcain, gblomqui, jhardy, lars, lavenel, lsmola, maufart, michael_rasoulian, obarenbo |
| Target Milestone: | GA | Keywords: | PrioBumpPM |
| Target Release: | 5.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | openstack:chargeback | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-20 11:54:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | Openstack | Target Upstream Version: | |
|
Description
Nandini Chandra
2016-08-22 21:04:09 UTC
I talked to Ladislav a bit about this one, and he mentioned that cpu_usagemhz_rate_average is derived from undercloud data. If so, then you may be affected by this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1364584 Ladislav, are there additional factors I may be missing? I did wrote a nice response, the BZ crashed and didn't save it. :-) Right, so we might need to revisit if the cpu speed is not available in the new versions of OpenStack, the code is like 1.5 years old. right now, we compute the cpu_usagemhz_rate_average from cpu_usage_rate_average https://github.com/Ladas/manageiq/blob/5be79d08113b52daa183453fdd709aba73cf7e62/app/models/metric/processing.rb#L95-L95 cpu_usage_rate_average should be normalized on OpenStack side to 0-100%. It divides it by number of cores I think. Then on our side the cpu_usagemhz_rate_average = number_of_cores * cpu_speed * cpu_usage_rate_average Btw. the info we take from Undercloud is the cpu_speed, which came from Ironic extra data at that time. Hi, I see this is targeted for 5.7, but we are still seeing this in the latest release (5.7.2). Any update on this issue? Thanks. Tzu-Mainn Chen spent some time helping me look into this, and we have a theory. It looks as if the chargeback columns are based on the cpu_usagemhz_rate_average metric. In https://github.com/ManageIQ/manageiq/blob/master/app/models/metric/processing.rb, this value is calculated from cpu_usage_rate_average (which we have) and total_cpu. total_cpu is calculated in https://github.com/ManageIQ/manageiq/blob/master/app/models/vim_performance_state.rb#L163 from cpu_speed. cpu_speed apparently comes from https://github.com/ManageIQ/manageiq-providers-openstack/blob/master/app/models/manageiq/providers/openstack/infra_manager/refresh_parser.rb#L238. You'll note that last value comes from an infra provider. In this deployment (as in many non-Directory deploymens) there is no undercloud, hence no infra provider, so it looks like this value is going to be zero. --- This may be fixable: even without an undercloud we are already collecting what appears to be an equivalent metric. There is a "compute.node.cpu.frequency" metric attached to each Nova hypervisor when properly configured. It seems as if this would actually be a better source of the information, since it's reported in the overcloud. I note that OpenStack also provides "cpu" and "cpu.delta" metrics, both of which track the actual amount of CPU time used (in nanoseconds), which seems like it may be more directly applicable to billing (via https://docs.openstack.org/ceilometer/latest/admin/telemetry-measurements.html#openstack-compute). Bug Closure Dear customer, The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. If you have any concerns about this, please let us know. Thanks and regards! |